AdilZ.91533 (Customer) asked a question.
Hi Everyone,
Hope you are doing good.
I have my Single Page Application using Okta-React-SDK. Now I have Updated the login initiate setting of my Single Page Application. And I'm trying login into my application through the okta my apps section (Dashboard). So that I log in to my application without entering the username password too using ID Token directly to the app (Okta Simplified).
But unfortunately, I'm unable to do this. when I click on my application through my okta app section (Dashboard). It is redirecting with "Cannot POST /login/callback". I have followed these links for Single Page Apps. And it is clearly mentioned that I can use this only in the Single Page Application. I had read these documentations at that time and planned overall things accordingly.
https://help.okta.com/en/prod/Content/Topics/Apps/Apps_App_Integration_Wizard_OIDC.htm
Actually, this Okta Simplified is one of the main features in the application so that the employee of my organization do not need to enter the password again and again. I struggling with a workaround to access and authenticate the application from the Okta My App section (Dashboard) using OKTA Simplified flow.
Guys, could you please have a look into my case. I'm really stuck in it.
Attaching snaps.
My App configuration: https://tinyurl.com/yy8x4c38
App Section/Dashboard: https://tinyurl.com/yxfzhsly
Redirection Error while clicking on App tile: https://tinyurl.com/y2h5vf3r
Thank you very much.
Adil
Hello Adil,
That is an expected behavior because the Okta Simplified flow is built to send tokens implicitly, but that is not OIDC Standard. The Standard flow stars by redirecting to the Initiate Login URI instead.
This affects your application development because our SDKs are build to work respecting the standard, and thus, the OIDC Simplified flow is intended and used by custom implementations.
You would have to modify your callback endpoint so that it supports receiving tokens without ever making a request in the first place.
I would highly recommend using the OIDC Compliant and standard flow instead, the user UX impact is relatively minimal if your Initiate Login page simply does a 302 to the /authorize flow. As the user already has an Okta session, they will just receive the tokens and continue on with the OIDC flow.
These samples can also help to compare your implementation if needed:
https://github.com/okta/samples-js-react
If you have any further questions feel free to open a support ticket with us!
Thank you,
Bogdan Andrisan
Okta Developer Support
Hello @bogdan.andrisan1.4534936759044734E12 (Okta, Inc.)
Thank you very much for the detailed response.
I have a few questions regarding this.
Looking forward to you.
Regards
Adil