OpenText™ Content Server

OpenText™ Directory Services

Integration Administration

The Directory Services Integration administration page in

Content Server is used to configure how users will authenticate
with Content Server.

LLESDSI220100-AGD-EN-02
OpenText™ Content Server
OpenText™ Directory Services Integration Administration
LLESDSI220100-AGD-EN-02
Rev.: 2021-Dec-02
This documentation has been created for OpenText™ Content Server CE 22.1.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com

Copyright © 2021 Open Text. All Rights Reserved.

Trademarks owned by Open Text.

One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
 Table of Contents
1 Configuring Directory Services Integration ............................ 5
1.1 Configuring Directory Services ........................................................... 5
1.2 Configuring Directory Services Internal Process Settings ..................... 6
1.3 Configuring Integration Settings ......................................................... 8
1.4 Explaining the OTDS-specific Content Server installation pages ......... 14
1.5 Your Directory Services installation and Content Server .................... 17

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration iii

Chapter 1
Configuring Directory Services Integration

OpenText Directory Services is an integral part of Content Server, and handles all
authentication for Content Server. During the installation of Content Server, the
administrator chose to install a particular version of Directory Services:

Internal OTDS
If your administrator selected an internal version of OTDS during the
installation of Content Server, you will be accessing the version of OTDS that
shipped with the Content Server installation files.
The internal OTDS installation creates and makes use of a Content Server
process in the System Object Volume. You can access this process directly from
the Content Server administration page, under the Directory Services
Integration Administration heading, click Configure Directory Services
Process. For more information about this process, see “To Edit an Internal OTDS
Process” on page 7.

Important
OpenText recommends the use of an external OTDS installation in order to
take advantage of high-availability capabilities.

Once you have completed the installation process for Content Server, you can
switch from an internal installation of OTDS to an external installation. For more
information, see “To Change from an Internal Installation of OTDS to an
External” on page 12.
External OTDS
If your administrator selected an external version of OTDS during the
installation of Content Server, you will be accessing a version of OTDS
downloaded from OpenText My Support (https://knowledge.opentext.com/go/
OTDS).

1.1 Configuring Directory Services

Directory Services is configured using the OTDS web administration user interface.
Selecting the Directory Services Integration Administration > Configure Directory
Services option from the Content Server administration menu will bring up the
OTDS web admin UI in a separate tab or window.

To sign in to Directory Services

To sign in to Directory Services:

1. In the Content Server administration page, under the Directory Services

Integration Administration heading, click Configure Directory Services.

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration 5

Chapter 1 Configuring Directory Services Integration

2. A new, separate page will open. This is the sign in page to either the internal or
the external OTDS user interface. By default, the user name is
“[email protected]”.
If you are signing in to the internal OTDS user interface, the password is the one
selected by your administrator during the installation of Content Server. When
signing in to the internal OTDS user interface, you can also use the Content
Server “Admin” userid.
If you are signing in to the external OTDS user interface, the password is the
one selected by your administrator during the installation of OTDS.
Enter your user name and password, and then click Sign in.

