Supported attributes reference
The following standard attributes can be mapped for user provisioning to PingOne. Custom attributes can also be created and mapped if desired.
Learn more about authentication device attributes and synchronization behavior in Authentication method management.
| Attribute | Description | ||
|---|---|---|---|
Username |
A unique identifier for the user in PingOne. This attribute is required. |
||
The user’s email address, which must be valid (for example, "jsmith@example.com"). This attribute is required. |
|||
Population ID |
The connector provisions users to this PingOne population. This attribute is required. Select a population name from the Default value list, or map a dynamic population ID.
|
||
Account ID |
The user’s account ID. This attribute can be an organization-specific identifier. |
||
Authoritative IdP |
The external identity provider for the user. This is used for identity provider discovery. Learn more in Identifier first action in the PingOne API documentation. |
||
City |
The city or locality component for the user’s mailing address. |
||
Country |
The country name component. When specified, the value must be in |
||
External ID |
A string that’s an identifier for the resource as defined by the provisioning client. The attribute can simplify the correlation of the user in PingOne with the user’s account in another system of record. |
||
First Name |
The user’s given name or first name in most Western languages (for example, 'Barbara' given the full name 'Ms. Barbara Jane Jensen, III'). |
||
Force Change Password |
Indicates if the user is forced to change their password at next log in. Valid values are |
||
Full Name |
The user’s full name, including all middle names, titles, and suffixes as appropriate, formatted for display (for example, 'Ms. Barbara Jane Jensen, III'). |
||
Honorific Prefix |
The user’s honorific prefix, or title in most Western languages, (for example, 'Ms.' given the full name 'Ms. Barbara Jane Jensen, III'). |
||
Honorific Suffix |
The user’s honorific suffix or suffix in most Western languages (for example, 'III' given the full name 'Ms. Barbara Jane Jensen, III'). |
||
Job Title |
The user’s title, such as "Vice President". |
||
Last Name |
The user’s family name or last name in most Western languages (for example, 'Jensen' given the full name 'Ms. Barbara Jane Jensen, III'). |
||
Locale |
Used to indicate the user’s default location for purposes of localizing such items as currency, date time format, or numerical representations. A valid value is a language tag as defined in RFC 5646, such as |
||
MFA Device Email 1 MFA Device Email 2 MFA Device Email 3 |
An email address that the user has paired with the PingOne MFA service. |
||
MFA Device Policy ID |
The ID of a PingOne MFA policy. When set, the provisioner uses the specified policy when pairing MFA devices during provisioning, instead of the default policy. When left blank, the provisioner uses the environment’s default MFA device policy. Learn more in MFA policies in the PingOne documentation. |
||
MFA Device SMS 1 MFA Device SMS 2 MFA Device SMS 3 |
An SMS phone number that the user has paired with the PingOne MFA service. You must enter a valid phone number in international format, including the leading
The following list contains a few examples of valid ways to format the phone number:
|
||
MFA Device Voice 1 MFA Device Voice 2 MFA Device Voice 3 |
A voice phone number that the user has paired with the PingOne MFA service. You must enter a valid phone number in international format, including the leading
The following list contains a few examples of valid ways to format the phone number:
|
||
MFA Enabled |
When the value is |
||
Middle Name |
The user’s middle name (for example, 'Jane' given the full name 'Ms. Barbara Jane Jensen, III'). |
||
Mobile Phone |
The mobile phone number for the user. This value must consist of a leading plus sign, 1 to 3-digit country code, dot separator, 4 to 14-digit phone number, and optional 1 to 8-digit extension (for example, '+1.3034682900x1234'). |
||
Nickname |
The casual way to address the user, such as "Bob" instead of "Robert". |
||
Password |
The user’s password. Passwords must match the Password Policy configured in PingOne. |
||
Preferred Language |
Indicates the user’s preferred written or spoken languages and is generally used for selecting a localized user interface as defined in RFC 7231, such as |
||
Primary Phone |
The primary phone number for the user. This value must consist of a leading plus sign, 1 to 3-digit country code, dot separator, 4 to 14-digit phone number, and optional 1 to 8-digit extension (for example, '+1.3034682900x1234'). |
||
Profile Image |
The user’s photo URL. A URI that is a uniform resource locator (as defined in section 1.1.3 of RFC 3986) that points to a resource location representing the user’s image. If provided, the resource URL must point directly to the image (for example, a GIF, JPEG, or PNG) rather than a web page containing an image. It must also have a scheme of HTTP or HTTPS. |
||
State / Region |
The state or region component for the user’s mailing address. |
||
Street Address |
The full street address component, which can include house number, street name, P.O. box, and multi-line extended street address information. |
||
Timezone |
The user’s time zone. This must be in IANA Time Zone database format as defined in RFC 6557, such as “America/Los_Angeles”. |
||
User Type |
Used to identify the relationship between the organization and the user. Typical values used might be "Contractor", "Employee", "Intern", "Temp", "External", and "Unknown", but any value can be used. |
||
ZIP Code |
The ZIP or postal code component for the user’s mailing address. |