Configure Authentication
Director Console Authentication
You need your Director Console credentials for logging in.
Log Into Director Console
Enter the IP address of the API Server in a web browser.
Enter your Username and Password.

Click Log In.
After two consecutive login attempts, captcha authentication is required for the next login.

LDAP Authentication
LDAP (Lightweight Directory Access Protocol) is a service protocol used to communicate with internet directories over an Internet Protocol (IP) network. If your organization uses LDAP for managing users, you can configure Director Console to pull user authentication and role-based access control rules from your LDAP directory. This allows the Director Console to manage user access and roles according to the rules defined in your organization’s LDAP system. When a user’s role is changed in LDAP authentication from a directory server, the new role is applied at their next login into the Director Console.
Configure LDAP
Before configuring LDAP, execute the following command as cmdr-admin to unlock the port for LDAP:
addldapsrv <IP_address> <port>
IP_address is the IP address of the LDAP server and port is the port to configure LDAP.
You can run the
addldapsrvcommand as cmdr-admin to load all the previous firewall rules after upgrading Director Console to a new version. Once you execute the command, you need to update your password.The
com-appinstallercommand updates the physical and tunnel IP address of the Fabric Server in the API Server. If you have run this command, you must re-run theaddldapsrvcommand to let LDAP users log into the Director Console and save configurations.
To configure LDAP Authentication:
Log in as the root user.
Go to
Authentication >> LDAP.
In Base Settings, enter the LDAP URL. It consists of the LDAP address and the port number of the LDAP server. If you are using secure ports in the LDAP URL, you must use the following format:
ldaps://<IP_address>:<port>Example: ldaps://10.45.3.109:636
Enter a Bind DN. It is an unique name for the LDAP server.
Enter your LDAP Password.
Enter a Base DN in the form of an Organization Unit (OU) and a Directory Controller (DC).
In Authenticate Using, select dn to use standard DN format for login, uid to use uid for login (uid for Linux system), SAM Account Name to use SAM Account Name for login (SAM Account Name for Windows), and User Principal Name to use User Principal Name for internet-style login.
Enter a Group Member Attribute which is the attribute of the group member provided in the LDAP server.
Enter a User Search Filter to apply a user filter to the results from the LDAP groups.
Select Enable CN Filter to filter users by their Common Name (CN). When using Active Directory (AD) for authentication with Director Console, enabling the CN Filter is required. It is recommended not to nest an LDAP account within an Active Directory group.
Enter the LDAP groups that have the Root Access, the Admin Access, and the User Access permissions in Role Settings.
For example, if the Group Member Attribute entered is
gidNumber, you must add the gidNumber of the group member in the:Root Access for root permission
Admin Access for admin permission
User Access for normal user permission
Click Update.
Log In Using LDAP Credential
Enter the IP address of the API Server into a web browser.
Select LDAP from the drop-down.
Enter your Username and Password.

Click Log In.
Captcha authentication is required on the next login after two consecutive failed login attempts.

ADFS Authentication
You can also use the ADFS authentication in Director Console. ADFS (Active Directory Federation Services) allows single sign-on (SSO) authentication for Director Console based on your local Active Directory login.
You must have a unique email address attributed to your ADFS account to use the ADFS service. The SAM Account Name must also be unique for each user.
When you change the role of any user in the LDAP or ADFS authentication from the respective directory server, the new role only enters into effect from the next login.
Configure ADFS in Director Console
Log in as the root user.
Go to Authentication >> ADFS.

In the ADFS Configuration section, enter the Application Host URL, the Active Directory Federation Services URL, and the Trust Identifier.
We recommend you use the name of the server that is used to generate the token-signing certificate, as the name of the Trust Identifier. It is a unique identifier for the Relying Party Trust added to the ADFS server.
Upload the Certificate pair and the ADFS token-signing certificate.
You can obtain the ADFS token signing certificate from the AD FS Server. The ADFS token-signing certificate must have a .cer extension.
Refer to the Generating AD FS Certificate section for details.
Click Update to save the settings.

Click View Metadata to view the metadata used to configure Relying Party Trusts.
After configurng ADFS in Director Console, configure Director Console in AD FS server.
Generate AD FS Certificate
Open Server Manager in your Windows machine.

Click Tools and select AD FS Management. It opens up the AD FS management console.

Expand Service and select Certificates.
Select the Token-Signing certificate from the list of certificates.

Go to the Details section of the Certificates tab.

Click Copy to File. It opens up the Certificate Export Wizard.

Click Next.
Select the Base-64 encoded X.509 (.CER) format.

Click Next.
Enter a File name and click Next.
Click Browse to select a location to save the file.

Click Finish to complete the export.

Add Director Console in AD FS Server
Open the AD FS Management console.
In AD FS >> Relying Party Trusts, right click and select Add Relying Party Trust.

Click Start on the welcome page of the Add Relying Party Trust Wizard.

On the Select Data Source page, select the Import data about the relying party from a file option.

Import the previously created XML file and click Next.
Enter the Display Name for the application on the Specify Display Name page.

Click Next.
Select an access control policy under Choose an access control policy.

Click Next. This action takes you to the Ready to Add Trust page.
Click Next on the Ready to Add Trust page.
Select the Configure claims insurance policy for this application option on the Finish page.

Click Close.
Add Claim Rules for Director Console in AD FS Server
After you have successfully added a Relying Party Trust, click the Edit Claim Issuance Policy option. It opens up the Edit Claim Issuance Policy for Application tab.

Click Add Rule. It opens up the Add Transform Claim Rule Wizard.

Click Next.

In the Configure Rule page:
4.1. Enter a Claim rule name.
4.2. Select Active Directory as the Attribute store.
4.3. In the Mapping of LDAP attributes to outgoing claim types table, map the following:
4.3.1. Select User-Principal-Name as an LDAP Attribute and UPN as an Outgoing Claim Type.
4.3.2. Select User-Principal-Name as an LDAP Attribute and UID as an Outgoing Claim Type.
4.3.3. Select Is-Member-Of-DL as an LDAP Attribute and Group as an Outgoing Claim Type.

Click Finish. This action redirects you to the Edit Claim Issuance Policy for Application tab.
Click Add Rule. It opens up the Add Transform Claim Rule Wizard.
Click Next with the default Claim rule template.
In the Configure Rule page:
8.1. Enter a Claim rule name.
8.2. Select Active Directory as the Attribute Store.
8.3. In the Mapping of LDAP attributes to outgoing claim types table, select E-Mail-Addresses as an LDAP Attribute and E-Mail Address as an Outing Claim Type.

Click Finish. This action redirects you to the Edit Claim Issuance Policy for Application tab once again.
Click Add Rule. It opens up the Add Transform Claim Rule Wizard. Select Transform an Incoming Claim as the Claim rule template.

Click Next.
In the Configure Rule page:
12.1. Enter a Claim rule name.
12.2. Select E-Mail Address as the Incoming claim type.
12.3. Select Name ID as the Outing claim type.
12.4. Select Email as the Outgoing name ID format.
12.5. Select Pass through all claim values.

Click Apply.

Last updated
Was this helpful?