3. You can access the help for OTDS from the OTDS user interface by clicking the
help button at the top of the main page.
For more information on OpenText Directory Services, see OpenText Directory
Services - Installation and Administration Guide (OTDS-IWC) on OpenText My
Support (https://knowledge.opentext.com/go/OTDS). Select Documentation.

1.2 Configuring Directory Services Internal Process

Settings
When Directory Services is installed as an internal process of Content Server, an
Internal OTDS process is installed to the System Object Volume.

Editing the internal OTDS process

The internal OTDS server uses a Jetty web and servlet server that is built into
Content Server. By default, the internal OTDS server uses a self-signed
certificate for HTTPS communications, but you can configure it to use a different
certificate by entering appropriate values in the Java Key Store settings in the
HTTPS Configuration area. For more information on configuring Jetty to use a
specific certificate, refer to the Jetty documentation.

Tip: Documentation for Jetty, which is a third-party software component,

is publicly available. For example, for information on creating a Java
keystore, visit http://www.eclipse.org/jetty/documentation/current/
configuring-ssl.html.
Deleting the internal OTDS process
If you have been using an internal installation of OTDS and you intend
switching to an external installation, you may want to delete the Internal OTDS
process.

6 OpenText™ Content Server LLESDSI220100-AGD-EN-02

 1.2. Configuring Directory Services Internal Process Settings

1.2.1 To Edit an Internal OTDS Process

To edit an internal OTDS process from the OTDS menu item:

1. Sign in to Content Server as the administrator. Under the Directory Services

Integration Administration heading, click Configure Directory Services
Process.

2. If you want to edit the ports that your internal installation of OTDS is using:

a. On the Internal OTDS page, under the Actions area, click Stop.
You will be returned to the administration page, click Configure Directory
Services Process.
b. On the Internal OTDS page, you can optionally change any of the port
fields. OpenText recommends that you do not edit any fields, other than
the port fields, unless directed by OpenText support.
c. Click Update.
d. Under the Actions area, click Start.

To Edit an Internal OTDS Process from the Process folder:

1. Sign in to Content Server as the administrator. Under the Search

Administration heading, click Open the System Object Volume.

2. On the System page, click Process Folder.

3. If you want to edit the ports that your internal installation of OTDS is using:

a. From the Internal OTDS functions menu, select Stop.

b. Now, also from the Internal OTDS functions menu, select Specific from
the Properties menu.
c. On the Internal OTDS page, you can optionally change any of the port
fields. OpenText recommends that you do not edit any fields, other than
the port fields, unless directed by OpenText support.
d. Click Update.
e. On the Process Folder page, from the Internal OTDS functions menu,
select Start.

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration 7

Chapter 1 Configuring Directory Services Integration

1.2.2 To Delete an Internal OTDS Process

To delete an internal OTDS Process:

1. Sign in to Content Server as the administrator. Under the Directory Services

Integration Administration heading, click Configure Directory Services
Process.

Tip: You can also access this page from the Content Server administration
page. Under the Search Administration heading, click Open the System
Object Volume. On the System page, click Process Folder.

2. If you want to delete your internal OTDS process, from the Internal OTDS
functions menu, select Delete.

Caution
Do not delete the Internal OTDS process if you intend to continue
using the version of Directory Services that installed as part of the
installation of Content Server. Only delete this process if you have an
externally installed and configured version of Directory Services.

3. Confirm that you want to delete this process.

1.3 Configuring Integration Settings

The Directory Services Integration Settings page in Content Server is used to
configure how users will authenticate with Content Server. Content Server supports
Single Sign On (SSO) and authentication services provided by either an internal or
an external installation of OTDS.

You can configure the following authentication options:

Web Server Authentication

You can choose to enable Web Server Authentication to retrieve authenticated
user information directly from your Web Server. You would enable this option if
your Web Server is configured to authenticate users as they access Content
Server URLs. For example, if you are using Microsoft Internet Information
Services (IIS), your server may be configured to authenticate users with
Integrated Windows Authentication (IWA), in which case IIS will populate the
Web Server environment variable REMOTE_USER with the account name of the
authenticated user. The format of <username> can be supplied and configured as
detailed below.
Environment Variable
The Environment Variable parameter allows you to choose which variable
to use for determining the user name. By default, this will be set to REMOTE_
USER. Other authentication schemes may set Environment Variable to a
different value, such as Siteminder, which uses the value HTTP_SM_USER.

8 OpenText™ Content Server LLESDSI220100-AGD-EN-02

 1.3. Configuring Integration Settings

Username Formatting
The Username Formatting area allows you to select how to format the value
in the above environment variable.

• Remove domain name: this will display the user name only. Choose this
option if uniqueness of user names is guaranteed across all domains in
your Windows domain registry. This is the default selection.
• Do not format: this will leave the user name unchanged. Choose this
option if uniqueness of user names is guaranteed only within each domain
in your Windows domain registry.
• Resolve through OTDS: the value from REMOTE_USER is sent to OTDS in
order to find the corresponding user name in Content Server. You must
configure OpenText Directory Services. For more information, see
OpenText Directory Services - Installation and Administration Guide (OTDS-
IWC) and the OTDS Release Notes on OpenText My Support (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/KCProduct?
id=373), and then select Documentation.

Note: A Web Access Management authentication handler must be

configured on OTDS for this option to work. For more information,
see the “Web Access Management” authentication handler
documented in OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC).

