<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
0D51Y00008j7DILSA2Okta Classic EngineSingle Sign-OnAnswered2020-06-22T18:39:44.000Z2020-06-15T17:51:14.000Z2020-06-22T18:39:44.000Z

RajeshR.03197 (Customer) asked a question.

Need Help - 400 Bad Request; The 'redirect_uri' for https

Have created app TCC, in this I have given redirect uri as https scheme, then while access login link it redirect to http schema only. Why it is not supporting https.

Can you please advise.


  • User15834064865797313461 (Vendor Management)

    Hi Rajesh,

    From what I gathered you are having issues with an OIDC app, where the value of the redirect uri is not registered in the OpenID Client in Okta. Here are the resources I have found on the matter:

    <<In the following example authorize request

     

    https://example.okta.com/oauth2/v1/authorize?client_id=0oais56vveNLSDqby0x7&scope=openid+profile&response_type=id_token&response_mode=fragment&nonce=1234&redirect_uri=

    http://localhost:8888/my-app/signin.html/&state=someState

     

    Make sure that redirect _uri = http://localhost:8888/my-app/signin.html/​ is registered as an allowed Login Redirect URI in Open ID Client (using client id 0oais56vveNLSDqby0x7 in the example above)

    1. From the Applications page of the Okta Admin Console, click on your OpenID application
    2. In the General tab, click Edit and add http://localhost:8888/my-app/signin.html/​ to the Login Redirect URI. Make sure the redirect URI in Open ID client matches exactly: for example, if there is a trailing slash (/) that is also added to the url, otherwise you will still get the error. 
    3. Click Save and General settings should look like:

    rtaImage>>

    Have a great day!

    Expand Post
This question is closed.
Loading
Need Help - 400 Bad Request; The 'redirect_uri' for https