Question 1
Introduction to the customer
You are assisting a company with adding HPE Aruba Networking ClearPass to its network, which uses HPE Aruba Networking network-infrastructure devices.
The company already has a Windows domain and Windows CA. The Windows CA issues certificates to domain computers, domain users, and servers such as domain controllers.


ClearPass cluster IP addressing and hostnames
Publisher = 10.47.47.5
Subscriber 1 = 10.47.47.6
Subscriber 2 = 10.47.47.7
Virtual IP with Subscriber 1 and Subscriber 2 = 10.47.47.8
Refer to the scenario.
You imported the root certificate for the Windows CA into the ClearPass CA Trust list. Based on the scenario requirements, which usages should be added to it?
In ClearPass Policy Manager, the Certificate Authority (CA) Trust List enforces strict trust domain separation using granular usage flags. When an enterprise root or intermediate CA certificate is imported, administrators must assign specific trust usages depending on which subsystems will validate certificates signed by that authority.
1. **EAP Usage**: The Windows CA issues user and computer authentication certificates used for 802.1X/EAP-TLS (or TEAP) client authentication. ClearPass must validate the cryptographic trust chain of these incoming client certificates during RADIUS authentication; therefore, the `EAP` usage is required.
2. **AD/LDAP Server Usage**: ClearPass queries Active Directory Domain Controllers for authentication and authorization over secure transport (LDAPS over port 636 or StartTLS). The Domain Controllers present directory server certificates issued by the internal Windows Enterprise CA. To validate the TLS identity of the domain controllers during LDAPS handshakes, ClearPass requires the `AD/LDAP Server` usage flag on the root CA.
Usages such as RadSec or HPE Aruba Networking Infrastructure apply strictly to RADIUS-over-TLS communication with network access devices and device management tunnels, which are unrelated to Windows CA client and directory certificates.








