> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/authentication-and-sso/technical-guide/ldap.md).
# LDAP
| Field | Description |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| auth\_default\_group | **string** If specified, Auth will always assign an authenticated user this string value as a session group upon login. |
| generateToken | **boolean** If `true`, Auth module will generate a unique JWT token corresponding to the authenticating user. This will also require that a signing certificate be imported into Auth. Default is `false`. |
| keyAlias | **string** If generating a token, this value is the provided 'name' when the certificate is created prior to importing into Auth. Only required if `generateToken` is `true`. |
| claimsMap | **string** If generating a token, specify a comma-delimited list of LDAP attributes to be added as claims inside the JWT token. Only required if `generateToken` is `true`. |
**Optional: LDAP Connections Array**
Beginning in Auth - LDAP version 4.7.14, LDAP supports listing multiple LDAP domain/connection point objects, using the same key-values listed above, within an `auth_ldap_connections` array. This will give several authentication options in case one service is unavailable. The authentication module will attempt each service until it successfully logs a user in with the provided credentials.
**Auth LDAP Example (including optional `auth_ldap_connections`):**
```
...
"auth_ldap": {
"hostname": "ldapserver.bluefletch.com",
"port": 636,
"domain": "@BLUEFLETCH",
"rootDN": "DC=BLUEFLETCH,DC=com",
"useHttps": true,
"auth_default_group": "Associates",
"keyAlias": "aliasNameForKey",
"generateToken": true,
"claimsMap": "sam=sAMAccountName,cname=cn,upn=userPrincipalName,memberof=memberOf,dn=distinguishedName"
},
"auth_ldap_connections" : [
{
"hostname": "ldapserver.mnl.bluefletch.com",
"port": 389,
"domain": "@MNL",
"rootDN": "DC=BLUEFLETCH,DC=com",
"useHttps": false
},
{
"hostname": "ldapserver.atl.bluefletch.com",
"port": 636,
"domain": "@ATL",
"rootDN": "DC=BLUEFLETCH,DC=com",
"useHttps": true
}
]
...
```
###
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/authentication-and-sso/technical-guide/ldap.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.