OCI journey - OIE upgrade: Identify Okta integrations and customizations#6208
Open
brentschaus-okta wants to merge 7 commits into
Open
OCI journey - OIE upgrade: Identify Okta integrations and customizations#6208brentschaus-okta wants to merge 7 commits into
brentschaus-okta wants to merge 7 commits into
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Acrolinx pass (acknowledgement->acknowledgment, Applications->Apps, etc.) plus reconciliation: restore dropped custom-domain link, fix Apps>Apps nav casing, normalize Apps API casing. Includes integration-type list shortening.
Record -> Record: so the fragment list items complete the stem. Linter terminology: app page, Sign-In Widget, classic mode.
ed64b9b to
c626bfa
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Cross-link the new OIE-upgrade discovery guide from sign-in-overview, oie-intro concept, ie-limitations, and the authn API reference. No journey (oie-upgrade-*) docs touched.
Acrolinx scoreA minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Successfully checked 6 of 6 documents. Reopen the pull request or push new changes to check again. Depending on the Acrolinx server configuration, the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
What's changed?
Adds a new OIE-upgrade guide, Identify your Okta authentication integrations and customizations, which helps customers discover and inventory every Okta integration point — redirect/hosted sign-in, embedded Sign-In Widget, custom sign-in pages, Auth.js/Okta SDKs, apps, SSWS API tokens, OAuth service apps, custom authorization servers, event/inline hooks, Okta Workflows, directory agents, and log streams — before upgrading from Classic Engine to Identity Engine. It also covers validating active usage via reports and the System Log, and mapping owners + upgrade actions.
docs/guides/oie-upgrade-identify-integrations/(guide + registration).docs/guides/index.mdandvuepress-theme-prose/const/navbar.const.js.sign-in-overview, theoie-introconcept,ie-limitations, and theauthnAPI reference. No journey (oie-upgrade-*) docs were modified — those are owned separately.Is this PR related to a Monolith release?
No. Targeting the July monthly developer docs release (code freeze June 26, 2026.07.0).
Resolves
Netlify Preview Link
Preview link