Enable LDAP for Kong Manager

Using the configuration below, it is unnecessary to manually apply the LDAP plugin; the configuration alone will enable LDAP Authentication for Kong Manager.

Ensure Kong is configured with the following properties either in the configuration file or using environment variables:

• If using HTTP instead of HTTPS, cookie_secure must be manually set to false.

After starting Kong with the desired configuration, you can create new Admins whose usernames match those in the AD. Those users will then be able to accept invitations to join Kong Manager and log in with their LDAP credentials.

When using only RBAC Token authorization, Service Directory Mapping to Kong Roles does not take effect. If you need to use CLI access with your Service Directory mapping, you can use the same authentication mechanism that Kong Manager uses to secure browser sessions.

Authenticate User Session

Now the cookie is stored at /tmp/cookie and can be read for future requests:

Because Kong Manager is a browser application, if any HTTP responses see the Set-Cookie header, then it will automatically attach it to future requests. This is why it is helpful to utilize cURL’s cookie engine or . If storing the session is not desired, then the header value can be copied directly from the /auth response and used with subsequent requests.