Study guide
12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO
CyberArk Defender - PAM PAM-DEF
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Vault Architecture, Network & Security
1.1 CyberArk PAS Core Architecture & Component Topology 1.2 Vault OS Hardening, Network Isolation & Port Requirements 1.3 Vault Cryptography, Encryption Keys & Master User Recovery
2 Chapter 2: Vault Configuration, Administration & CLI Utilities
2.1 Vault Server Configuration Files & DBParm.ini Tuning 2.2 Vault Administrative Utilities & PARClient Commands 2.3 Event Notification Engine (ENE) & Notification Administration
3 Chapter 3: Password Vault Web Access (PVWA) Administration
3.1 PVWA Web Portal Architecture & Interface Configuration 3.2 PVWA REST API Administration & Lifecycle Automation 3.3 PVWA Security Settings, User Access & Session Timeouts
4 Chapter 4: Central Policy Manager (CPM) Architecture & Operations
4.1 CPM Service Architecture, Logs & Multi-CPM Load Distribution 4.2 The Credential Management State Machine: Change, Verify & Reconcile 4.3 CPM Plug-in Architecture, Process/Prompts Files & Custom Plug-in Troubleshooting 4.4 Loosely Connected Devices: Rotating Laptop & Workstation Credentials
5 Chapter 5: Safe Design, RBAC & Account Governance
5.1 Enterprise Safe Architecture & Naming Conventions 5.2 Safe Permissions, Authorizations & Safe Handler Delegation 5.3 Object Versioning, Retention Policies & Storage Quotas 5.4 Mandatory Account Properties, Account Types & Linked Accounts 5.5 Vault Users, Predefined Groups & Vault-Level Authorizations
6 Chapter 6: Account Discovery & Lifecycle Workflows
6.1 Automated Account Discovery, Detection Rules & Pending Accounts 6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver 6.3 Exclusive Access, One-Time Passwords (OTP) & Check-out Automation 6.4 Bulk Onboarding: Password Upload Utility, Bulk Upload REST API & AccountUploader
7 Chapter 7: Master Policy & Platform Management
7.1 Master Policy Framework & Enterprise Compliance Rules 7.2 Platform Architecture, Settings Tree & Platform Duplication 7.3 Platform Policy Overrides, Advanced Settings & Target Tuning
8 Chapter 8: Privileged Session Manager (PSM) Core Architecture
8.1 PSM Architecture, Jump Host Isolation & Service Accounts 8.2 PSM Connection Components (PSM-RDP, PSM-SSH, PSM-Web) 8.3 PSM Universal Connector Framework & Custom Integrations 8.4 Split Workflow: Separating Session Use from Credential Retrieval
9 Chapter 9: PSMP, HTML5 Gateway & Session Security
9.1 PSM for SSH (PSMP) Architecture & Unix Proxy Brokering 9.2 PSM HTML5 Gateway Architecture & Clientless Web Access 9.3 Session Recording, Storage in Recordings Safes & Vault Retention 9.4 CyberArk Remote Access (Vendor PAM): Administering Third-Party Privileged Access
10 Chapter 10: Live Session Auditing, Reporting & Privileged Threat Analytics
10.1 Live Session Monitoring, Shadowing & Active Termination 10.2 Privileged Threat Analytics (PTA) Behavioral Anomaly Detection 10.3 PTA Automated Incident Response & SIEM Integration (CEF/Syslog) 10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility
11 Chapter 11: Application Access Manager (AAM) & Secrets Management
11.1 AAM Credential Provider (CP) Architecture & Local Memory Cache 11.2 Central Credential Provider (CCP) & Web Service Integration 11.3 Application Server Credential Provider (ASCP) & Application Authentication (AppID) 11.4 Conjur Secrets Manager & Cloud-Native DevOps Workflows
12 Chapter 12: Directory Integration, Disaster Recovery & Troubleshooting
12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO 12.2 Disaster Recovery (DR) Vault & PADR Replication Architecture 12.3 Vault Backup Operations with PAReplicate & Safe Recovery 12.4 Diagnostic Procedures, Vault/CPM/PSM Error Codes & System Recovery
12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO
Key Takeaways Explain This Topic AI
Active Directory integration communicates via LDAPS over TCP port 636 (or TCP port 3269 for Global Catalog), requiring the enterprise root CA certificate installed in the Vault's Trusted Root store.
Directory Mapping rules link Active Directory security groups to Vault User Templates dynamically, provisioning users upon their first login without creating static individual Vault users.
Safe permissions are governed efficiently by adding mapped Active Directory security groups directly as Safe members, providing automated permission inheritance.
RADIUS multi-factor authentication is configured in DBParm.ini via the RadiusServersInfo parameter, validating secondary credentials over UDP port 1812 or 1645.
SAML 2.0 federated SSO delegates authentication to external IdPs via SP-initiated flows, but strictly requires pre-existing LDAP Directory Mapping to resolve the NameID claim into Vault authorizations.
Last updated: September 2026
12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO
Quick Answer: The CyberArk Digital Vault connects to Active Directory via LDAPS over TCP port 636 (or TCP 3269 for Global Catalog), requiring the domain's issuing CA certificate in the Vault's local Trusted Root store. Administrators define Directory Mapping rules that link AD security groups to Vault authorizations, user templates, and Safe access dynamically without static Vault accounts. Secondary authentication challenges are integrated via RADIUS over UDP port 1812/1645 in DBParm.ini , while federated SAML 2.0 SSO redirects users to external Identity Providers (Entra ID, Okta), relying on LDAP directory mappings to resolve the SAML NameID into authorized Vault identities.
Active Directory Integration Architecture & LDAPS Configuration
CyberArk integrates with Microsoft Active Directory (AD) and LDAP-compliant directories to centralize identity management, enforce enterprise password policies, and leverage existing directory groups.
Protocol and Cryptographic Requirements
The Digital Vault initiates outbound connections to Active Directory domain controllers:
Protocol & Ports: Integration requires LDAP over SSL/TLS (LDAPS) on TCP port 636 for standard Domain Controller queries, or TCP port 3269 for Global Catalog queries across multi-domain forests. Cleartext LDAP over TCP port 389 is insecure and rejected in hardened environments.
Certificate Validation: The Vault validates the SSL/TLS certificate presented by the Domain Controller. The issuing Root and Intermediate CA certificates must be imported into the Local Computer \ Trusted Root Certification Authorities certificate store on the Vault host.
High Availability & The Bind Account
To eliminate single points of failure, CyberArk supports configuring multiple Domain Controllers in Password Vault Web Access (PVWA):
Host Priority: Administrators define primary and backup Domain Controllers by FQDN or static IPv4 address.
Automatic Failover: If the primary Domain Controller is unresponsive, the Vault automatically diverts subsequent search and authentication requests to the secondary directory host.
The Bind User: The Vault requires a dedicated domain service account (the Bind Account) with read-only permissions across user and group Organizational Units (OUs). This account should have a complex, non-expiring password (or be managed by CPM) and requires standard Domain Users rights rather than domain administrative privileges.
Directory Mapping Rules & Dynamic Provisioning
CyberArk avoids synchronizing the entire Active Directory tree into the Vault database. Instead, it uses an on-demand, transparent provisioning model driven by Directory Mapping Rules .
Directory Map Components
A Directory Map evaluates incoming directory attributes against defined search criteria to determine how a user is represented inside the Vault:
LDAP Query / Group Filter: Evaluates directory group memberships or OU paths (e.g., memberOf=CN=PAM_Admins,OU=Groups,DC=corp,DC=local ).
Vault User Template: Defines Vault attributes applied to matching users:
User Type: Defines the license type (typically EPVUser for standard administrators).
Authorized Interfaces: Controls accessible client interfaces, including PVWA Web, PrivateArk Client GUI, and PACLI.
Default Location: The organizational container in the Vault directory hierarchy where the user object is placed.
Internal Groups: Built-in Vault groups (e.g., Vault Admins , Auditors ) to which matching users are automatically added.
Rule Precedence & Safe Access via AD Groups
Evaluation Order: The Vault evaluates Directory Mapping rules sequentially from top to bottom . The first matching rule is applied, and evaluation stops immediately. Subsequent rules are ignored. Specific administrative mappings must reside at the top, with broad catch-all maps at the bottom.
Safe Authorizations: Best practice mandates adding the Active Directory security group directly as a Safe member in PVWA. When a domain user logs in for the first time, CyberArk provisions an external user reference object in the Vault database. Because the user belongs to the AD security group, the Vault automatically calculates effective permissions and grants instant access to authorized Safes.
Multi-Factor Authentication: RADIUS Integration
CyberArk natively supports the Remote Authentication Dial-In User Service (RADIUS) protocol to deliver secondary authentication challenges (RSA SecurID, Duo Security, Okta Verify).
RADIUS Configuration in DBParm.ini
RADIUS integration is configured at the Vault level by modifying DBParm.ini in C:\Program Files (x86)\PrivateArk\Server\Conf\ : [RADIUS]
- RadiusServersInfo=10.10.1.50;1812;VaultPrimary;secretKey123;1;10.10.1.51;1812;VaultPrimary;secretKey123;2
- RadiusTimeout=15
RadiusServersInfo : Semicolon-delimited string specifying the RADIUS server IP address, UDP port ( 1812 or legacy 1645 ), client host identifier, shared secret, and priority order.
RadiusTimeout : Seconds the Vault waits for a challenge-response packet before failing over to the secondary server.
Authentication Workflow
The user provides their directory credentials at the PVWA portal.
PVWA prompts for the RADIUS passcode (or triggers an out-of-band push notification).
The Vault formats an Access-Request UDP packet and forwards it over UDP 1812 to the RADIUS server.
Upon receiving an Access-Accept response, the Vault issues an encrypted session token.
Federated Single Sign-On: SAML 2.0 Integration
SAML 2.0 enables web-based Single Sign-On (SSO) by delegating authentication to an Identity Provider (IdP) such as Microsoft Entra ID, Okta, PingIdentity, or ADFS.
SP-Initiated Flow & PVWA Configuration
In the standard Service Provider (SP)-Initiated flow, the user accesses the PVWA URL. PVWA generates an encrypted SAML AuthnRequest and redirects the browser to the IdP. The IdP authenticates the user, generates a signed SAML assertion, and redirects the browser back to the PVWA Assertion Consumer Service (ACS) endpoint ( /PasswordVault/api/auth/saml/logon ).
SAML is configured in PVWA under Administration \ Configuration Options \ Options \ Authentication Methods \ saml :
IdentityProviderLoginURL : The SSO URL of the external IdP.
IdentityProviderCertificate : Public X.509 certificate used by PVWA to validate assertion signatures.
Issuer / EntityID : The unique URI identifying the PVWA instance to the IdP.
NameID Claim: Attribute containing the user's primary logon identifier (e.g., sAMAccountName or userPrincipalName ).
SAML and LDAP Co-Dependence
SAML authentication requires underlying Active Directory integration:
The SAML assertion confirms only that the user authenticated successfully at the IdP.
When PVWA receives the assertion, it extracts the NameID attribute.
The Vault must resolve this NameID against an existing Directory Mapping rule configured via LDAPS to calculate group memberships and Safe authorizations. Without LDAP directory mapping, login fails.
Enterprise Authentication Protocols Comparison Matrix
Protocol Default Port Primary Use Case Configuration Location Vault User Creation Model
CyberArk Native TCP 1858 Break-glass emergency access (Administrator, Master) Native Vault Database Manually provisioned
LDAPS TCP 636 / 3269 Directory authentication & attribute querying PVWA LDAP Integration & DBParm.ini Dynamic via User Template
RADIUS UDP 1812 / 1645 Out-of-band MFA (RSA, Duo, Okta Verify) Vault DBParm.ini ( RadiusServersInfo ) Bound to existing user object
SAML 2.0 TCP 443 (HTTPS) Web-based Federated SSO (Entra ID, Okta) PVWA Options & web.config Resolves NameID via LDAP Map