Skip to main content
druva_logo.pngDruva
|
Documentation

How can we help you?

 

Trending articles:
Druva Documentation

Change user provisioning from SCIM to AD/LDAP

  1. Last updated
  2. Save as PDF

Overview

inSync provides the option to change the user provisioning method from SCIM to AD/LDAP and vice versa, while preserving the user's backed up data. 

This section provides:

  • The detailed impact of changing the user provisioning  method from SCIM to AD/LDAP
  • The procedure to change user provisioning from SCIM to AD/LDAP
  • Next steps after changing the provisioning method from SCIM to AD/LDAP

Impact of changing the user provisioning method from SCIM to AD/LDAP 

Changing the user provisioning method from SCIM to AD/LDAP has the below impact:

  • SCIM mappings and settings used to manage users in inSync are deleted.
    UserDeploymentPg3.png
  • SCIM API token is deleted
  • SCIM app configured in the IdP will not work as its token gets deleted. Login to the IdP console and delete the Druva app used for user provisioning.

    UserDeploymentPg2.png
  • User provisioning mode for all users will be changed to Manual provisioning.

Change user provisioning from SCIM to AD/LDAP

  1. Login to inSync Management Console and go to GearIconNew.png > Settings.
  2. Open the Deployment tab. Under User Provisioning, the Provisioning Method is set as SCIM.

    SCIMtoADSettingsPg.png
  3. Click Edit to change the provisioning method. 
  4. On the Edit Settings dialog box, change the Provisioning Method to AD.

    SCIMtoADEditSettings.png
  5. Click Save.  inSync asks for a confirmation and indicates the impact of the change in user provisioning method.

    All users will be moved to manual provisioning mode and will not be mapped to an AD mapping automatically.


    SCIMtoADConfirmMsg.png
  6. Click Confirm.  A confirmation message is displayed indicating the user provisioning method successfully changed to AD.

Error preventing change in provisioning method

In a rare scenario, you may see the below error message while changing the provisioning method from SCIM to AD.

SCIMtoADErrorMsg.png

Changing the provisioning method fro SCIM to AD fails whenever this error occurs.

Resolution: Regenerate the SCIM token and reconfigure the SCIM app with the new token. Subsequently, try to change the provisioning method from SCIM to AD/LDAP again.

Next steps after changing the provisioning method from SCIM to AD/LDAP

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    This page has no tags.