OKTA integration user unable to update certain ServiceNow user fields due to field-level ACL restric

deepakm29284933
Tera Contributor

Created custom integration user account in the DEV instance to create/update user records from Okta to ServiceNow. The account has been granted admin and required integration roles and is configured as a web service enabled user. but, some user table fields are not editable and updates from Okta are not being applied to those fields.

Need clarification on whether there is any role or configuration that allows the integration user to bypass field-level ACLs. Since custom is an integration/web service account, should ServiceNow allow updates through the integration despite existing ACL restrictions, or is additional configuration required to permit updates to those specific fields?


2 REPLIES 2

DeanB9201927820
Mega Sage

Since you've given Admin I would expect that any field you want to edit would pass ACL checks.


Have you tried using Access Analyzer on the Service Account to confirm it has write access to the fields in question? 

 

What information are you get from logs etc? 

 

Yes, the admin role has already been granted to the account. I understand that the issue is likely caused by field-level ACLs. but , my question is how we can allow the integration account to update those fields without disabling existing ACLs or creating additional ACL rules.

Since account  is a dedicated web service/integration account, I would expect it to be able to update user records through the integration. Is there any ServiceNow mechanism, role, property or configuration that allows a service account to bypass ACL enforcement during inbound integration transactions?

 looking for an alternative approach that would allow the Okta integration to update the restricted fields while keeping the current ACL structure intact. Is there a recommended ServiceNow best practice for this type of integration account scenario?