Policy Enforcement · Topic 1 of 7
Identity Stores, Active Directory and LDAP
Join ISE to Active Directory, connect an LDAP server, and compare identity store options including certificates, token servers, MFA and local users.
- 5 min
- Native AD means ISE joins the domain as a member, using a join point.
- Before the join, DNS and time sync must be correct.
- Only the AD groups you select on the Groups tab can be used in policy.
What it is
An identity store is the place where ISE looks up a user or machine to check who it is.
ISE can keep identities itself, or ask an external source. The external source is often Active Directory, but it can be an LDAP directory, a certificate authority, or a token server.
How it works
ISE joins or connects to each store, then policy decides which store to ask and which attributes to use.
Native Active Directory
Native means ISE joins the domain as a member machine. The Policy Service Nodes then talk to the domain controllers directly.
Before you join, check three things:
- DNS: ISE must resolve the domain and find the domain controllers.
- Time: The ISE clock must be close to the domain controllers, because Kerberos is sensitive to time.
- Account: The account you use to join needs the right to create or use a computer account.
The join is done in the admin portal under Administration, Identity Management, External Identity Sources, Active Directory. You add a join point, enter the domain, and join the nodes. Each node shows a status of Operational when it is joined and healthy.
After the join, open the Groups tab and select the directory groups you want to use in policy. Only the groups you add are available as conditions. The Attributes tab works the same way for directory attributes.
ise-psn/admin# show application status ise
ise-psn/admin# show ntp
Use show ntp on the ISE command line to confirm time sync before a join. A join that fails after a correct password is often a clock or DNS problem.
AD supports the common password based and certificate based methods. That includes PEAP with MS-CHAPv2 and EAP-TLS. It also supports machine authentication, where the computer account is checked as well as the user.
LDAP
LDAP is a generic directory connection. You use it for non Microsoft directories, or when you do not want to join the domain. It is configured under External Identity Sources, LDAP.
You enter the server name and port, the bind account, and the search bases for subjects and groups. For a protected connection, use LDAPS, which runs on port 636. Plain LDAP uses port 389.
| Feature | Native AD | LDAP |
|---|---|---|
| Joins the domain | Yes | No |
| Password methods | MS-CHAPv2, PAP and more | PAP and EAP-GTC, not MS-CHAPv2 |
| Machine authentication | Supported | Not as a computer account |
| Group lookup | Built in | By search base |
LDAP cannot check an MS-CHAPv2 password, because the directory does not give ISE the secret it needs. Use PAP over a protected tunnel, or use certificates, with LDAP.
Other identity store types
ISE supports more sources than AD and LDAP:
- Certificate authentication profile: Used for PKI. It picks which certificate field is the username, and can compare the certificate with the directory.
- RADIUS token server and RSA SecurID: Used for one time passwords.
- SAML identity provider: Used for portal sign on with an external provider.
- ODBC: Used to look up users in a database.
- Internal users: A local database inside ISE, good for small groups and test accounts.
Internal endpoints are a separate local store. ISE keeps endpoint MAC addresses there, and policy can use it for MAB.
REST ID store
A REST ID store lets ISE check users against a cloud identity provider through its web API, with no domain join. The usual example is Microsoft Entra ID, formerly Azure Active Directory (Azure AD).
ISE uses the OAuth 2.0 Resource Owner Password Credentials (ROPC) flow. It sends the username and password it received to the provider and gets back a token. ISE can then also read the user's groups for use in policy.
Because ISE must pass the user's password on to the provider, it needs an authentication method in which it can see the real password.
Multifactor authentication
Multifactor means a password plus something else, such as a one time code or a push. ISE does this by pointing at a token server, an external multifactor service that acts as a RADIUS proxy, or a SAML provider.
The usual design is that ISE sends the request on and the external service handles the second factor. ISE then acts on the result.
Identity source sequences
A sequence is an ordered list of stores. ISE tries them in order until one finds the user.
You use a sequence when users could be in more than one place. You can also say what to do if a store cannot be reached: stop, or move on to the next one.
When an AD join fails, check DNS and time before you check the password. Those two cause most failures.
What to remember for the exam
Eight facts cover this topic.
- Native AD means ISE joins the domain as a member, using a join point.
- Before the join, DNS and time sync must be correct.
- Only the AD groups you select on the Groups tab can be used in policy.
- LDAP does not join a domain, and it uses port 389, or 636 for LDAPS.
- LDAP supports PAP and EAP-GTC but not MS-CHAPv2.
- Certificate authentication profiles handle PKI and pick the username field.
- Multifactor is done through a token server, a RADIUS proxy or SAML.
- An identity source sequence tries stores in order.
Use LDAP with a method it supports. PEAP with MS-CHAPv2 will fail against a plain LDAP store.
Common mistakes
These four mistakes are common.
Wrong DNS on ISE. The join cannot find the domain controllers.
Forgetting to add groups. The group does not appear in policy until you select it on the Groups tab.
Using MS-CHAPv2 with LDAP. The directory cannot validate it.
Using plain LDAP across an untrusted path. Use LDAPS so the bind password is protected.
Check yourself
Work through these three questions.
What must be correct before ISE joins Active Directory?
DNS must resolve the domain and the ISE clock must match the domain controllers.
Why is MS-CHAPv2 not supported with LDAP?
The directory does not give ISE the secret it needs to check that password.
What does an identity source sequence do?
It tries a list of identity stores in order until one finds the user.
Topic 1 of 7 in Policy Enforcement
Test yourself on Policy Enforcement
The full Cisco CCNP 300-715 SISE question bank has 852 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Cisco. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.