Skip to main content

What are the Okta Attributes and Mappings I need to Provision Hosts to Traction Guest via SCIM?

Updated over 7 months ago

This knowledge article lists the Okta attributes and mappings that you need to provision hosts to Traction Guest via SCIM. For more information on how you can integrate SCIM with your account, click HERE.



​Okta Attributes and Mappings
​

Okta Attributes

  • First name

    • Display name: Given name

    • Variable name: givenName

    • External name: name.givenName

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: Yes

  • Last name

    • Display name: Family name

    • Variable name: familyName

    • External name: name.familyName

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: Yes

  • Primary email

    • Display name: Primary email

    • Variable name: email

    • External name: emails.^[primary==true].value

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: Yes

  • Primary email type

    • Display name: Primary email type

    • Variable name: primaryEmailType

    • External name: emails.^[primary==true].type

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: No

  • Secondary email

    • Display name: Secondary email

    • Variable name: secondEmail

    • External name: emails.^[primary==false].value

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: No

  • Secondary email type

    • Display name: Secondary email type

    • Variable name: secondaryEmailType

    • External name: emails.^[primary==false].type

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: No

  • Primary phone

    • Display name: Primary phone

    • Variable name: primaryPhone

    • External name: phoneNumbers.^[primary==true].value

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: No

  • Primary phone type

    • Display name: Primary phone type

    • Variable name: primaryPhoneType

    • External name: phoneNumbers.^[primary==true].type

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: No

  • Secondary phone

    • Display name: Secondary phone

    • Variable name: mobilePhone

    • External name: phoneNumbers.^[primary==false].value

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: No

  • Secondary phone type

    • Display name: Secondary phone type

    • Variable name: secondaryPhoneType

    • External name: phoneNumbers.^[primary==false].type

    • External namespace: urn:ietf:params:scim:schemas:core:2.0:User

    • Attribute required: No

  • Organization

    • Display name: Organization

    • Variable name: organization

    • External name: organizaiton

    • External namespace: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User

    • Attribute required: No

  • Department

    • Display name: Department

    • Variable name: department

    • External name: department

    • External namespace: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User

    • Attribute required: No


​Okta Mappings
​

For mappings, there are two types:

  1. Okta User to Your SCIM App

  2. Your SCIM App to Okta User

Both are needed.

  • First name

    • Your SCIM App to Okta User

      • appuser.givenName to firstName

      • Apply mapping on user create only

    • Okta User to Your SCIM App

      • user.firstName to givenName

      • Apply mapping on user create and update

  • Last name

    • Your SCIM App to Okta User

      • appuser.familyName to lastName

      • Apply mapping on user create only

    • Okta User to Your SCIM App

      • user.lastName to familyName

      • Apply mapping on user create and update

  • Primary email

    • Your SCIM App to Okta User

      • appuser.email to email

      • Apply mapping on user create only

    • Okta User to Your SCIM App

      • user.email to email

      • Apply mapping on user create and update

  • Primary email type

    • Your SCIM App to Okta User

      • N/A

    • Okta User to Your SCIM App

      • (user.email != null && user.email != '') ? 'work' : '' to primaryEmailType

      • Apply mapping on user create and update

  • Secondary email

    • Your SCIM App to Okta User

      • appuser.secondEmail to secondEmail

      • Apply mapping on user create only

    • Okta User to Your SCIM App

      • user.secondEmail to secondEmail

      • Apply mapping on user create and update

  • Secondary email type

    • Your SCIM App to Okta User

      • N/A

    • Okta User to Your SCIM App

      • (user.secondEmail != null && user.secondEmail != '') ? 'other' : '' to secondaryEmailType

      • Apply mapping on user create and update

  • Primary phone

    • Your SCIM App to Okta User

      • appuser.primaryPhone to primaryPhone

      • Apply mapping on user create only

    • Okta User to Your SCIM App

      • user.primaryPhone to primaryPhone

      • Apply mapping on user create and update

  • Primary phone type

    • Your SCIM App to Okta User

      • N/A

    • Okta User to Your SCIM App

      • (user.primaryPhone != null && user.primaryPhone != '') ? 'work' : '' to primaryPhoneType

      • Apply mapping on user create and update

  • Secondary phone

    • Your SCIM App to Okta User

      • appuser.mobilePhone to mobilePhone

      • Apply mapping on user create only

    • Okta User to Your SCIM App

      • user.mobilePhone to mobilePhone

      • Apply mapping on user create and update

  • Secondary phone type

    • Your SCIM App to Okta User

      • N/A

    • Okta User to Your SCIM App

      • (user.mobilePhone != null && user.mobilePhone != '') ? 'mobile' : '' to secondaryPhoneType

      • Apply mapping on user create and update

  • Organization

    • Your SCIM App to Okta User

      • appuser.organization to organization

      • Apply mapping on user create only

    • Okta User to Your SCIM App

      • user.organization to organization

      • Apply mapping on user create and update

  • Department

    • Your SCIM App to Okta User

      • appuser.department to department

      • Apply mapping on user create only

    • Okta User to Your SCIM App

      • user.department to department

      • Apply mapping on user create and update
        ​

Note that there will be a default set of mappings, with many attributes that are not included in the above lists. While they do not have any effect on requests, as they are ignored by the server, they should be deleted.

Did this answer your question?