From 5c7631a297753b3b9a17a889bb5519592efd8593 Mon Sep 17 00:00:00 2001 From: Marisa Date: Wed, 8 Oct 2025 11:36:09 -0400 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ae301b3..0fb0e36 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ If you wish (and it is recommended in development) to save the configuration and ``` `Parameters explanation:`with -h we are specifying the name of the host, we are using example.com, this is very important. -i tells docker to run in an interactive way instead of running the container in the background. -t goes in hand with -i, and allocates a tty (terminal) so we can run commands. -v mounts a volume to save information (we use one to save the data and another one to save the configuration). -## _Explaining DN, parentDN, CN, and DC as parameters_ +## _Explaining DN, parentDN, CN, and DC_ 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".