<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A3g7r2CQAOkta Classic EngineAuthenticationAnswered2025-10-28T09:03:10.000Z2024-03-20T13:13:59.000Z2024-03-20T18:53:57.000Z

MadsZ.17237 (Customer) asked a question.

Newest Chrome update 123.0.6312.59 has broken multiple saml authentication flows

Have anyone else experienced that their saml authentication to specific apps has stopped working completely or partly after updating to the newest chrome version 123.0.6312.59?


  • qla7b (qla7b)

    Same issue here, when authenticating to AWS Client VPN. Raised a P1 with Okta support. Provided SAML Tracer and HAR file, but they determined the issue wasn't Okta related. Issue still occurred when using password only (no Okta Verify for MFA). Additionally filed tickets with AWS and Google.

     

    You can attempt to manage/block/rollback updates if your Chrome Browsers are managed: https://support.google.com/chrome/a/answer/9838774?hl=en#zippy=

    Expand Post
This question is closed.
Loading
Newest Chrome update 123.0.6312.59 has broken multiple saml authentication flows