okasion/ldapdock
2
1
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Marisa 2025-09-25 10:25:02 -04:00
parent 39ed68857e
commit 441e49edc1
1 changed files with 1 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -27,12 +27,7 @@ With -h we are specifying the name of the host, we are using example.com, this i
## _Explaining DN, parentDN, CN, and DC as parameters_
One of the key configuration of LDAP is our "DC" or "parent DN", which to make it easy, in this case \
would be "dc=example,dc=com", if our domain would be for example "ideas.lab.com", the parent DN would be \
"dc=ideas,dc=lab,dc=com". This configuration it's very often passed with the CN (Common Name) \
in concatenation with the DN (Distinguised Name), which is not the same as parent DN, and the result \
it's very simple, for example.com it is DN: "cn=config,dn=example,dn=com", or for ideas.lab.com \
DN: "cn=config,dn=ideas,dn=lab,dn=com".
One of the key configuration of LDAP is our "DC" or "parent DN" and other terms, which to explain it in a pure pragmatic way, we will use some examples: we use per defect example.com as our domain, so the DC (Distinguished Name) that we would use it is **"dc=example,dc=com"**, instead, if our domain would be for example "ideas.lab.com", the parent DN would be "dc=ideas,dc=lab,dc=com". This configuration it's very often passed with the CN (Common Name) in concatenation with the DN (Distinguished Name), and the result it's very simple, in the case of the domain example.com, it is **DN: "cn=config,dn=example,dn=com"**, or for ideas.lab.com DN: "cn=config,dn=ideas,dn=lab,dn=com".
## _Inside the ldapdock image container_