Using fromURI= for User Activation Flows while Upgrading to OIE
Dec 13, 2023
Okta Classic Engine
Okta Identity Engine
Administration
Overview
Warning: The fromURI usage of the User Activation Email Template is in a legacy format.
Customer using fromURI= for UA( user activation) (FROM_URI_USAGE_FOR_SSUA)
Upgrade Eligibility: Eligible - Consent Required
Applies To
- Okta Classic Engine
- Okta Identity Engine (OIE)
Solution
The following documentation has been identified to review as part of the preparation needed to perform the upgrade to Okta Identity Engine (OIE). Note, additional Okta features may require reconfiguration or be disabled in order to complete the upgrade.
Applies To
- FEATURE_ENG_SELF_SERVICE_REGISTRATION_READ_ONLY_BYPASS_PROGRESSIVE_PROFILING
- Upgrade Eligibility: Customer Consent Required
- Self-Service Registration Read Only attributes have been detected
- Writing
How does this blocker impact the upgrade to OIE?
Some Okta Admins may have modified the email URL that is generated when initiating the UA flow via API only. The modification includes appending the fromURI to the request to “Activation User URL” returned (in API or email template).
This feature is supported in OIE; However, depending on the method the account activation is initialized there may need to be a modification in the email template as follows:Self-Service Registration using the okta Sign-in Widget (hosted/embedded)
If using the user initiated activation/Self-Service Registration using the okta Sign-in Widget (hosted/embedded). This will impact post-upgrade integrations if any of the okta Identity Engine SDKs are used; in these cases the format of the email must be updated)
Classic:
${activationLink}?fromURI=https://yourDomain.com/pathHere
Identity Engine:
${activationLink}&fromURI=https://yourDomain.com/pathHere
API/Admin Initiated User Activation Flows
No changes to the email templates are needed to perform redirection when using:
RECOMMENDATIONS
Adopt the built-in Okta Identity Engine experience within the Okta hosted environment. This will return the user to the "Originating Application" upon completion.