Username Case Sensitivity

Case sensitivity for the <username> can be configured to preserve case or
change case to all lowercase. You may wish to change case to lowercase
when you have a case-sensitive database and synchronization is configured
to lowercase.
If Web Server authentication is enabled but user information is not available,
authentication will try OTDS authentication.

Global Integration Settings

This area provides Content Server with the information it needs to access either
the internal or the external version of OTDS. Both fields in this area are required
fields.
If you are accessing an internal version of OTDS, Content Server's installation
will have populated both fields: OTDS Server URL and Resource Identifier.
If you are accessing an external version of OTDS, the Admin must first create a
Content Server resource in OTDS. During the process, a unique identifier, called
the resource ID, is generated. The resource ID and the OpenText Directory
Services server URL are required values, and must be entered to set up OTDS
Authentication in Content Server. For more information, see OpenText Directory
Services - Installation and Administration Guide (OTDS-IWC) and the OTDS
Release Notes on OpenText My Support (https://knowledge.opentext.com/
knowledge/llisapi.dll/open/KCProduct?id=373), and then select Documentation.

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration 9

Chapter 1 Configuring Directory Services Integration

Local Integration Settings

The OTDS Sign In URL field provides the option to specify a URL to which
users are redirected when they sign in. You also have the option of displaying a
log-out option for users that authenticate with single sign on.

1.3.1 To Configure OTDS Integration Settings

To configure Directory Services integration settings:

1. On the Content Server Administration page, in the Directory Services

Integration Administration area, click the Configure Integration Settings link.

Tip: You can use a shortcut to access this page directly, http://<fully_
qualified_server_name>/<Content Server_service_name>/cs.exe?
func=otdsintegration.settings.
An example of a URL is: http://machine1.opentext.com/OTCS/cs.exe?
func=otdsintegration.settings

2. In the Web Server Authentication area, do the following:

a. Optional Select Enabled if you want to retrieve authenticated user

information directly from your Web Server. If you are using an internal
installation of OTDS, make sure that Web Server Authentication is
enabled.
b. In the Environment Variable box, enter the variable used to validate user
credentials or leave the default, REMOTE_USER. If you are using an internal
installation of OTDS, leave REMOTE_USER.
c. In the Username Formatting area, select the option that corresponds to the
format of users' Log-in names in Content Server:

• Remove domain name: this will display the user name only. This is the
default selection.
If you are using an internal installation of OTDS, leave Remove domain
name selected.
• Do not format: this will leave the user name unchanged.
• Resolve through OTDS: the value from REMOTE_USER is sent to OTDS
in order to find the corresponding user name in Content Server. You
must configure OpenText Directory Services. For more information, see
OpenText Directory Services - Installation and Administration Guide (OTDS-
IWC).

Note: A Web Access Management authentication handler must be

configured in OTDS in order for this option to work.
For more information, see the “Web Access Management”
authentication handler in OpenText Directory Services - Installation
and Administration Guide (OTDS-IWC).
d. In the Username Case Sensitivity area, select one of the following:

10 OpenText™ Content Server LLESDSI220100-AGD-EN-02

 1.3. Configuring Integration Settings

• Select Preserve Case to preserve the user name when the user signs in
to Content Server.
If you are using an internal installation of OTDS, leave Preserve Case
selected.
• Select Lowercase to change the user name to all lowercase letters when
the user signs in to Content Server.

3. In the Global Integration Settings area, do the following:

a. In the OTDS Server URL box, enter the URL of the Directory Services
server.
The URL must include the fully-qualified domain and port number of the
Directory Services server. For example, the URL would be one of:

• http://<server_name>:<port_number>
• https://<server_name>:<port_number>

Note: If your Directory Services server has been installed in a cluster,

you must enter the fully-qualified domain and port number of the
load balancer in the OTDS Server URL box.

An example of a valid URL when using an external, stand-alone,

installation of OTDS is: http://mymachine.opentext.com:8080
An example of a valid URL when using a version of OTDS that ships
internally with Content Server is: http://mymachine.opentext.com:8002
If you are using an internal installation of OTDS, this box is filled by
default.
b. In the Resource Identifier box:

