This guide demonstrates two ways to access the Cisco ISE Admin Portal: a local ISE account with read-only access and an Active Directory (AD) account mapped to an external administrator group. It starts from an existing, reachable AD DS domain; installing AD DS is outside this article.
The AD workflow uses a dedicated AD account to join the ISE node, an AD user group to identify administrators, and an ISE RBAC policy to assign portal permissions. Passwords are not included.
Lab environment#
| Parameter | Value |
|---|---|
| Cisco ISE platform | Virtual machine |
| Cisco ISE version | 3.5 Patch 0 |
| ISE node | ise121.company.local |
| ISE management address | 198.18.134.121 |
| AD domain | company.local |
| AD domain controller / DNS | company-ad.company.local / 198.18.134.50 |
| AD join point name | Company-AD |
| AD join account | svc_ise_join |
| AD administrator test account | ise-user1-ad@company.local |
| AD security group | ISE-Admin-Security |
| ISE external administrator group | ISE-Admin-Lab |
Prerequisites#
Before starting, confirm that:
- Cisco ISE can resolve and reach the existing AD domain controller.
- The AD user and security group used for administrator access already exist, or can be created by an AD administrator.
- You have an ISE administrator account with permission to configure external identity sources and Admin Access.
- The account used to join ISE to AD has the required delegated permissions on the ISE computer object.
- You have a separate, known-good ISE administrator login for recovery while changing Admin Portal authentication.
This procedure does not install AD DS or create the company.local domain. It also does not configure endpoint or network-device authentication.
1. Create a local read-only administrator#
This first procedure records the local ISE administrator configured in the lab.
In the ISE Admin Portal, go to Administration > Identity Management > Identities > Users, then click Add. Create an enabled internal user named ise-user1. Set and confirm a password without including it in the article.
The capture shows With Expiration selected with a 60-day password lifetime. This is the setting shown in the lab; use the password policy approved for your environment.

Figure 1. The Network Access User form shows ise-user1 enabled with the Internal Users password type.
Go to Administration > System > Admin Access > Administrators > Admin Users. Select Add > Select from Network Access Users, then choose ise-user1.

Figure 2. Select the existing Network Access User from the Admin Users page.
On the Admin User page, leave Enabled selected, keep External unchecked, and select Read Only. Save the administrator.

Figure 3. The Admin User form shows the local account enabled with Read Only selected.
Confirm that ise-user1 appears in the Admin Users list with the Read Only Admin group.

Figure 4. The administrator list shows ise-user1 with the Read Only Admin group.
Open the Admin Portal at the management URL and sign in with ise-user1. Select Internal as the identity source if the login page prompts for one.
1https://198.18.134.121/admin/
Figure 5. The dashboard identifies the signed-in account as ise-user1 and displays Read-Only access.
To verify the read-only role, open Policy > Policy Sets while signed in as ise-user1. The lab capture shows the Read-Only status on the page.

Figure 6. The Policy Sets page displays the Read-Only status for the current session.
2. Create the AD user and administrator security group#
Create an AD user for Admin Portal sign-in. The lab uses the logon name ise-user1-ad with the user principal name ise-user1-ad@company.local. The screenshot shows the directory object’s name as ise-user-ad-1. Set the password in AD; do not include it in the article.

Figure 7. The AD user is created for the ISE administrator login.
Create or select the AD security group ISE-Admin-Security, then add the test account to it. The directory capture shows ise-user-ad-1 as a member of this group.

Figure 8. The test account is a member of the ISE-Admin-Security AD group.
3. Create a dedicated account for the ISE domain join#
Create a separate AD account named svc_ise_join for the ISE join operation. Use the password set in AD only in the ISE join dialog; never place it in the article.

Figure 9. The AD account svc_ise_join is created for the ISE domain-join operation.
The lab pre-creates a computer object named ise121 in the AD Computers container. This lets the join account receive permissions on the specific ISE computer object instead of relying on a domain-wide administrator account.

Figure 10. The ISE computer account is created in AD before the join.
Open the computer object’s Properties > Security > Advanced, then add a permission entry for svc_ise_join. Select the account as the principal.

