Configuring ServiceNow

Regular user accounts in ServiceNow can send heartbeat signals but are unable to manage RPCs. A ServiceNow account capable of changing passwords needs the standard ServiceNow admin role, or a custom role with permissions to modify the sys_user.user_password field.

It is advisable to set up a privileged ServiceNow account with these permissions within ServiceNow, and designate it as the Privileged account in the Secret Server.

To configure a Privileged account in Secret Server:

1. Log into Secret Server with the admin account.

2. Go to Administration > Remote Password Changing.

3. Select a ServiceNow RPC.

4. Change password using the Privileged account credentials.

5. Save the changes.

Creating a role

ServiceNow provides a built-in admin role that allows you to manage your password changes via the REST API.

To create a new role in ServiceNow:

1. Open the Service Now instance.

2. Go to User Administration > Roles and create a new role. Name it appropriately, such as "Password Change Role."

3. Save the changes.

Providing Level Access

To provide a required level of permissions to a role:

1. Access Security Rules > ACLs in the ServiceNow instance.

2. Locate the ACL for the user_password field in the sys_user table.

3. Edit the ACL to grant both read and write access for the newly created role.

4. Save the changes.

Assigning a Role

To assign a role to the appropriate group of users:

1. Go to User Administration > Users and select the users whose passwords need to be changed using the REST API.

2. Assign the newly created role to these users.

3. Save the changes.

Verifying Role Configuration

To check that you have configured a role in ServiceNow correctly:

1. Utilize the REST API for password change operations as required.

2. Verify that the password change functionality works as expected for users with the assigned role.

3. After changing the password using the REST API, attempt to log in to the ServiceNow portal using the updated credentials for validation.