i. If you are using an external installation of OTDS, enter the unique ID

that was generated when you created a synchronized Content Server
resource in Directory Services.
ii. If you are using an internal installation of OTDS, Content Server will
have generated the Resource Identifier and it will be present in the
box.
c. You can choose to click Test Settings to confirm that the URL entered in
the OTDS Server URL box is valid.

Note: The connection test does not check whether the OpenText
Directory Server is configured properly with Content Server. It only
checks that the URL provided in the OTDS Server URL box is valid.

4. Optional In the Local Integration Settings area, do the following:

a. In the OTDS Sign In URL box, specify a URL to which users are redirected
when they sign in. For an example of the URL convention, see Step 3.a.

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration 11

Chapter 1 Configuring Directory Services Integration

Note: You might choose to select this option when OTDS is only
accessible to users through an external URL.
b. If you want to display a sign-out option for users that are authenticated
with single sign on, select Show log-out option for SSO users.
5. In the Web Administrator Password area, type the Content Server Web
Administrator Password in the box provided, and then click Save.
6. Next, do one of the following:

• If you are using an internal installation of OTDS, restart Content Server.

• If you are using an external installation of OTDS, do the following:
1. On the Content Server Administration page, in the Server
Configuration area, select Configure Security Parameters.
2. On the Configure Security Parameters page, if you are using an external
installation of OTDS, in the Trusted Referring Websites box, ensure that
the OTDS Server name from Step 3.a is listed.
3. Restart Content Server.

1.3.2 To Change from an Internal Installation of OTDS to an

External
If you decide to change your OTDS installation from an internal version that
shipped with Content Server to an external version of OTDS, you need to follow the
following steps. For more information, see the OpenText Directory Services -
Installation and Administration Guide (OTDS-IWC).

1. Create a supported database for your OTDS data, see Step 1.

2. Download the OTDS installer from My Support and install it, see Step 2.
During the installation you will be:
a. Informing OTDS about your newly created database.
b. Importing your data from the location it resided when you were using the
internal installation of OTDS.
3. Access the System Attributes page in your new, external OTDS installation to
verify the Synchronization Master Host, see Step 3.
4. Access the Configure Integration Settings Content Server page to inform
Content Server about the location of the newly installed, external OTDS, see Step
4.

To change from an internal installation of OTDS to an external:

1. You must first create a database before you begin installing OTDS as an
external, stand-alone application. This database will contain all data that OTDS
manages. For more information, see OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC).

12 OpenText™ Content Server LLESDSI220100-AGD-EN-02

 1.3. Configuring Integration Settings

2. Install OTDS as an external, stand-alone application.

During the installation process you will inform OTDS about your database and
its location.
You will also have the option of importing your data from a previous version of
OTDS. When you begin your installation of the external OTDS, and to import
users, follow the instructions in Importing your data to OTDS 16 or higher
(https://knowledge.opentext.com/knowledge/piroot/otds/v210400/otds-iwc/en/
html/jsframe.htm?s-upgrimp).
Selecting this option will import your data from OpenDJ to your new database.
3. On the new, external OTDS installation, the value of the system attribute
“directory.bootstrap.MasterHost” (Synchronization Master Host) needs to be
adjusted to ensure that it is correct.
For more information, see System Attributes (https://knowledge.opentext.com/
knowledge/piroot/otds/v210400/otds-iwc/en/html/jsframe.htm?ch-attributes).
4. On your Content Server installation, on the Content Server administration page,
under the Directory Services Integration Administration heading, click
Configure Integration Settings.

Tip: You can use a shortcut to access this page directly, http://<fully_
qualified_server_name>/<Content Server_service_name>/cs.exe?
func=otdsintegration.settings.
An example of a URL is: http://machine1.opentext.com/OTCS/cs.exe?
func=otdsintegration.settings

On the Directory Services Integration Administration page, do the following:

