Currently, our application utilizes setCookieAndRedirect to seamlessly redirect users to a new URL upon successful authentication. However, with the recent upgrade to OIE, setCookieAndRedirect has been deprecated. I’d like to explore alternative methods to achieve the same functionality.
For additional context, our application is built with React and employs the embedded sign-in widget. We have successfully enabled the interaction code flow, which is central to our authentication process.
Any guidance or recommended practices on how we can effectively redirect users after authentication under the new OIE framework
If you are currently able to complete interaction code flow, what do you need setCookieAndRedirect for? This endpoint is only used to pass a sessionToken via the /login/sessionCookieRedirect to get an Okta session cookie set on the Okta domain (which is why it is a redirect).
I typically have only seen this method used for SAML or other non OpenID Connect integrations, but since you are using Interaction Code flow successfully, then I don’t see why you would need this method?
Are you trying to facilitate SSO into a different application (other than our OIDC based React app)?
Are you trying to facilitate SSO into a different application (other than our OIDC based React app)?
Yes, basically redirect to a different application