Figure 11. Open the advanced security settings for the ISE computer object.

Figure 12. Add a permission entry to the computer object.

Figure 13. Choose the account that will receive delegated permissions.

Figure 14. Select svc_ise_join as the permission principal.
For this lab, the permission entry on the ise121 computer object includes:
- Reset Password
- Read account restrictions
- Write account restrictions
- Validated write to DNS host name
- Validated write to service principal name

Figure 15. The delegated rights apply to the ISE computer object.
4. Apply the SAM RPC policy used in this lab#
During the earlier join attempt, the lab returned Access is denied (ERROR_ACCESS_DENIED, code 5) after validating the join account’s credentials and updating the ISE computer-object attributes. The lab then changed the SAM password-change RPC policy on the domain controller before retrying the join.
On the domain controller, open Group Policy Management. Expand Forest > Domains > company.local > Domain Controllers, right-click Default Domain Controllers Policy, and choose Edit.

Figure 16. Open the Default Domain Controllers Policy in Group Policy Management.
In the Group Policy editor, navigate to:
1Computer Configuration
2 > Policies
3 > Administrative Templates
4 > System
5 > Security Account Manager
6 > Configure SAM change password RPC methods policy
Figure 17. Locate the SAM change-password RPC policy.
Open Configure SAM change password RPC methods policy, set it to Enabled, then select Allow all change password RPC methods.

Figure 18. Open the SAM change-password RPC policy settings.

Figure 19. Enable the policy.

Figure 20. Select Allow all change password RPC methods for this lab.
Apply the updated computer policy on the domain controller:
1gpupdate /forceThe lab capture shows that the computer and user policy updates completed successfully.

Figure 21. The domain controller reports that Group Policy updated successfully.
This is the setting used by this Cisco ISE 3.5 Patch 0 lab. It changes the SAM RPC behavior applied through the domain controllers policy. Review the scope and security impact before using the same setting in a production domain.1
5. Add the AD join point and join the ISE node#
In the ISE Admin Portal, go to Administration > Identity Management > External Identity Sources > Active Directory. Add an AD join point named Company-AD for the domain company.local, then save it.

Figure 22. Configure the Company-AD join point for company.local.
Select the ISE node ise121.company.local and start the join operation.

Figure 23. Select the ISE node that will join the domain.
Enter the svc_ise_join credentials in the Join Domain dialog. In this lab, Specify Organizational Unit and Store Credentials were left unchecked. Click OK to start the join.

Figure 24. Enter the dedicated join account and leave the two optional checkboxes unchecked as captured.
Wait for the operation to finish and confirm that the ISE node reports Completed.

Figure 25. The ISE node’s domain-join status is Completed.
6. Test the AD user against the join point#
Before using the AD user for Admin Portal access, test it against the Company-AD join point with Test User. The lab returned SUCCESS for ise-user1-ad.

Figure 26. Cisco ISE successfully authenticates the AD test user.
The terminal session records this additional result:
1Test Username : ise-user1-ad
2ISE NODE : ise121.company.local
3Scope : Default_Scope
4Instance : Company-AD
5
6Authentication Result : SUCCESS
7
8Authentication Domain : company.local
9User Principal Name : ise-user1-ad@company.local
10User Distinguished Name : CN=ise-user-ad-1,CN=Users,DC=company,DC=local
11
12Groups : 2 found.
13Attributes : 33 found.
14
15Authentication time : 3767 ms.
16Groups fetching time : 55 ms.
17Attributes fetching time: 40 ms.
18Warning : ISE is experiencing latency issues, please check your network
19
20
21Processing Steps:
2216:34:03:165: Resolving identity - ise-user1-ad
2316:34:03:165: Search for matching accounts at join point - company.local
2416:34:06:253: Single matching account found in forest - company.local
2516:34:06:253: Identity resolution detected single matching account
2616:34:06:916: RPC Logon request succeeded - ise-user1-ad@company.localThe authentication result is successful. The captured output also includes an ISE latency warning; the available terminal result does not identify its cause.
7. Retrieve the AD group in Cisco ISE#
In ISE, open Administration > Identity Management > External Identity Sources > Active Directory, select the Company-AD join point, then open Groups. Use Add > Select Groups From Directory and select ISE-Admin-Security.

