-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty cookie error after server upgrade from 7.2.7 to 7.2.8 #1205
Comments
Just noticed i was running an older version of openfortivpn. Tested it with the newest version (v1.21.0) but the issue remains:
|
The server might have moved to SAML with authentication is a web browser. See #867. You can also give openconnect a try. |
I did some more research and resolved my issue. I login using the command When removing the username and password from the openfortivpn command I force it to authenticate using certificates. Now I can connect without any issue. My new command is It seems the upgrade from FortiOS 7.2.7 to 7.2.8 reacts differently to sending both user/pass and certificates, causing this issue after our server upgrade. |
Thank you very much for the explanation. I wonder whether there are cases where both the certificate and the username/password are required. Otherwise, we could force authentication with the certificate when or at least emit a warning if user/password are passed as arguments in addition to the user certificate. |
For testing I've tried to login using the official Forticlient VPN client, using username 'foo' while authentication using my 'milenco' certificates. It seems the username gets fully ignored, no mentions of it in the logs on the firewall side:
This is the relevant part from my firewall config:
The Hope this helps. |
I have been using username/password and certificate in combination. This not truly a second factor because all the credentials reside on the same client device, but it's at least a good protection against a simple password leak. I still have that VPN running, but I must admit that I haven't used it for a while. |
So using a different username or password in combination with your certificate actual fails to log you in? Because I can't replicate that behavior, but it's very well possible it's because of my configuration. |
I think so, but I'll try that out. Unfortunately that VPN doesn't respond at all right now. I have to check on-site what's the problem. Maybe an important detail: in this case users and groups are local ones on the Fortigate. If authentication happens via LDAP or AD things might be different. But I'll check it for local users/groups when I get that setup working again. |
Finally I had the chance to do the promised double-check: With a local user on the Fortigate with certificate authentication and user/password, the certificate and the password must match. If a wrong password is entered, the authentication is aborted:
|
Thanks dor reporting back! So both methods (just a certificate as well as certificate+user/pass) must be supported. |
Yesterday I've upgraded our Fortinet firewall from FortiOS v7.2.7 to 7.2.8. Ever since, I can't login anymore using openfortivpn. This issue occurs on multiple hosts from multiple locations. Logging in via the Forticlient VPN client (on macOS) continues to keep working fine.
When logging in using the command
openfortivpn example.com:10443 -u milenco -p mypassword --set-routes=1 --set-dns=1 --user-cert=/root/cert.pem --user-key=/root/cert.key --ca-file=/root/ca.pem -vvvv
I get the following output:On the server-side I get this debug log (not sure if it's relevant):
I suspect something broke on openfortivpn's side after the FortiOS upgrade to 7.2.8, causing the
Empty cookie.
error, which seems to be the root cause of this issue.Others with the same issue after 7.2.8 (or upgraded and have no issue)? Is there anything I can do to resolve this or help test?
The text was updated successfully, but these errors were encountered: