About this article
This article is about how to set up SCIM (automatic user provisioning) within the Azure AD SAML2 and OpenID Connect single sign-on applications.
- Configure SCIM in Azure AD
- Assign User or User Groups to the SCIM application
- Verify the attribute mappings within the SCIM configuration
- Test SCIM using Provision on-demand
- Enable SCIM
Prerequisites
|
|
1. Configure SCIM in Azure AD
- Open the Templafy OpenID Connect or SAML2 enterprise application in Azure AD
- Navigate to the
Provisioning
tab - Select
Automatic
in the Provisioning Mode dropdown - Under the
Admin Credentials
section, fill in theTenant URL
andSecret token
- Tenant URL format is - https://[templafytenantid].api.templafy.com/v1/scim/
- The Secret token is available when creating the SCIM API key in the Templafy tenant (support article about how to create the SCIM API key)
- Click
Test connection
- Once the connection has been established, Save the configuration
- Return to the main application screen
2. Assign User or User Groups to the SCIM application
- Open the Templafy OpenID Connect or SAML2 enterprise application in Azure AD
- Navigate to the
Users and groups
tab - Click
Add user/group
on the top ribbon - Under
Users and groups
, clickNone selected
- Search for the user or group
- Click the user or group and then click the blue
Select
button - Click
Assign
3. Verify the attribute mappings within the SCIM configuration
*Note: If using SAML2 SSO, the attribute mappings in SCIM should be the same as the attributes mapped in normal single sign-on.
This is particularly important when the UPN (User Principle Name) and E-mail address are different. It is best practice to create users in Templafy with the e-mail as opposed to the UPN. This is the example I show in the video below.
- Open the Templafy OpenID Connect or SAML2 enterprise application in Azure AD
- Navigate to the
Provisioning
tab - Click
Edit attribute mappings
- Scroll down to the
Mappings
section - Click on
Provision Azure Active Directory Users
- Scroll down to the attribute mappings
- Click on the attribute you want to re-map
- In this case, I want to update the UPN to e-mail
- Under
Source attribute
, find themail
attribute and clickOk
at the bottom - Save the change
4. Mapping of custom claims
Note: Custom claims are currently only supported with the SAML2 and not with the OpenID Connect protocol. OpenID Connect does not provide custom claims attributes and will therefore overwrite the ones received via SCIM 2.0.
- Open the Templafy SAML2 enterprise application in Azure AD
- Navigate to the
Provisioning
tab - Click
Edit attribute mappings
- Scroll down to the
Mappings
section - Select
Provision Azure Active Directory Users
- Click
Add New Mapping
- Within the Target attribute choose a Templafy custom claim and select the attribute that should be send with it in the Source attribute.
5. Test SCIM using Provision on-demand
*Note: SCIM has not been enabled yet. It is important to test SCIM with a user prior to running the initial synchronization to ensure the user is successfully created in Templafy with accurate AD claim data
In order to use the Provision on demand
feature, the user must already be assigned to the application. This feature does not support provisioning of groups, only users
- Open the Templafy OpenID Connect or SAML2 enterprise application in Azure AD
- Navigate to the
Provisioning
tab - Click
Provision on demand
on the top ribbon - Search for the user you want to provision on-demand
- Select the user
- Click
Provision
After the user is provisioned, export details are shown along with other useful information about the provision including scoping, matching, and action details
6. Enable SCIM
Before enabling SCIM, make sure that the appropriate users or groups are assigned to the application. It is these users or groups that will then be added to your Templafy tenant.
-
Open the Templafy OpenID Connect or SAML2 enterprise application in Azure AD
-
Navigate to the
Provisioning
tab -
Click
Start provisioning
on the top bar
When you start provisioning, all users or groups who are assigned to the application will then be synched into your Templafy tenant. Once The initial sync is finished, you are able to check the Provisioning logs to check the status of the synch (who was synched and who was not synched).
|
Related articles
Comments
0 comments
Article is closed for comments.