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
PulseSecure support with SAML and 2FA #11
Comments
Please run openconnect-sso with |
Thanks for your reply, I can paste at least the beginning as starts with |
Are you sure you are connecting on an AnyConnect compatible endpoint? Does anyconnect work on that endpoint? The reason I ask this is that openconnect-sso (and openconnect in anyconnect compatibility mode too) expects that the endpoint it connects to serves an XML like this:
|
I'm trying to connect to a PulseSecure PSA5000 which is working fine as long as it's not using SAML. If the login is username/password + 2FA, everything works as expected. For openconnect I'm adding the paramenter --juniper. |
Unfortunately It seems to me that unlike AnyConnect, Pulse is starting with the web for authentication. I have found that we'd need to parse the |
thanks for looking into that. I had a look at the repo you mentioned and also gave it a try, same behavior. |
@bene2342 @vlaci
|
Keep in mind that this will be complicated if a host checker is in use (at least our company pulse server requires the host checker before authentication on the website) |
I tried connecting to a Pulse Secure appliance which is configured with GSuite and 2FA, unfortunately it was not working. It would be great if that could be added. Some output I able to share.
The text was updated successfully, but these errors were encountered: