Add an LDAP Configuration
To use your own Lightweight Directory Access Protocol (LDAP) authentication service, Data Hub Service (DHS) must be able to access your Active Directory (AD).
You must set up your own LDAP server before configuring and creating the DHS instance:
- by setting up VPC peering for the LDAP server, or
- by making your Active Directory publicly visible (Not recommended)
Before you begin
You need:
Peered Track
- An AWS virtual private cloud (VPC)
- An AWS peer role
- A peered DHS network
- To configure network routing between client-side and DHS networks
- A peered DHS instance
Public Track
About this task
Important: MarkLogic does not recommend configuring LDAP in a public network. To improve security, configure LDAP in a peered network. See Set Up a Peered Network for Data Hub Service - AWS.
Important: For this task, you must log into your DHS portal with the Security Administrator (SEC-ADMIN) portal role. See Portal Security Roles - AWS.
Procedure
If you are a Data Hub Security Administrator, you can configure additional settings in the Advanced Config section. The Data Hub Security Administrator can modify LDAP groups for DHS.