Configure Windows Server 2012 LDAP with Cisco AVPair attribute to enable Cisco APIC authentication and role-based access control for users.
This task enables Windows Server 2012 LDAP authentication for Cisco Application Policy Infrastructure Controller (Cisco APIC) by adding the CiscoAVPair attribute to the Active Directory schema and configuring user permissions with appropriate RBAC roles.
LDAP integration with Cisco APIC requires the CiscoAVPair attribute to be configured in the Windows Server 2012 Active Directory schema. This attribute enables assignment of Cisco APIC roles to LDAP users for role-based access control.
Before you begin
-
First, configure the LDAP server, then configure the Cisco Application Policy Infrastructure Controller (Cisco APIC) for LDAP access.
-
The Microsoft Windows Server 2012 is installed and online.
-
The Microsoft Windows Server 2012 Server Manager ADSI Edit tool is installed. To install ADSI Edit, follow the instructions in the Windows Server 2012 Server Manager help.
-
CiscoAVPair attribute specifications: Common Name = CiscoAVPair, LDAP Display Name = CiscoAVPair, Unique X500 Object ID = 1.3.6.1.4.1.9.22.1, Description = CiscoAVPair, Syntax = Case Sensitive String.
For LDAP configurations, best practice is to use CiscoAVPair as the attribute string. If customer faces the issue using Object ID 1.3.6.1.4.1.9.22.1, an additional Object ID 1.3.6.1.4.1.9.2742.1-5 can also be used in the LDAP server.
-
A Microsoft Windows Server 2012 user account is available that will enable the following:
-
Running ADSI Edit to add the CiscoAVPair attribute to the Active Directory (AD) Schema.
-
Configuring an Active Directory LDAP user to have CiscoAVPair attribute permissions.
-
-
Port 636 is required for configuring LDAP integration with SSL/TLS.
Follow these steps to configure Windows Server 2012 LDAP for APIC access with Cisco AVPair:
Procedure
The LDAP server is configured to access the Cisco APIC.
What to do next
Configure the Cisco APIC for LDAP access.