I just installed the 7.0.14 update over the weekend and now, FortiClient VPN on Android is no longer authenticating.
We use Okta SSO to authenticate with FortiClient. We get the Okta login just fine but while it authenticates, the browser in the app goes to 127.0.0.1:8020 and says site can’t be reached. When we close the browser, the FortiClient app shows “Could not retrieve auth ID” and the connection fails.
We had users connect on Friday just before the update and since the update was caused by an SSLVPN vulnerability, I suspect FortiClient added additional settings or whatnot which is preventing our tablets and phones from connecting.
Our laptops connect without issues.
Anyone else having these issues?
Edit: Just got off the phone with FortiGate support. There is apparently an update to the Android VPN app that should be available next week so hopefully, that fixes the issue.
Edit2: It’s bug number 0924259 for the FortiClient. The update is going to be 7.2.2.
Not sure if you’re using LetsEncrypt and older Androids. LetsEncrypt dropped support for Android 7.0 and older on Feb 8th 2024 (by dropping cross-signing by default).
Tested this today with the the app version that I can find in the Store (version 7.2.2.0127) and still having issues. Can somebody else confirm it is already working fine for them?
Having the same exact issue here after the 7.0.14 upgrade, though we use Azure SSO. Do you get an Untrusted Certificate error when connecting to the Forticlient VPN on your devices?
Yup… I am trying to schedule a screen share. The support rep doesn’t seem to understand the issue which is baffling since I’m clearly not the only one who is having this issue.
Things are getting more and more interesting. With a number of test devices, the issue occurs. However, one of our intermediate managers is not experiencing this issue at all. For the life of me I can’t find any difference with his configuration and the configuration that we have on our test devices. Any hint? thanks!!
Nope, the certs seems okay. I did try to disable trusted cert settings in the Android app to see if it’s a cert issue but no dice. I opened a ticket with Fortigate support to see what the issue could be.