How to convert DocuShare Users to LDAP Users that authenticate through Active Directory

Issue

Administering accounts takes time. Converting them using the LDAP feature means only making User account changes centrally in Active Directory (AD).

Solution

Once the LDAP feature has been configured in DocuShare and Users appear in the list of possible Users(see instructions)

Note:  For detailed instructions on How To Configure LDAP in DocuShare click the solution link listed at the bottom of this page.

1.     Log into DocuShare as admin.

2.     Click Admin Home | Account Management | LDAP Accounts.

3.     Select Convert.

4.     Chose the option to convert DocuShare to LDAP (Single User) or (Multiple Users) to do them all at once.

Note:  When using the option to convert Multiple Users, you need to choose a matching criteria. This must match on both sides for DocuShare to be able to convert the User. Options for Criteria are:

·         Email Address

·         First Name

·         Last Name

·         Phone

·         Username

Instructions on page are as follows:

Convert

• Use this page to convert existing internal domain user accounts to external domain user accounts. You must first create new user accounts in the external domain.

• Use this page to convert an existing external domain user account to an internal domain user account. After the conversion, the external domain user account still resides on the LDAP server. To purge the external account, the LDAP administrator must manually delete the account from the LDAP server.

• When you set up external accounts, be aware of how DocuShare matches internal and external accounts during multiple user DocuShare to LDAP account conversion. The value of a matching property in both the DocuShare and the LDAP accounts must be a unique value for a conversion to work correctly. If the matching values are not unique, then when you convert accounts you may inadvertently convert the wrong account. Convert matching properties are determined by those properties that were bound on the Bind User page.

Solution Published:  January 13^th, 2015

Solution ID:  1614