László Vaskó

The default rules are the following (in ~/.config/openconnect-sso/config.toml`): ``` [auto_fill_rules] [[auto_fill_rules."https://*"]] selector = "div[id=passwordError]" action = "stop" [[auto_fill_rules."https://*"]] selector = "input[type=email]" fill = "username" [[auto_fill_rules."https://*"]] selector = "input[type=password]" fill =...

The error message is that somehow your VPN server still returns an auth request response, instead of complting the authentication. At debug loglevel the response message is logged on screen....

It would be great to know what anyconnect does differently in your case. A [mitmproxy log](https://docs.mitmproxy.org/stable/overview-getting-started/) of a successful login with anyconnect would be most helpful. **Make sure to remove...

It is indeed funny as the last connection attempt shows a succesfull authentication. At debug log level openconnect-sso logs all request-responses. Mitmproxy would help to capture Anyconnect's traffic to figure...

Could you check if the issue persist with the newest 0.6.1. I hope, that #37 may have fixed this issue.

FYI as of 0.7.0, the browser properly caches cookies between connection attempts so that it is possible to reuse a previous successful authentication.

Yeah, I still see that cookie saving is racy somehow. It may work for someone and won't for others. :(

😞 Thanks for figuring that out! I have the idea that I should remove multiprocessing and python subprocesses altogether.

Just to ping you back I have finally merged all outstanding changes to master. I am planning to remove this multiprocessing machinery altogether in an upcoming version.

Could you try changing the following line: https://github.com/vlaci/openconnect-sso/blob/54da0073732cc1cb445360c3d6f0c915ae223ec8/openconnect_sso/authenticator.py#L187 to look like ```python auth_message=xml.auth.get("message"), ``` and see if the connection succeeds that way.