ServiceNow Provisioner

Supported attributes reference

The following attributes can be mapped for user provisioning to ServiceNow.

For more information about these attributes, see Create a user in the ServiceNow documentation.

Attribute Description

UserName

The user’s unique identifier in ServiceNow.

This attribute maps to the user’s user_id in ServiceNow. The ServiceNow Provisioner uses this value to synchronize pre-existing users in ServiceNow with the data store.

This user attribute is required for provisioning. It must be unique and is not cannot be updated. For more information, see Known issues and limitations.

First name

The user’s given name. For example, "Barbara" in "Ms. Barbara Jane Jensen, III".

Last name

The user’s family name. For example, "Jensen" given the full name "Ms. Barbara Jane Jensen, III".

Middle name

The user’s middle name or names. For example, "Jane" given the full name "Ms. Barbara Jane Jensen, III".

Prefix

The user’s honorific prefix or prefixes, such as "Ms.", "Mr.", or "Dr." This attribute maps to the user’s "introduction" in ServiceNow.

Gender

The user’s gender.

Email

The user’s email address.

Title

The user’s business title, such as "Software engineer".

Department

The user’s department or work group, such as "Sales".

Password

The user’s password. Passwords cannot be mapped from a source data store, so this field can be used to set a literal default value.

Password Needs Reset

When set to true, the user must change their password at next login.

Language

The user’s language. Uses the two-character language code as defined by the ISO 639-1 standard.

This attribute has a default value in ServiceNow. Languages might need to be updated in ServiceNow to account for other allowable values for this field.

Location

The user’s geographical location.

Photo

The user’s photo.

Business Phone

The user’s business phone number.

Mobile Phone

The user’s mobile phone number.

Home Phone

The user’s home phone number.

Street

The user’s street address.

City

The user’s city or locale.

State/Province

The user’s state, province, or territory.

Zip/Postal Code

The user’s ZIP or postal code.

Country Code

The user’s country. Uses the two-character country code as defined by the ISO-3166-1 alpha-2 standard.

This attribute has a default value in ServiceNow. County Codes might need to be updated in ServiceNow to account for other allowable values for this field.

Roles

The user’s role, such as "Student" or "Faculty".

This attribute supports multiple values.

The ServiceNow Provisioner can only assign roles that are already assigned to the user account that you use for provisioning.

The ServiceNow Provisioner does not create new roles, so the roles must already exist in ServiceNow.

By default, the ServiceNow Provisioner can set roles but not remove them. To remove this limitation, you can grant elevated security permissions, as shown in Adding the Ping Identity provisioning role in ServiceNow.

Notification

Determines whether to enable notifications. Select Enable or Disable.

Employee Number

A string identifier, typically numeric or alphanumeric, assigned to a person, often based on order of hire or association with an organization.

Time Zone

The user’s time zone. Uses IANA time zone database format. For example, "America/Los_Angeles".

The ServiceNow Provisioner can only set time zones that are already assigned to the user account that you use for provisioning. The time zone might need to be updated in ServiceNow to account for other allowable values in this field.

Time Format

The user’s time format. For details on time formatting, see Global date and time field format in the ServiceNow documentation.

The ServiceNow Provisioner can only set time formats that are already assigned to the user account that you use for provisioning.

Manager

The distinguished name (DN) representing the manager for the user.

During the first synchronization between ServiceNow and your data store, you might see errors in provisioner.log because the manager for a user has not been provisioned yet. The user is still created without the manager attribute. On the next retry, the manager will exist and the user’s manager attribute will be updated.

This attribute is not supported in PingFederate 9.0 and 9.0.1.