How to set the default login domain

Note: This solution applies to DocuShare 5.x, 6.x, 6.5.x, and 6.6.x only. Solution

This solution will change the default login domain from the internal DocuShare domain to another (internal DocuShare or external LDAP) domain..

Note: You must be a Windows Administrator to perform this solution.

Note: This solution will require a restart of the DocuShare Service.

Prerequisite:

• The domain must already be created by the DocuShare Administrator.

To set the default login domain:

Note: DocuShare 7.x has built-in GUI support on the Administration page for detailed instructions click th How to set the default login domain in DocuShare 7 solution link listed at the bottom of the page.

1. Open Windows Explore and Open the <dshome>\config folder.

    

   Where <dshome is replaced with the installation directory for DocuShare.  The default installation path is C:\Xerox\DocuShare. Depending on your installation environment the path may vary.

    

2. Make a copy of the dscommon.properties file and name it dscommon.properties.bak.

    

3. Open the dscommon.properties file in a text editor.

    

4. Add the following entry at the top or bottom of the file.

    

   defaultLoginDomain=yourdomainname

    

   Note: Where yourdomainname is your external domain name.

    

   Note: The domain name you enter must match the spelling (case sensitive) that shows up in the Domain pull down menu on the DocuShare Home page.

    

   Note: If the domain name conatins extended character set, for example, Japanese Kanji characters ("技開本") - all the characters must be entered as escaped Unicode encoded characters ("defaultLoginDomain=\u6280\u958B\u672C").

    

   Note: Refer to external web sitehttp://unicode.org/charts/for mappings of Unicode character names to character codes.

    

5. Restart DocuShare for the changes to take effect.

    

   Note: When logging in as DocuShare admin, you will need to change the domain to DocuShare from the Domain pull down menu.

Solution Updated: May 25, 2015

Solution ID: 331