<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
0D54z00006xKwFSCA0Okta Classic EngineAnswered2024-07-18T09:00:09.000Z2021-05-08T07:58:11.000Z2021-05-11T16:25:44.000Z

rppqa (rppqa) asked a question.

Pass through a GET variable from login page through to the redirect_uri

Hi there, we want it to be possible for our developers to test out their features on the staging instance of our application, by appending ?branch=my-git-branch-feature-foo to the url of the site.

 

What happens is that the Okta login page loads up correctly (with the "branch" param in the URL) and after the successful login they are sent to the redirect_uri, at which point the "branch" parameter in the URL is gone.

 

Ideally there would be a way for the okta login widget to retain the branch parameter throughout the login flow.

 

I see that there's a setting in okta where we can specify the allowed redirection URLs, and if we hardcode the branch name in there it should work - but that means having lots of redirection URLs configured in okta (one per feature-branch) which seems difficult and error-prone to administrate.

 

Any thoughts on how we can pass through this parameter?

 


  • User15840128127994021225 (Vendor Management)

    Andreea here on behalf of Okta's Customer Support Team, thank you for posting the question!

     

    Please open a case with our Developers Support Team to further discuss the issue.

     

    Thank you!

    Expand Post
This question is closed.
Loading
Pass through a GET variable from login page through to the redirect_uri