You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Okta requires the OAuth 2.0 state parameter on all requests to the /authorize endpoint to prevent cross-site request forgery (CSRF). The OAuth 2.0 specification requires (opens new window) that clients protect their redirect URIs against CSRF by sending a value in the authorize request that binds the request to the user-agent's authenticated state. Using the state parameter is also a countermeasure to several other known attacks as outlined in OAuth 2.0 Threat Model and Security Considerations (opens new window).
To Reproduce
Enable PKCE flow using enablePKCEAuthentication & hook it up to your Okta instance. Start login flow from the Argo main page, and you will see a 400 with message "authentication request has an invalid 'state' parameter".
Checklist:
argocd version
.Describe the bug
The current PKCE flow introduced in #15889 does not set the
state
parameter (thank you very much for the feature @Marvin9 🙏).This results in a
400
when using Okta as the provider becausestate
is a required parameter.In their docs (https://developer.okta.com/docs/reference/api/oidc/#parameter-details):
To Reproduce
Enable PKCE flow using
enablePKCEAuthentication
& hook it up to your Okta instance. Start login flow from the Argo main page, and you will see a400
with message "authentication request has an invalid 'state' parameter".Expected behavior
Login flow completes successfully.
Screenshots
(sorry this was on another person's laptop)
Version
Logs
The text was updated successfully, but these errors were encountered: