RajeshT.69629 (Customer) asked a question.
OIDC options
I am new to okta and my study is still in progress .
I did not understand the OIDC documentation provided in
https://help.okta.com/oie/en-us/Content/Topics/Apps/Apps_App_Integration_Wizard_OIDC.htm
If you decide that either the application or Okta can initiate the sign-in request, there are two flow options:
- Redirect to your OIDC application to start the sign-in request. This conforms to Section 4 of the OpenID Connect specification. When the end users click an Okta tile, they’re redirected to the initiate_login_uri of the client application. The client application constructs an authorization request and redirects the end user back to Okta.
- Send an ID token directly to your OIDC application. This is a simpler flow, where Okta creates an ID token and posts it directly to the first redirect URI registered for the target application. This flow is the same as with sign-in requests for SAML apps. You can configure which OIDC scopes to grant. This flow uses the form_post response mode. There's no state parameter included in the request since it’s a one-way request.
Hello @RajeshT.69629 (Customer) Thank you for reacting out to our Community!
By default the OIDC application does not have the option for IDP initiated login, and this part here explains how to make the application work both IDP initiated and SP initiated at the same time.
Additionally if you need further assistance we recommend to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
https://devforum.okta.com/
Community members help others by clicking Like or Select as Best on responses. Try it today.
Okta Identity Engine (OIE) Ask Me Anything: Get answers from product experts by clicking here.
Thanks Paul !!!