a. In the OTDS Server URL field, enter the URL for the external installation
of OTDS.
For more information about this field and example URLs, see Step 3.a in
“To configure Directory Services integration settings:“ on page 10.
b. In the Resource Identifier field, ensure that the resource identifier
generated when you created a resource for Content Server in OTDS is
present.
If you need to retrieve the resource identifier from OTDS, see Editing a
synchronized resource (https://knowledge.opentext.com/knowledge/piroot/
otds/v210400/otds-iwc/en/html/jsframe.htm?s-editdelresource).
c. You can choose to click Test Settings to confirm that the URL entered in
the OTDS Server URL field is valid.
d. In the OTDS Sign In URL field, you can choose to specify a URL to
redirect users to sign in to OTDS.
For more information about this field and example URLs, see Step 3.a in
“To configure Directory Services integration settings:“ on page 10.
e. Type the Content Server Web Administrator Password in the field
provided, and then click Save Changes.

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration 13

Chapter 1 Configuring Directory Services Integration

5. You can optionally choose to delete the internal OTDS process. For more
information, see “To Delete an Internal OTDS Process” on page 8.

1.4 Explaining the OTDS-specific Content Server

installation pages
During the installation of Content Server, the administrator has to specify
information that OTDS requires. OpenText recommends that you do not access these
pages after completing your Content Server installation.

• The administrator is required to select their OTDS server type during installation
on the http://MyContentServer.com/<CS_service_name>/cs.exe?func=
admin.otds page. For more information, see “The Configure OTDS Integration
Settings Content Server installation page” on page 14.
• Optionally, the administrator can choose to apply their Content Server license(s)
during installation on the http://MyContentServer.com/<CS_service_name>/
cs.exe?func=admin.licensesetup page. For more information, see “The
License Setup Content Server installation page” on page 16.

1.4.1 The Configure OTDS Integration Settings Content

Server installation page
The Configure OTDS Integration Settings Content Server installation page, which
OpenText recommends you do not access after completing your Content Server
installation, contains the following:

1. From the Server Type list, choose whether your OTDS installation is an internal
or an external installation.
The next fields that appear on this page depend on your selection in this field.
a. If you selected “External OTDS Server” in 1, you will see the following:
i. The Server URL box. A value in this box is required if you are setting up
an external OTDS installation. You need to enter the host name (or IP
address) and port of your OTDS server. For example, enter http://
MyOtdsServer.corp.com:8080
ii. The Resource ID box. A value in this box is required if you are setting up
an external OTDS installation. You need to enter the Resource Identifier
of the OTDS Resource that has been set up for use with Content Server.
An example of a resource ID is: dba563af-b01d-4f88-
bc42-2493c97dbc87.
iii. You can choose to click Test Settings to confirm that the URL entered in
the OTDS Server URL box is valid.

Note: The connection test does not check whether the OpenText
Directory Server is configured properly with Content Server. It
only checks that the URL provided in the OTDS Server URL box is
valid.

14 OpenText™ Content Server LLESDSI220100-AGD-EN-02

 1.4. Explaining the OTDS-specific Content Server installation pages

b. If you selected “Internal OTDS Server” in 1, you will see the following:
i. The JDBC URL box. A value in this box is required if you are setting up
an internal OTDS installation. You need to provide the direction to the
database that was set up for your OTDS server.
For example, if you are using an SQL server database, enter
jdbc:sqlserver://MyOtdsServer.corp.com;databaseName=
livelink

Important
You must take care when entering values to the three JDBC boxes.
These values cannot be validated at the time you enter them. Any
error in one of these three values will result in errors in the OTDS
logs.

ii. The JDBC Username box. A value in this box is required if you are
setting up an internal OTDS installation. Type the userid of a user with
the required privileges to access the database that you entered in i.

iii. The JDBC Password box. A value in this box is required if you are
setting up an internal OTDS installation. Type the password for the
userid that you entered in ii.

iv. The HTTP Port, HTTPS Port, and Stop Port boxes. A value in each port
box in the Jetty Parameters area is required if you are setting up an
internal OTDS installation.

v. Optionally, when setting up an internal OTDS installation, you can

choose to configure the internal OTDS Server to use a security certificate
of your choice, rather than the default, self-signed certificate.
You do so by entering the Java key store parameters in the Jetty HTTPS
Configuration area. You will need to enter values to the Java Key Store,
Java Key Store Password, and Java Key Manager Password boxes.

