Important Update: Cohesity Products Knowledge Base Articles


All Cohesity Knowledge Base Articles are now managed via the Cohesity Support Portal: https://support.cohesity.com/s/searchunify. The Knowledge Base articles available here will not reflect the latest information or may no longer be accessible.

How to provision users using SCIM in Alta Archiving

Article: 100059182
Last Published: 2024-10-29
Ratings: 0 0
Product(s): Veritas Alta Archiving

Description
 

Users can be provisioned in Alta Archiving using System for Cross Domain Identity Management(SCIM). SCIM leverages an Enterprise Application in Azure AD to provision users in Alta Archiving. 

Provisioning using SCIM is not enabled by default for any company in Alta Archiving. Please contact Veritas Support to enable this option for your company.

Note: Currently, users will have Archiving and Personal Archive enabled using the SCIM method.  If this is not desired, using the O365 sync method will allow for additional options.  

Once enabled, use the following steps to configure SCIM. 

1. Login to the Alta Archiving Administration console and navigate to Configuration | User Management

2. Click the Generate SCIM Token option. A SCIM token is required to be generated to connect to our hosted SCIM app via Azure AD app.



3. Once the token is generated, copy it so it can be used in the Azure AD application configuration.

3. Next, login to the Azure AD admin center (Microsoft Entra admin center) and navigate to Applications | Enterprise Applications

4. Click on New Application | Create your own application. Enter the name of the application and click on Create once the options are selected as below. 

5. Once the application is created, navigate to Provisioning section and then click Get started


 

6. Set the Provisioning Mode as Automatic. Set the Tenant URL based upon the datacenter used by your company. Refer the table below for Tenant URL to be used. 

Datacenter Tenant URL
UKS01 https://scim.uk1.archivecloud.net/scim
USW03 https://scim.us3.archivecloud.net/scim
EUW01 https://scim.ams.archivecloud.net/scim
AUE02 https://scim.au2.archivecloud.net/scim
CAC01 https://scim.ca1.archivecloud.net/scim


In the Secret Token section, paste the token copied in Step 3 and click Test Connection

7. Upon successful validation, the below notification will be seen. Next, click on Save.

8. Go to Mappings and set Provision Azure Active Directory Groups to No as this is not supported in Alta Archiving. 


9. Next, click Provision Azure Active Directory Users to create the Attribute Mappings. Add a new attribute to the attribute mapping by selecting Show advanced options | Edit attribute list for customappsso. 



10. Add the following attribute:urn:ietf:params:scim:schemas:extension:veritas:2.0:User:emailAliases as a String and ensure the Multi-Value flag is checked as seen below. 



11. Next, add a new attribute by clicking on Add New Mapping. Select the Source attribute proxyAddress and set the Target attribute as urn:ietf:params:scim:schemas:extension:veritas:2.0:User:emailAliases.

12. The final attribute list should look like below.



13. Add the user(s) whose archive(s) need to be provisioned in Alta Archiving to this app from the Users and groups section.



14. To provision the users, navigate to Provisioning section of the application. Click Provision on demand, select the user from the list and click on Provision



15. The provisioning job will run and show the status as below when complete. 


16. Verify the archive has been created in Alta Archiving Administration console under Configuration > Account Management. 

Note: Ensure all accepted domain(s) of the company are added to Alta Archiving, before provisioning users via SCIM. 

 

References

JIRA : EVCSRE-60836

Was this content helpful?