ServiceNow Locked Status Attribute During Okta Provisioning Flow
Last Updated:
Okta Integration Network
Okta Classic Engine
Okta Identity Engine
Overview
One user or multiple users have been reassigned to the ServiceNow app in Okta. On the ServiceNow side, the accounts are in a Locked status.
Applies To
- ServiceNow
- Provisioning
- Locked Users
Cause
When a user is unassigned from the ServiceNow App in Okta, the user gets deactivated and locked out of ServiceNow. When the user is reassigned to the app in Okta, the user gets activated in ServiceNow, but is still locked out as the Locked Out attribute is not selected from the schema and is not mapped to any value in Okta.
Solution
Add the Lockout attribute from the Schema in Okta and send a value of FALSE.
- Go to Directory > Profile Editor in Okta
- Find the ServiceNow application instance.
- Click on the Profile. Select the Add Attribute and search for the
LockedOutattribute.
- Now go to Mappings and select the Okta to ServiceNow tab at the top.
- Find the Locked Out attribute and map it to the string
'false'. This will also work if we set a blank value in the user profile.
