<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
0D54z00006zlt2jCAAOkta Classic EngineAnswered2021-06-02T11:55:35.000Z2021-06-01T22:25:08.000Z2021-06-02T11:55:35.000Z

ScottD.92454 (Customer) asked a question.

Where is the redirect_uri in the authorize request uri being set?

I'm getting a 400 Bad Request error related to the redirect_uri attribute in the authorize request URI not matching to what is set in the app settings. I have reviewed the resolution to this error in the knowledge base (https://support.okta.com/help/s/article/The-redirect-uri-parameter-must-be-an-absolute-URI) and understand that under normal circumstances, the solution would be to update the Sign-In redirect URI in the app settings, however. the issue that I have is the redirect_uri value in the authorize request uri is incorrect while the Sign-in redirect URI in the app settings is correct.

 

I'm using the custom-login example code for PHP and I can see the where the redirect_uri value is being set, however, the value that I've set it for does not appear in the authorize request URI. So, my question is... how or where does Okta obtain the redirect_uri value when it constructs the authorize request URI after a successful login?


  • ScottD.92454 (Customer)

    Turns out that the redirect_uri needed to be configured in /views/login.twig - now works like a charm!

    Selected as Best
  • ScottD.92454 (Customer)

    Turns out that the redirect_uri needed to be configured in /views/login.twig - now works like a charm!

    Selected as Best
This question is closed.
Loading
Where is the redirect_uri in the authorize request uri being set?