Use the Server Details wizard page to specify the name of the directory server holding the directory you are adding and the port number to which you are connecting.
Note: For external directories that use Secure Sockets Layer (SSL), the certificate that the Lightweight Directory Access Protocol (LDAP) server uses must be valid and certifiable through the Microsoft Windows certificate authority chain. Previous versions of Windows gave the LDAP developer the opportunity to verify certificates; however, Windows 2003 SSL enforces this for you.
Follow these steps:
The directory client always attempts to create a secure encrypted connection to the directory using the port specified here. Some directories support port 389 for secure and insecure communications. Some directories also support port 636 as a secure-only channel. Your directory administrator can tell you which port to use.
For the port specified, a secure channel is used if one is available; otherwise, if the port specified allows insecure communication, this is used. (If insecure communication is not acceptable, the directory import is rejected with a corresponding error message when you click Finish.)
Note: Common configuration policies for directories—in particular, the Enable LDAP simple authentication policy—can have an impact on whether authentication can take place over an insecure communication channel.
Note: If, after adding an LDAP directory, the specified access port is changed, the original security authority is not removed correctly and the security authority list may contain an invalid security authority. This has no functional impact on Client Automation, but the original security authority is listed as valid in security dialogs. Removing the extraneous security authority requires a tool from Technical Support. Contact your support representative and request the cfspsetpass utility.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|