Figure 27. Retrieve the AD group that contains the administrator account.
8. Configure the Admin Portal to authenticate with AD#
Go to Administration > System > Admin Access > Authentication > Authentication Method. Select Password Based, choose AD:Company-AD as the Admin Portal identity source, and save the change.

Figure 28. The Admin Portal is configured to authenticate administrators through AD:Company-AD.
This setting is for Admin Portal authentication. The lab capture continues to show Internal as the API identity source.
9. Map the AD group to an ISE administrator group and RBAC policy#
Go to Administration > System > Admin Access > Administrators > Admin Groups and add an administrator group named ISE-Admin-Lab. Select External, choose the Company-AD instance, and map the external AD group ISE-Admin-Security.

Figure 29. The external ISE administrator group maps to ISE-Admin-Security in AD.
Next, open Administration > System > Admin Access > Authorization > RBAC Policy. Add or update a rule that matches the ISE external administrator group ISE-Admin-Lab, then assign the menu and data permissions approved for that role.
The lab capture shows the custom rule ISE-Admin-Security-Policy matching ISE-Admin-Lab and displaying Super Admin Menu Access.

Figure 30. The captured RBAC rule matches ISE-Admin-Lab and shows Super Admin Menu Access.
Cisco ISE separates menu permissions from data permissions for external administrator RBAC. Choose both according to the intended role and verify the saved policy before relying on the account for administrative changes.
10. Verify Admin Portal login with the AD account#
Open a private or incognito browser window and go to the ISE Admin Portal. Choose AD:Company-AD, then sign in with ise-user1-ad and its AD password.

Figure 31. Select the AD identity source and enter the AD user credentials.
Confirm that the user can open the ISE dashboard.

Figure 32. The dashboard opens after the external AD administrator signs in.
Security notes and limitations#
- Do not store AD passwords, service-account passwords, or other secrets in the article or screenshots.
- The join account is separate from the AD user used for Admin Portal access. The lab delegates join permissions on the pre-created ISE computer object.
- The captures show Password never expires selected for the lab AD user and join account. Treat that as a lab setting; follow the organization’s service-account and password lifecycle policy in production.
- The SAM RPC policy change is a lab-specific workaround used with Cisco ISE 3.5 Patch 0. Review its domain-controller scope before applying it outside the lab. For later releases, check the Cisco documentation and required Windows Server updates for the exact version in use.
- The authentication output reports success but also includes a latency warning. The supplied result does not identify the warning’s cause.
- A successful portal login confirms authentication and access to the dashboard. The effective administrative capabilities depend on the saved RBAC menu and data permissions.
Conclusion#
The lab verified local read-only access through ise-user1 and AD-backed Admin Portal access through ise-user1-ad. Cisco ISE joined company.local using the dedicated svc_ise_join account, authenticated the AD user successfully, mapped the ISE-Admin-Security group to the external ISE group ISE-Admin-Lab, and opened the dashboard after an AD-based login.
This article does not cover AD DS installation, endpoint authentication, or network-device authentication.
Appendix#
References#
- Cisco ISE Administrator Guide 3.5 — External administrator authentication and RBAC
- Cisco ISE Administrator Guide 3.5 — Administrator groups and RBAC
- Cisco ISE Administrator Guide 3.5 — Windows Server 2025 and SAM RPC settings
Footnotes#
-
Cisco documents that Cisco ISE 3.5 Patch 3 supports joining Windows Server 2025 AD domains without manual domain-controller configuration. For a Windows Server 2025 domain controller, Cisco’s current guide also lists security hotpatch KB5068861, or a later cumulative update that supersedes it, as a prerequisite. This note distinguishes the Patch 0 lab workaround above from guidance for later ISE releases. Check the applicable ISE patch and Windows Server updates before changing the SAM RPC policy in another environment. See Cisco ISE 3.5 New and changed information and Cisco ISE 3.5 Active Directory join requirements. ↩