2. Optionally, you can choose to enable Set OTDS login URL if you want to
explicitly set the OTDS URL to which users should be redirected, enter that URL
in this field.
If you have structured either a proxy or a containerized environment, then you
will need to ensure that the Login URL box contains that URL. If you do not
have either a proxy or a containerized environment, then you do not need to
enable this setting.
The following are two examples of the format of the URL that you will enter to
this field:

• https://servername.domain.com
• https://servername.domain.com:8443

You may need to put the port number after the base URL depending on how you
set up your proxy.

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration 15

Chapter 1 Configuring Directory Services Integration

For more information, see OpenText Content Server - Installation Guide (LLESCOR-
IGD) on OpenText My Support (https://knowledge.opentext.com/knowledge/
llisapi.dll/open/2120999). Select Documentation.

1.4.2 The License Setup Content Server installation page

The License Setup Content Server installation page provides information about
your Content Server license, your Content Server module(s) license(s), your Content
Server system fingerprint, and allows you to apply license(s) to your installation.
This page, which OpenText recommends you do not access after completing your
Content Server installation, contains the following:

• The Content Server License Overview area contains information about your
Content Server license, if one is applied. For information about the fields in this
area, see OpenText Content Server - Content Server Administration (LLESWBA-AGD)
on OpenText My Support (https://knowledge.opentext.com/knowledge/
llisapi.dll/open/2120999). Select Documentation and view the admin online help
collection.
• The Module License(s) Overview area contains information about your Content
Server module(s) license(s), if any is applied. For example, if you have licenses
for ObjectImporter or for WebReports, this area will display information about
those licenses.
• The System Fingerprint area provides you with your Content Server system
fingerprint. If you will be licensing Content Server, or any Content Server
module, you will need to copy the value in the System Fingerprint field to use
below. For more information, see OpenText Content Server - Content Server
Administration (LLESWBA-AGD) on OpenText My Support (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/2120999). Select
Documentation and view the admin online help collection.
• The License Management area provides the OpenText Product Activation
website for Content Server (http://productactivation.opentext.com/
ContentServer) URL, and a License Location field so that you can apply a
Content Server license or a license to a Content Server module. To apply your
licenses during installation, on the License Setup page, do the following:
1. Click the product activation link to open the OpenText product activation
website, and then, do the following:
a. Sign in to the product activation website using the userid and password
provided to you when you purchased your OpenText product.
b. If you have more than one Content Server environment, select the
environment to which you will be applying the license.

Tip: Only one license is required for multiple instances of Content

Server that connect to the same database.
c. Select the appropriate product and license file type.

16 OpenText™ Content Server LLESDSI220100-AGD-EN-02

 1.5. Your Directory Services installation and Content Server

d. You need to copy the value in the System Fingerprint field, as detailed
above, in order to generate a license file. You will be prompted to enter
your system fingerprint in the OpenText product activation website.
e. OpenText will send you the license file that you must apply to Content
Server. You may have multiple license files depending on the number of
OpenText products for which you chose to acquire license(s).
2. Return to the License Setup page. In the License Location field, click Choose
File.
Browse to the location that you saved the license file, and then click that
filename to select it. The license file will be a “<filename>.lic” file.
3. Click Apply to apply that license file to Content Server.
4. If you have more license(s) to apply, use the Choose File and Apply buttons
as detailed in 2 and 3 above to apply all licenses.

Important
You must apply each license file one at a time. In other words, use the
Choose File button to find and then select the license, and then click
Apply before proceeding to select and apply the next license.
5. Once you have finished applying your license(s), restart your Content Server
admin servers, and then click Continue.

If you choose not to license your Content Server installation, or your Content Server
module(s), at this time, you will need to follow the procedure found in OpenText
Content Server - Content Server Administration (LLESWBA-AGD) on OpenText My
Support (https://knowledge.opentext.com/knowledge/llisapi.dll/open/2120999).
Select Documentation and view the admin online help collection.

1.5 Your Directory Services installation and Content

Server
Whether you are using an internal version of OTDS or an external stand-alone
version, a database must be provisioned for OTDS to use. The database that is used
by Directory Services stores OTDS configuration, partitions, and user data. There are
situations, such as upgrading, that require you to manage the existing OTDS
information. This section details the Migrate option, that allows you to migrate all
Content Server users and groups into OTDS.

Explaining the internal OTDS database

OTDS user data and configuration data can be stored separate from the database
that Content Server uses for data. However, that OTDS data is linked to the Content
Server database.

Important
If you change your Content Server database, or if you upgrade Content Server,
and you are using an internal installation of OTDS, you must follow the steps

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration 17

Chapter 1 Configuring Directory Services Integration

in “To migrate OTDS data:“ on page 18 and “To Change from an Internal
Installation of OTDS to an External” on page 12 to point Content Server to the
database that contains your OTDS data.

1.5.1 To Migrate OTDS Data

To migrate OTDS data:

1. If your Content Server installation uses an internal installation of OTDS and you
want to change your Content Server database, or you are upgrading your
installation of Content Server, you need to follow these instructions.
During the process of changing your Content Server database or upgrading
your Content Server installation, you will see the User and group migration
page.

2. On the User and group migration page, in the OTDS Partition box, type the
name of the OTDS partition that will be used by Content Server. This is the
OTDS partition that stores any users and groups created in Content Server or
migrated from the Content Server database.

Note: The partition name you enter will only be used when users and/or
groups are migrated from the Content Server database, or when users
and/or groups are created directly in Content Server instead of being
created through OTDS.

3. The Migrate option applies if you have an installation of Content Server with
CSDS, an internal installation of OTDS, or an external installation of OTDS:

a. If you are using an external installation of OTDS, and prior to beginning

the migration, you must ensure that the access role has been created in
OTDS correctly.
For example, make certain that the “Content Server Members” partition has
been added to the Content Server access role. You must also ensure that the
Include groups option has been selected on that Content Server access role.
Because this is the default behavior in an internal installation of OTDS, you
only need to perform this check if you are using an external installation of
OTDS.

b. If OTDS has never been used with Content Server, select the Migrate box to
migrate users and groups from the Content Server database to OTDS. The
Migrate option applies to migration of users and groups only.

Important
The migration function cannot distinguish users synchronized from
OTDS from internal Content Server users. If you have already
synchronized new users and/or groups from OTDS to Content Server,
and you use the migration option, you will end up with duplicate
users and groups.

18 OpenText™ Content Server LLESDSI220100-AGD-EN-02

 1.5. Your Directory Services installation and Content Server

There are three options associated with the Migrate option. You can select
any of the following:

i. If you want to migrate internal users and groups, select Migrate

internal users and groups.
All existing users and groups in OTDS contained in the partition you
entered in Step 2, and any Content Server domain partitions will be
replaced with users and groups in the current database.
ii. If you want to migrate external users and groups, select Migrate
(Tempo) external users and groups. This option relates to the
OpenText Tempo product.
All existing users and groups in OTDS contained in the partition you
entered in Step 2, and any Content Server domain partitions will be
replaced with users and groups in the current database.
iii. If the migrate option has identified a Content Server Directory Services
module's synchronization sources that you can migrate to OTDS, those
synchronization sources will be listed for you to select.

Note: The migration function does not migrate CSDS users and
groups. It migrates the CSDS sync profile into OTDS, which can
then be used to import the same set of users.
If your internal Content Server groups have synchronized CSDS
members, you need to ensure that synchronized users and
groups exist in OTDS prior to migrating the internal Content
Server groups into OTDS. You can check to see if any of your
Content Server groups, that are not synchronized by CSDS,
contain synchronized CSDS members.
This is necessary so that the migration can find the DN of the
synchronized user or group in OTDS in order to create or
designate that user or group as a member of the migrated internal
group.
Under these circumstances, run the migration to migrate your
CSDS synchronized sources only. When all your synchronized
users and groups exist in OTDS, you can run the migration tool a
second time to migrate the internal users and groups.

4. Type the Content Server Web Administrator Password in the box provided,
and then click Continue. This process may take a few minutes.

LLESDSI220100-AGD-EN-02 OpenText™ Directory Services Integration Administration 19