<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
0D54z00008AXT10CAHOkta Classic EngineIntegrationsAnswered2022-10-07T20:30:03.000Z2022-10-06T22:27:31.000Z2022-10-07T20:30:03.000Z

byrond.01329 (Customer) asked a question.

Validate nonce/state tokens using OIDC authentication

I am attempting to use okta as an OIDC identity provider for a drupal application. (it will perform JIT Okta identity creation) The redirect URL is:

https://dev-XXXX.okta.com/oauth2/v1/authorize?idp={IDP_ID}&client_id={CLIENT_ID}&response_type=code&response_mode=fragment&scope=openid%20email&redirect_uri={REDIRECT}&state=123&nonce=456

 

The returned authorized payload contains values:

[state] => RXd4UkdDazFNWFlZWjFXVG5JRUpJb25FWjBjeU1ibDl2RzA3eUtwQjNyK0RkSGRWXXXXXXXXXXXXX

[nonce] => TfsUxrDnRfngYsXXXXXXXXXXX_XXXXXXX

 

I want to validate that the state/nonce values I provide are the same as being returned. My question is:

Why arent the state and nonce values the same as what i provide? and if they are encoded versions of what i provided, how can i decode them?


This question is closed.
Loading
Validate nonce/state tokens using OIDC authentication