-
Notifications
You must be signed in to change notification settings - Fork 140
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
Error after SSO Auth (Azure) is complete #93
Comments
I got the same exect same error, but managed to get it to work after importing the anyconnect profile using edit: I get error message on the first run, second run it connects.. |
For us in our organization we had to stop passing the username in the cli as Azure does a stricter check apparently. |
Thanks @sam-sla ! The solution works for me. A further look seems to indicate my organization (or Azure) now checks how quickly the "sign in" button is clicked. If it's too quickly, the authentication fails. In my case, I managed to work around it by replacing the following lines in ~/.config/openconnect-sso/config.toml
with
so that the saved username and password still work, only the "sign in" button needs to be clicked manually. |
In case someone would like to automate the authentication process before the official fix is out, another workaround is to add a delay before clicking the "sign in" button: Change
to: |
Running
openconnect-sso --server vpnserver --user myuser -l debug
Goes through SSO with autocomplete user/password - and after completing 2FA verification, this happens:
I tried some tips from #57 without any luck, namely
#57 (comment)
and
#57 (comment)
Since the error message is different, I open a new issue.
Running this on MacOS Big Sur 12.5.
Any tips?
The text was updated successfully, but these errors were encountered: