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 to read-only attributes is not supported in Okta Identity Engine.  These attributes will be removed from the created profile enrollment policy as part of the upgrade; thus will no longer be populated by the user during registration.  If you do not know which attributes are impacted, contact support. 

How does this blocker impact the upgrade to OIE?

In the current (Classic) Self-Service Registration policy configuration, there are read-only attributes included. This was enabled via an additional feature.
if no action is taken, these attributes will be removed from the newly created profile enrollment policy; thus will not populate the user profile post-upgrade;

How do I remediate this blocker?

Convert attribute to allow for users to "read-write"
   or
Implement an alternative method
 

Alternative Method for achieving the ability to use a "Read-only" attribute in Self-Service Registration would require the usage of an inline Registration Hook And/OR Account Creation event hook; Either of these triggers could be configured in Okta Workflows.

High-Level steps to prepare a "read-only" attribute for self-service registration upgrade:
1: Create a new attribute with "Read/Write" user access;
2: Replace the current attribute in the Self-Service Registration policy.
3: Create a Registration/Event hook that will copy the new attribute "read/write" value to the original "read-only"