Changes for page KerberosAndLDAP
Last modified by Sirius Rayner-Karlsson on 2024/05/09 10:54
From version 27.1
edited by Sirius Rayner-Karlsson
on 2024/05/07 10:18
on 2024/05/07 10:18
Change comment:
There is no comment for this version
To version 7.1
edited by Sirius Rayner-Karlsson
on 2024/05/01 17:00
on 2024/05/01 17:00
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,98 +3,77 @@ 1 -{{toc/}} 2 - 3 3 = Debian = 4 4 5 -The guide I followed was https://wiki.debian.org/LDAP/OpenLDAPSetup#Kerberos which while it worked required some minor tweaks. I obtained edit privileges for the Debian Wiki and updated the guide with the fixes that I found. I however have a Synology NAS and that can run an LDAP Server. So this guide differs from the upstream Debian Guide. 3 +The guide I followed was [[https:~~/~~/wiki.debian.org/LDAP/OpenLDAPSetup#Kerberos>>https://wiki.debian.org/LDAP/OpenLDAPSetup#Kerberos]] which while it worked required some minor tweaks. I obtained edit privileges for the Debian Wiki and updated the guide with the fixes that I found. I however have a Synology NAS and that can run an LDAP Server. So this guide differs a little from the upstream Debian Guide. 6 6 7 - Assumption ishatyou haveinstalledtheLDAP Serverpackage onyour NASand gonethroughinitialconfiguration steps, soit hasa domain, thereis aDN younbindsand so forth. Itislsoassumedyou havea Debiansystem (12.5orlater,thoughthis guide shouldwork with11.xand likely 10.xaswell) that will become your KDCandKAdminserver.5 +First, install the packages containing the LDAP-enabled Kerberos servers ([[krb5-kdc-ldap>>url:https://packages.debian.org/krb5-kdc-ldap]] and [[krb5-admin-server>>url:https://packages.debian.org/krb5-admin-server]]) and the [[schema2ldif>>url:https://packages.debian.org/schema2ldif]] tool: 8 8 9 -Recommendation is that you create actual ##.ldif## files rather than use here-documents as used in this guide. It is far easier to make adjustments to things if you have a file to edit rather than having to type it all out again or paste it and then have to try and make edits to it without making mistakes. 7 +### 8 +$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif 9 +### 10 10 11 -**The guide is for illustration. Expectation is that you do not follow it verbatim but adapt it to your needs.** 12 12 12 +Then load the ##kerberos## schema: 13 13 14 - =====Installpackages: =====14 +{{{$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldap:~/~/nas.fqdn/ -D uid=root,cn=users,dc=example,dc=com 15 15 16 -(% class="wikigeneratedid" %) 17 -The packages you need are [[krb5-kdc-ldap>>url:https://packages.debian.org/krb5-kdc-ldap]], [[krb5-admin-server>>url:https://packages.debian.org/krb5-admin-server]] for the actual KDC and [[schema2ldif>>url:https://packages.debian.org/schema2ldif]] plus [[slapd>>https://packages.debian.org/search?keywords=slapd]] for adding the schema and ##slappasswd##. They are to be installed on your designated Debian host. 16 +adding new entry "cn=kerberos,cn=schema,cn=config" 18 18 19 -(% style="color:#400" %) 20 -##{{{$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}## 18 +}}} 21 21 22 22 23 - =====Load ##kerberosLDAP## schema:=====21 +And add an index on the ##krbPrincipalName## (improves performance and also suppresses some log messages if ##slapd## is configured to log more than default) for the database(s) where you intend to store Kerberos data: 24 24 25 - Nowyou needtoloadthe kerberos schemainto the LDAPserver on the Synology.Andhere youneedto use the ##cn=config## DN.23 +{{{# ldapmodify -H ldap:~/~/nas.fqhn <<EOF 26 26 27 -(% style="color:#400" %) 28 -##{{{$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldaps://nas.example.com/ -D cn=config -W}}}## 29 -##{{{Enter LDAP Password:}}}## 30 -##{{{adding new entry "cn=kerberos,cn=schema,cn=config"}}}## 31 -##{{{$}}}## 25 +dn: olcDatabase={1}bdb,cn=config 32 32 27 +add: olcDbIndex 33 33 34 - ===== CreateIndexonkrbPrincipalName:=====29 +olcDbIndex: krbPrincipalName eq,pres,sub 35 35 36 - Having an index on the ##krbPrincipalName## improves performance and also suppresses some log messages if ##slapd## is configured to log more than default for the database(s) where you intend to store Kerberos data. As this isOpenLDAP on the Synology, it does not use ##mdb## format, it uses ##bdb##. If you install ##slapd## on Debian, it uses ##mdb## format. It is different database format, but the principle is the same. Again, as you are modifying config, the DN is ##cn=config##. Interestingly, it is still the main password you set for the Synology LDAP server.31 +EOF 37 37 38 -(% style="color:#400" %) 39 -##{{{$ ldapmodify -H ldaps://nas.example.com/ -D cn=config -W <<EOF}}}## 40 -##{{{dn: olcDatabase={1}bdb,cn=config}}}## 41 -##{{{add: olcDbIndex}}}## 42 -##{{{olcDbIndex: krbPrincipalName eq,pres,sub}}}## 43 -##{{{EOF}}}## 44 -##{{{Enter LDAP Password:}}}## 45 -##{{{modifying entry "olcDatabase={1}bdb,cn=config"}}}## 46 -##{{{$}}}## 33 +modifying entry "olcDatabase={1}bdb,cn=config" 47 47 35 +}}} 48 48 49 -===== Create principals kadmin and kdc: ===== 50 50 51 -Next, you create and configure two entries which will be used by the Kerberos servers to connect to OpenLDAP. AsyouwillnotruntheKerberosKDCandAdminServeron the samehost asOpenLDAP, these steps arerequired. In order to keep things nicely separated, everything will be created under a separate ##organizationalUnit##.I divergefromtheofficialDebianguidehereasI do not agree with the DN theyuse. I also hadto make changeso theDNsof##kdc##and##kadmin##due to ##pwdPolicy## appliedby Synology to their LDAPserver. The official guide will haveyou use placeholder passwordsandthat doesnotwork withtheSynologyLDAPserver.Youneed to generate them upfront with ##slappasswd -h {SSHA}##.38 +Next, you need to create and configure two entries which will be used by the Kerberos servers to connect to OpenLDAP. If you are running Kerberos and OpenLDAP on the same system, these steps are optional, but recommended. In order to keep things nicely separated, everything will be created under a separate ##organizationalUnit##. Note that a simple bind (##-x -D##) is used instead of an ##EXTERNAL## bind since write access to the dc=example,dc=com DIT is necessary: 52 52 53 -(% style="color:#400" %) 54 -##{{{$ ldapadd -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}## 55 -##{{{dn: ou=kerberos,dc=example,dc=com}}}## 56 -##{{{objectClass: organizationalUnit}}}## 57 -##{{{objectClass: top}}}## 58 -##{{{ou: kerberos}}}## 59 59 60 -(% style="color:#400" %) 61 -##{{{dn: cn=kdc,ou=kerberos,dc=example,dc=com}}}## 62 -##{{{cn: kdc}}}## 63 -##{{{sn: kdc}}}## 64 -##{{{objectClass: person}}}## 65 -##{{{objectClass: pwdPolicy}}}## 66 -##{{{pwdAttribute: userPassword}}}## 67 -##{{{pwdMinLength: 8}}}## 68 -##{{{pwdCheckQuality: 2}}}## 69 -##{{{pwdPolicySubentry: cn=kdc,ou=kerberos,dc=example,dc=com}}}## 70 -##{{{userPassword: {SSHA}<password-hash>}}}## 71 -##{{{description: Kerberos KDC Account}}}## 41 +{{{# ldapadd -x -D cn=admin,dc=example,dc=com -W <<EOF 42 +dn: ou=Services,dc=example,dc=com 43 +objectClass: organizationalUnit 44 +objectClass: top 45 +ou: Services 72 72 73 -(% style="color:#400" %) 74 -##{{{dn: cn=kadmin,ou=kerberos,dc=example,dc=com}}}## 75 -##{{{cn: kadmin}}}## 76 -##{{{sn: kadmin}}}## 77 -##{{{objectClass: person}}}## 78 -##{{{objectClass: pwdPolicy}}}## 79 -##{{{pwdAttribute: userPassword}}}## 80 -##{{{pwdMinLength: 8}}}## 81 -##{{{pwdCheckQuality: 2}}}## 82 -##{{{pwdPolicySubentry: cn=kadmin,ou=kerberos,dc=example,dc=com}}}## 83 -##{{{userPassword: {SSHA}<password-hash>}}}## 84 -##{{{description: Kerberos KDC Account}}}## 85 -##{{{EOF}}}## 86 -##{{{Enter LDAP Password:}}}## 47 +dn: ou=kerberos,ou=Services,dc=example,dc=com 48 +objectClass: organizationalUnit 49 +objectClass: top 50 +ou: kerberos 87 87 88 -(% style="color:#400" %) 89 -##{{{adding new entry "ou=kerberos,dc=example,dc=com"}}}## 52 +dn: uid=kdc,ou=kerberos,ou=Services,dc=example,dc=com 53 +uid: kdc 54 +objectClass: account 55 +objectClass: simpleSecurityObject 56 +userPassword: {CRYPT}x 57 +description: Kerberos KDC Account 90 90 91 -(% style="color:#400" %) 92 -##{{{adding new entry "cn=kdc,ou=kerberos,dc=example,dc=com"}}}## 59 +dn: uid=kadmin,ou=kerberos,ou=Services,dc=example,dc=com 60 +uid: kadmin 61 +objectClass: account 62 +objectClass: simpleSecurityObject 63 +userPassword: {CRYPT}x 64 +description: Kerberos Admin Server Account 65 +EOF 66 +Enter LDAP Password: SECRET 93 93 94 -(% style="color:#400" %) 95 -##{{{adding new entry "cn=kadmin,ou=kerberos,dc=example,dc=com"}}}## 68 +adding new entry "ou=Services,dc=example,dc=com" 96 96 97 - Synology LDAP server did not likeaddinguserswithplaceholderpasswords,because Synology puts in placepassword policies. Hencechanging this to a ##cn## instead of a ##uid##. It seems to haveworkedout fine as my KDC is fully functioning.70 +adding new entry "ou=kerberos,ou=Services,dc=example,dc=com" 98 98 72 +adding new entry "uid=kdc,ou=kerberos,ou=Services,dc=example,dc=com" 73 + 74 +adding new entry "uid=kadmin,ou=kerberos,ou=Services,dc=example,dc=com"}}} 75 + 76 + 77 +