Documentation on how to enable `state` parameter

Hi Team,

We’re trying to determine if state OAuth2 parameter can be auto-generated and verified by this library, or if this is something that the client should implement on their own. Do you have any clarifying documentation on it?

Thank you

[pamapa]

hmmm when i call auth.signinRedirect() here i get:

https://<server url>?client_id=<client id>&redirect_uri=<encoded redirect url>&response_type=code&scope=openid&state=<the state>&code_challenge=<code challenge>&code_challenge_method=S256&response_mode=query
...
https://<redirect url>?code=<code>&state=<same state as above>
...

The state is something like c990e16feb674bf19a3932919394bbe4.

As the auth process will ping/pong, the application will be run multiple times in the same browser tab, to see anything you need to enable “Preserve log” in the network browser tab of the DevTools…

If you still have issues, please provide logs of the network tab and of the oidc-client-ts by enabling logging via: Log.setLogger(console); Log.setLevel(Log.DEBUG); + “Preserve log” in the browser console tab of the DevTools.

[dinvlad]

@pamapa thanks again - I think the confusion on our side was because the state property on the user object is different, as you mentioned. We do see state request param passed in both of the URLs, however, so all is good!