-
Notifications
You must be signed in to change notification settings - Fork 130
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
Using AAD SAML auth with AnyConnect #143
Comments
No scripts for doing the "SAML auth tap-dance" with Azure exist, as far as I know, but should be possible to start with something like @arthepsy's https://github.com/arthepsy/pan-globalprotect-okta and adapt for this purpose. Also see #137, where a user got Azure auth working… but this seems to be a setup without SAML. |
My workplace just moved to a SAML-based Azure AD authentication. Previously they were doing MFA in a way that worked with the Auth app. I would really much rather NOT have to switch to AnyConnect. Is there anything specific that I could do to help move this support along? |
@chrispoupart Can you share logs of what it looks like when openconnect v8.x tries to connect to your server ( Also, let's please move this over to Gitlab, where all the upstream development is happening. I created https://gitlab.com/openconnect/openconnect/issues/84 |
@dlenski can we get this GitHub project annotated in some fashion, then, if you're moving development to GitLab? |
My company recently switched from Okta to Microsoft Authenticator causing the standard Gnome VPN client to not connect anymore, for those with the same issue @vlaci's https://github.com/vlaci/openconnect-sso solved the issue. |
Thank you @rlueder ! I just wrote these detailed instructions on how to install and use |
I'm trying to connect to an AnyConnect VPN while using OpenConnect. Unfortunately, this particular VPN uses SAML, provided by Azure AD.
Are there any options available for doing this with an AnyConnect VPN? I know that there's been work with GlobalProtect VPNs and SAML auth via Okta, but this seems to be a separate ballgame.
The text was updated successfully, but these errors were encountered: