Cisco Cisco Intelligent Automation for Cloud 4.2 Guida All'Installazione
32
Optional Tasks
Configuring Authentication
a.
Enter a name for the datasource. Do not use spaces or special characters.
b.
Enter a description of the datasource. (Optional.)
5.
Expand Choose protocol and server product, then choose the following:
a.
The protocol is always LDAP.
b.
Choose MS Active Directory. (Other server options are Sun One or IBM Tivoli Directory Server.)
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.
This information includes lookup user that you set up as a prerequisite.
a.
Choose Simple (text username and password) from the Authentication Method drop-down list.
b.
Choose Non SSL from the Mechanism drop-down list.
c.
Enter the bind-distinguished name (BindDN) value for the lookup user. The BindDN looks like the following
example:
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.
d.
To query the BindDN value, open a command prompt on the Windows server and execute the following
command:
command:
e.
dsquery user -name “[name]*”
f.
Enter the fully qualified hostname or IP address of the LDAP directory server. For example: dc.notexist.local
g.
Enter the parent folder under which all users will gain access.
h.
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.
in the Austin organization will have access.
i.
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.
j.
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.
domain controller, or by using the SysInternals tool TCPView.exe.
k.
Enter the password for the user specified as the BindDN.
7.
Click Update.
8.
Check the check box next to the newly added datasource and click Test Connection. The Test Status column
displays OK if the connection is successful.
displays OK if the connection is successful.
Configuring Authentication
Configuring authentication requires completing two tasks: configuring mappings and configuring events. The instructions
in this section are how one would complete each task in the example scenario.
in this section are how one would complete each task in the example scenario.