Ann,
I typed up some basic instructions below. See if this helps you.

On the Server tab:

Use the IP address of a AD Domain Controller and the port number to use for connecting to LDAP. If you are going to use Secure LDAP (LDAPS) then you will need the secure port number. We use this and I recommend it.

Select the Server Type of Active Directory and LDAP or LDAPS depending on which port you used above.

BindDN is the Distinguished Name of the service account used to bind to Active Directory. So if I have a user account called san in the Service Accounts OU, which is under the Servers OU which is at the root of the corp.com domain, then the DN I will use in this field is:

CN=san,OU=Service Accounts,OU=servers,DC=corp,DC=com

The Bind Password is just the password of the user account above.

The User Search path and Group Search Path fields are just an LDAP reference used for searching the directory for users and groups. You can be as broad or narrow in your search as you like. For our example above I would just use the broadest approach (unless you have a really large directory):

DC=corp,DC=com


On the Role Mapping tab:

For my environment I use AD groups to control access to Navisphere. So all users that need access to Navisphere I place in a Group called SAN Admins. For the Role Mapping select Group from the first drop down box, type the name of the group in the Name box, and select the Role you want to assign to the group.


On the Advanced tab:

I use the following values which I find to work well:
User ID Attribute: sAMAccountName
User Name Attribute: cn
Group Name Attribute: cn
Group Member Attribute: member
User Object Class:
Group Object Class: group

Hopefully this will help you setup the connection.