The article addresses a warning displayed during the Okta Identity Engine (OIE) upgrade process. The following warning is shown:
OIE_UPGRADE_REQUIRED_NON_WRITABLE_ATTRIBUTES_WARN
Self-Service Registration Non writable attributes (read only, hidden, or sensitive) have been detected.
Writing to Non-Writable 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.
The warning indicates that the current (Okta Classic) Self-Service Registration policy configuration includes non-writable attributes such as Directory or Inbound Federation. If no action is taken, these attributes will be removed from the newly created profile enrollment policy and will not populate the user profile after the upgrade.
- Okta Identity Engine Upgrade
- OIE_UPGRADE_REQUIRED_NON_WRITABLE_ATTRIBUTES_WARN
The problem occurs because non-writable attributes (such as Directory or In Bound Federation) are included in the Classic Self-Service Registration policy configuration. Writing to non-writable attributes is not supported in Okta Identity Engine (OIE). These attributes will be removed from the created profile enrollment policy as part of the upgrade.
Resolve the upgrade blocker by either converting the attribute to allow "read-write" user access or by implementing an alternative method.
If the attribute must remain "read-only," implement the following alternative method:
-
Create a new attribute with "Read/Write" user access.
-
Replace the current attribute in the Self-Service Registration policy.
-
Create a Registration/Event hook that copies the new "read/write" attribute value to the original "read-only" attribute.
NOTE: The alternative method for achieving the ability to use a "read-only" attribute in Self-Service Registration requires the usage of an inline Registration Hook and/or Account Creation event hook, which can be configured in Okta Workflows.
