- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7.0.17 - breaking SAML
Hi,
Anyone else noticing issues with login to SSLVPN using SAML with Entra after upgrade to 7.0.17 for users with FortiClient 7.4.X ?
Did an upgrade on FOS to a client and it broke the connection for newer versions butwith FortiClient 7.2.X it appears to work just fine and it used to work also with this version up until upgraded .
A similar issue was also brought up here
Solved! Go to Solution.
- Labels:
-
FortiClient
-
FortiGate
-
SAML
-
SSL-VPN
-
SSO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same experience. Users required to offload saml to external browser.
Pushed to 7.2.10 as EoES was mentioned in my support ticket
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A simple advice would be to bump yourself up to FortiOS 7.0 and start using external browser for SAML logins. Then you can offload all the cookie shenanigans and username/pwd saving to your default browser, and stop caring what FortiClient makes or breaks next.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I guess they broke something when they fixed the below in 7.0.17.
1101837 | Insufficient Session Expiration in SSLVPN using SAML authentication. |
The issue now is that they "may" not fix it in 7.0.x anymore since it is EoES.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same experience. Users required to offload saml to external browser.
Pushed to 7.2.10 as EoES was mentioned in my support ticket
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your input guys.
Have a nice day!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are working on this issue and created an engineering ticket #1117475 for tracking, can you help share the config file, FCT and FGT debug logs, TAC case number if any to sferoz@fortinet.com for more investigation.
