Skip to content
Snippets Groups Projects
Commit e603a5e6 authored by Owen Tuz's avatar Owen Tuz
Browse files

LDAP connector - Document that 'DN' must be in capitals

parent 5f054fcf
Branches
Tags
No related merge requests found
...@@ -43,6 +43,8 @@ Dex currently allows insecure connections because the project is still verifying ...@@ -43,6 +43,8 @@ Dex currently allows insecure connections because the project is still verifying
User entries are expected to have an email attribute (configurable through `emailAttr`), and a display name attribute (configurable through `nameAttr`). `*Attr` attributes could be set to "DN" in situations where it is needed but not available elsewhere, and if "DN" attribute does not exist in the record. User entries are expected to have an email attribute (configurable through `emailAttr`), and a display name attribute (configurable through `nameAttr`). `*Attr` attributes could be set to "DN" in situations where it is needed but not available elsewhere, and if "DN" attribute does not exist in the record.
For the purposes of configuring this connector, "DN" is case-sensitive and should always be capitalised. This is treated as a special case because, while all other configuration values refer to single attributes on an entity, an LDAP Distinguished Name consists of multiple attributes which uniquely identify a resource.
The following is an example config file that can be used by the LDAP connector to authenticate a user. The following is an example config file that can be used by the LDAP connector to authenticate a user.
```yaml ```yaml
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment