Installation Guide

5-2

Cisco Intelligent Automation for Cloud Installation Guide

OL-29971-02

Chapter 5 Optional Tasks

Configuring an LDAP Server

The first step is to add a data source and test the connection in Cisco Prime Service Catalog. The

instructions in this section are how one would connect to the LDAP server in the example scenario.

Step 1 Choose Service Portal from the module drop-down list, then click the System Settings from the Setup

tab.

Step 2 On the System Setup portal, click the Connections tab to open the portlet, then click Manage Directory

Server Connection.

Step 3 Click Add to display the Datasources Configuration pane.

Step 4 In the Add or Edit a Datasource pane, enter the following:

• Enter a name for the datasource. Do not use spaces or special characters.

• Enter a description of the datasource. (Optional.)

Step 5 Expand Choose protocol and server product, then choose the following:

• The protocol is always LDAP.

• Choose MS Active Directory. (Other server options are Sun One or IBM Tivoli Directory Server.)

Step 6 Expand Connection Information, then specify the following required datasource information in the

definition area. This information includes lookup user that you set up as a prerequisite.

• Choose Simple (text username and password) from the Authentication Method drop-down list.

• Choose Non SSL from the Mechanism drop-down list.

• Enter the bind-distinguished name (BindDN) value for the lookup user. The BindDN looks like the

following example:

CN=Mehalic Michael,OU=Users,OU=Austin,OU=Texas,OU=USA,

DC=notexist,DC=local

Note PSC now supports the use of LAN Manager (down-level logon) formats now. You can

still use the BindDN as you have it now but you can also use the format of

domainname\username.

• To query the BindDN value, open a command prompt on the Windows server and execute the

following command:

dsquery user -name “[name]*”

• Enter the fully qualified hostname or IP address of the LDAP directory server. For example:

dc.notexist.local

• Enter the parent folder under which all users will gain access.

For example, if the User BaseDN is OU=Austin,OU=Texas,OU=USA,DC=notexist,DC=local, then

all users in the Austin organization will have access.

• Enter the port number for the LDAP according to either of the following conditions:

–

For a non-SSL connection, the default port number for LDAP is 389.

–

For an SSL connection, the default port number for LDAP is 636.

• You can verify the port number for your LDAP server using either by running the command netstat

-an on the domain controller, or by using the SysInternals tool TCPView.exe.