Multiple apps in the same portal

[jliu]

Hmm, did not see any notification about new replies to this thread.

You are right that cookies are domain & port specific. Okta session cookie will allow the browser to log into your second app without seeing Okta login widget.

A few thoughts on why it did not work - first, Okta session cookie is session bound, it’s gone when

• The browser processes are killed, which cleans up all session cookies, or
• User clicked Okta logout link, or
• Session expired (2 hours of inactivity)

Second, it’s a puzzle that you do not see Okta session cookie. I have seen the session behavior between an Okta SAML app and Okta dashboard. Could there be anything in your app configuration that prevent session behavior/cookie?

And last, looks like this thread is related to your question:

Can I use the Okta Sign-In Widget, OIDC and normal Okta session functionality?

The primary use case is that the widget would be used to get an id_token and then it would be passed to a downstream app (App A) which would consume it and SSO the user and issue an app session token of their own. In addition, a link within App A would then trigger an SP-initiated SAML flow to another downstream app (App B). As App B can’t consume an id_token, we would need to exchange it during initial Okta auth (I would think) for an Okta session cookie. I’m relatively clear on using the foll…

Hope that helps.