0 Votes

Changes for page KerberosAndLDAP

Last modified by Sirius Rayner-Karlsson on 2024/05/09 10:54

From version 17.1
edited by Sirius Rayner-Karlsson
on 2024/05/01 17:44
Change comment: There is no comment for this version
To version 16.1
edited by Sirius Rayner-Karlsson
on 2024/05/01 17:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -80,6 +80,5 @@
80 80  ##{{{userPassword: {SSHA}<hashed password>}}}##
81 81  ##{{{description: Kerberos Admin Server Account}}}##
82 82  
83 -and that seems to have worked out fine as my KDC is fully functioning. It required modifying the rest of the guide with the fact that it no longer was ##uid=kadmin## and ##uid=kdc##, but rather ##cn=kadmin## and ##cn=kdc##. The most important thing is that it works. As an aside, I am not sure it is required to have two nested Organisation Units, ##Services## and ##kerberos## - so I will likely re-deploy and get rid of the ##Services## Organisational Unit altogether. It shortens the DN's used for binds to LDAP and limits the risk for typos. I also find it highly unlikely that deploying this in a real organisation that there would be an existing Organisational Unit called '##kerberos##' while the risk for there being an existing department called '##Services##' is much more likely.
84 -
83 +and that seems to have worked out fine as my KDC is fully functioning. It required modifying the rest of the guide with the fact that it no longer was ##uid=kadmin## and ##uid=kdc##, but rather ##cn=kadmin## and ##cn=kdc##. The most important thing is that it works.
85 85