- Newest
- Most votes
- Most comments
I would like to inform you that the AWS Client VPN team is aware of an issue affecting customers that use Chrome version 123 and SAML authentication [1]. We are working on a new client release to address this issue and as a workaround we recommend using another browser such as Firefox as your default browser.
Similar issues are reported for the Safari browser as well and the work around is to use Firefox as your default browser.
Please accept our apologies for any inconvenience caused. If you require further assistance or have any questions, please don't hesitate to reach out to us. We would be glad to assist you.
References
[1] https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/federated-authentication.html
it is still possible to use chrome and work around this, while the issue is being addressed, disable the chrome flag (chrome://flags/) "Reduce waiting time for Private Network Access preflights response"
Relevant content
- asked a month ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 8 months ago
I'm also seeing this problem. In my case I'm on windows and switching Chrome -> Edge is the fix.
This is also happening at my org for users on both Mac and Linux, each using clients 3.9.1 and 3.12.1, respectively. Azure SAML in our case. For now we are recommending our users switch to Firefox.
Best not to upgrade your browsers it seems. Safari broke for me first. Chrome worked but then I went to check the version and that point it helpfully upgraded, breaking that work around.
Just wanted to Chime in and add Latest macOS/Safari/VPN Client/Chrome and very broken. Using Google as our SAML/Idp with the Application ACS URL configured as "http://127.0.0.1:35001". Others have tried to change that to https with no luck.
My re:Post: https://repost.aws/questions/QUrtBrUIkeQjCWINLH-g3RDA/aws-vpn-client-login-fails-with-safari
Also seeing the issue with 3.11.1 on windows (Chrome 123) and 3.9.1 OS X (Chrome 123) - confirmed that Chrome 122 was working, tried to upgrade to 123 (lab machine) and received the SAML Assertion error.