
oocac (oocac) asked a question.
By following this link "https://developer.okta.com/docs/guides/add-an-external-idp/saml2/main/*create-an-identity-provider-in-okta" I have added one okta application as an external Identity provider. By making this request "https://${yourOktaDomain}/oauth2/v1/authorize?idp=${idp_id}&client_id=${client_id}&response_type=id_token&response_mode=fragment&scope=openid%20email&redirect_uri=https%3A%2F%2FyourAppUrlHere.com%2F&state=WM6D&nonce=YsG76jo
" I should get redirected to my redirect URL with ID token. Workflow gets completed perfectly I do get redirected to redirect_uri with token only when I am already login in okta, if I sign out from okta than instead of taking me to okta login page it shows me this "400 Bad Request; The 'redirect_uri' parameter must be a Login redirect URI in the client app settings" error. I did make sure that redirect URL is same and all the other parameters are also good. We have made a custom widget to login with okta in our application

Hello @oocac (oocac)
I hope you are having a great day
Thank you for posting, In this scenario I suggest you to take a look in the link below which explains the reason for this error and also provide the solution example.
https://support.okta.com/help/s/article/The-redirect-uri-parameter-must-be-an-absolute-URI?language=en_US
I hope this helps
Regards
Henry E.
Okta Inc
Hello Henry,
Thankyou for your reply. The request I am sending is this "https://dev-46812287.okta.com/oauth2/v1/authorize?idp=0oa40xxxx&client_id=0oa3xxxxxx&response_type=id_token&response_mode=fragment&scope=openid%20email&redirect_uri=https://beta.pubhive.com/auth/login.aspx&state=WM6D&nonce=YsG76jo"
and I have attached a screenshot of redirect URI configured in app, also I am quiet sure that idp and client Id is also correct as, if anything was wrong I should not be able to get token even if I am already login into okta as I have also mentioned in my query, is anything I am missing, correct me if I am wrong.
Thankyou
@oocac (oocac) have you able to resolve the issue? what was wrong?