Set-Cookie: SVPNCOOKIE= path=/ expires=Sun, 12:00:00 GMT secure httponly GET /remote/login?realm=saml&lang=en HTTP/1.1 Location: /remote/login?realm=saml&lang=en Compared with http traffic from the latest windows version (7.) of the same client: GET /remote/info HTTP/1.1 Is there a bug in v7 of FortiClient or is there some server side config that could be improved (for mac users)?Įdit: It's obvious that the mac-version does something wrong. If I put in the gateway url into my Chrome browser, I am correctly redirected to my SSO login page. Server does not respond to this last request :(Īccording to this comment on github: response from the /remote/saml/start should redirect me to the login page. Request 2: GET /remote/saml/start HTTP/1.1Īccept: text/html,application/xhtml+xml,application/xml q=0.9,image/avif,image/webp,image/apng,*/* q=0.8,application/signed-exchange v=b3 q=0.9 Strict-Transport-Security: max-age=31536000 User-Agent: Mozilla/5.0 (Macintosh Intel Mac OS X 12_0_1) AppleWebKit/537.36 (KHTML, like Gecko) FortiClient/6.0.0 Chrome/.88 Electron/11.1.1 Safari/537.36Ĭontent-Security-Policy: frame-ancestors 'self' object-src 'self' script-src 'self' https 'unsafe-eval' 'unsafe-inline' blob: Tracing the http-requests using a local proxy, I get this output: When I click 'Saml login', I get a blank pop up window with the text: The response from: My config:Gateway: /samlPort: 443SSO-option checked. (The free VPN-only version)Mac OS: Monterey 12.0.1 However, I would like to get the SSO working also.įorticlient: 7. The normal non-SSO option is working fine on Mac, so it's not a problem working remotely. There are a few of us that are using Mac, but they say 'we don't support Mac', so I'm left to fend for my self. Most of the users are using Windows and the Fortinet VPN client for Windows is apparantly working fine. My IT dept recently rolled out a SSO option for our SSL-VPN.

Forticlient vpn not connecting mac