Dynamic Query Params in redirect uri using okta-auth-js library

[prathamesh.phadke]

Hi all,
In one of the scenarios we would like to pass a URL with path parameters and persists those bath parameters post login. These bath parameters are dynamically generated, and these URLs cannot be configured in Okta PKCE app.
We are using Okta-auth-js library for oidc handshake between app and okta.

example pre-login URL - localhost:3000/myparam/random12345

expected redirect uri - localhost:3000/login/callback/myparam/random12345
default redirect uri - localhost:3000/login/callback

However, post /authorize call, the additional params ‘myparam/random12345’ are stripped off / removed.

It would be great if Okta dev forum can share findings or general recommendations on how to handle this case by passing dynamic query or path parameters, pre-login and persisting them to be utilized post login using redirect URI.

[andrea]

What is your use case here? It’s not expected that a callback path would be dynamic, as the authorization server needs to know the redirect_uri it will be passed (as part of the “Login redirect URIs” within the OIDC application’s settings in Okta) before it will be accepted.