Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view

This file was deleted.

This file was deleted.

1 change: 0 additions & 1 deletion packages/@okta/vuepress-site/docs/guides/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,6 @@ guides:
- oie-upgrade-sign-in-widget
- oie-upgrade-sign-in-widget-styling
- oie-upgrade-mfa-enroll-policy
- ie-limitations
- authenticators-overview
- authenticators-google-authenticator
- authenticators-web-authn
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ meta:

<ApiLifecycle access="ie" />

Okta uses an HTTP session cookie to provide access to your Okta organization and applications across web requests for interactive user agents such as a browser. The Okta [Sessions API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Session/) provides operations to create and manage authentication sessions for users in your Okta org.
Okta uses an HTTP session cookie to provide access to your Okta org and apps across web requests for interactive user agents such as a browser. The Okta [Sessions API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Session/) provides operations to create and manage authentication sessions for users in your Okta org.

After your org is upgraded to Okta Identity Engine, there are a few things you should know about how sessions work with Identity Engine:

Expand All @@ -34,4 +34,8 @@ The following section discusses different use cases and what the changes are aft

4. **Are you making this request (POST `/api/v1/sessions?additionalFields=cookieToken`) using the Sessions API?** This operation works only on the session ID (`sid`) session and not on the Identity Engine `idx` session.

If you're using this endpoint, Okta highly recommends that you move away from using the session ID entirely and use the [My Session Management endpoints](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Session/#tag/Session/operation/getCurrentSession) instead. This puts you in charge of managing your own session.
If you're using this endpoint, Okta highly recommends that you move away from using the session ID entirely. Use the [My Session Management endpoints](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Session/#tag/Session/operation/getCurrentSession) instead. This puts you in charge of managing your own session.

5. **Did a user authenticate in Classic Engine before the upgrade was completed?** If a user authenticates in Classic Engine, they receive a sessionToken that remains valid for five minutes. If the upgrade to Identity Engine completes while this sessionToken is still valid, the user's existing session becomes invalid. When the user attempts to access an OpenID Connect app after the upgrade, they’re prompted for their password again.

> **Note:** This scenario only happens during an upgrade from Classic Engine to Identity Engine. It doesn't continue to happen after the upgrade.
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Work with Okta session cookies
---

> **Note:** This page provides information on Okta Classic Engine. If you're using Okta Identity Engine, see [Understand how sessions work after the upgrade](/docs/guides/oie-upgrade-sessions-api/) and this [Sessions APIs](/docs/guides/ie-limitations/main/#sessions-apis) section. See [Identify your Okta solution](https://help.okta.com/okta_help.htm?type=oie&id=ext-oie-version) to determine your Okta version.
> **Note:** This page provides information on Okta Classic Engine. If you're using Okta Identity Engine, see [Understand how sessions work after the upgrade](/docs/guides/oie-upgrade-sessions-api/) and this [Sessions APIs](/docs/guides/oie-upgrade-sessions-api/main/) section. See [Identify your Okta solution](https://help.okta.com/okta_help.htm?type=oie&id=ext-oie-version) to determine your Okta version.

This guide provides examples for retrieving and setting a session cookie for different deployment scenarios. With these scenarios, you can provide SSO capabilities for custom web apps built on Okta.

Expand Down
4 changes: 0 additions & 4 deletions packages/@okta/vuepress-theme-prose/const/navbar.const.js
Original file line number Diff line number Diff line change
Expand Up @@ -564,10 +564,6 @@ export const guides = [
title: "Plan embedded app upgrades",
guideName: "oie-upgrade-plan-embedded-upgrades",
},
{
title: "Identity Engine limitations",
guideName: "ie-limitations",
},
{
title: "Okta Sign-In Widget upgrade",
subLinks: [
Expand Down