Changes for page KerberosAndLDAP

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,98 +3,65 @@
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 a little 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		-I will assume that you have installed the LDAP Server package on your NAS and gone through initial configuration steps, so it has a domain, there is a DN you can bind as and so forth. The Synology NAS can be leveraged for a multitude of things, and running DNS, DHCP, WebServices and Containers are but a few. I will also assume you have a Debian system (12.5 or later, though this guide should work with 11.x and likely 10.x as well) that will become your KDC and KAdmin server.
	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		-I also recommend 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. The guide is for illustration and expectation is that you do not follow it verbatim but adapt it to your needs.
	7	+{{{# apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}
10	10
	9	+Then load the ##kerberos## schema:
11	11
12		-===== Install the packages containing the LDAP-enabled Kerberos servers: =====
13	13
14		-(% class="wikigeneratedid" %)
15		-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~#~#.
	12	+{{{# zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -Q -Y EXTERNAL -H ldapi:///
	13	+adding new entry "cn=kerberos,cn=schema,cn=config"}}}
16	16
17		-(% style="color:#400" %)
18		-##{{{$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}##
	15	+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:
19	19
20	20
21		-===== Load the ##kerberos## schema into the LDAP server on your Synology: =====
	18	+{{{# ldapmodify -Q -Y EXTERNAL -H ldapi:/// <<EOF
	19	+dn: olcDatabase={1}mdb,cn=config
	20	+add: olcDbIndex
	21	+olcDbIndex: krbPrincipalName eq,pres,sub
	22	+EOF
22	22
23		-(% style="color:#400" %)
24		-##{{{$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W}}}##
25		-##{{{Enter LDAP Password:}}}##
26		-##{{{adding new entry "cn=kerberos,cn=schema,cn=config"}}}##
27		-##{{{$}}}##
	24	+modifying entry "olcDatabase={1}mdb,cn=config"}}}
28	28
	26	+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:
29	29
30		-===== Create Index on krbPrincipalName: =====
31	31
32		-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 is OpenLDAP on the Synology, it does not use ~#~###mdb~#~### format, it uses ##~#~#bdb~#~###. If you install ~#~#slapd~#~# on Debian, it uses ~#~#mdb~#~# format.
	29	+{{{# ldapadd -x -D cn=admin,dc=example,dc=com -W <<EOF
	30	+dn: ou=Services,dc=example,dc=com
	31	+objectClass: organizationalUnit
	32	+objectClass: top
	33	+ou: Services
33	33
34		-(% style="color:#400" %)
35		-##{{{$ ldapmodify -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
36		-##{{{dn: olcDatabase={1}bdb,cn=config}}}##
37		-##{{{add: olcDbIndex}}}##
38		-##{{{olcDbIndex: krbPrincipalName eq,pres,sub}}}##
39		-##{{{EOF}}}##
40		-##{{{Enter LDAP Password:}}}##
41		-##{{{modifying entry "olcDatabase={1}bdb,cn=config"}}}##
42		-##{{{$}}}##
	35	+dn: ou=kerberos,ou=Services,dc=example,dc=com
	36	+objectClass: organizationalUnit
	37	+objectClass: top
	38	+ou: kerberos
43	43
	40	+dn: uid=kdc,ou=kerberos,ou=Services,dc=example,dc=com
	41	+uid: kdc
	42	+objectClass: account
	43	+objectClass: simpleSecurityObject
	44	+userPassword: {CRYPT}x
	45	+description: Kerberos KDC Account
44	44
45		-===== Create the two principals kadmin and kdc: =====
	47	+dn: uid=kadmin,ou=kerberos,ou=Services,dc=example,dc=com
	48	+uid: kadmin
	49	+objectClass: account
	50	+objectClass: simpleSecurityObject
	51	+userPassword: {CRYPT}x
	52	+description: Kerberos Admin Server Account
	53	+EOF
	54	+Enter LDAP Password: SECRET
46	46
47		-Next, you create and configure two entries which will be used by the Kerberos servers to connect to OpenLDAP. As you will not run the Kerberos KDC and Admin Server on the same host as OpenLDAP, these steps are required. In order to keep things nicely separated, everything will be created under a separate ##organizationalUnit##. I diverge from the official Debian guide here as I do not agree with the DN they use. I also had to make changes to the DNs of ~#~#kdc~#~# and ~#~#kadmin~#~# due to ~#~#pwdPolicy~#~# applied by Synology to their LDAP server. The official guide will have you use placeholder passwords and that does not work with the Synology LDAP server. You need to generate them upfront with ~#~#slappasswd~#~#.
	56	+adding new entry "ou=Services,dc=example,dc=com"
48	48
49		-(% style="color:#400" %)
50		-##{{{$ ldapadd -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
51		-##{{{dn: ou=kerberos,dc=example,dc=com}}}##
52		-##{{{objectClass: organizationalUnit}}}##
53		-##{{{objectClass: top}}}##
54		-##{{{ou: kerberos}}}##
55		-## ##
56		-##{{{dn: uid=kdc,ou=kerberos,dc=example,dc=com}}}##
57		-##{{{uid: kdc}}}##
58		-##{{{objectClass: account}}}##
59		-##{{{objectClass: simpleSecurityObject}}}##
60		-##{{{userPassword: {CRYPT}x}}}##
61		-##{{{description: Kerberos KDC Account}}}##
62		-## ##
63		-##{{{dn: uid=kadmin,ou=kerberos,dc=example,dc=com}}}##
64		-##{{{uid: kadmin}}}##
65		-##{{{objectClass: account}}}##
66		-##{{{objectClass: simpleSecurityObject}}}##
67		-##{{{userPassword: {CRYPT}x}}}##
68		-##{{{description: Kerberos Admin Server Account}}}##
69		-##{{{EOF}}}##
70		-##{{{Enter LDAP Password:}}}##
71		-## ##
72		-##{{{adding new entry "ou=kerberos,dc=example,dc=com"}}}##
73		-## ##
74		-##{{{adding new entry "uid=kdc,ou=kerberos,dc=example,dc=com"}}}##
75		-## ##
76		-##{{{adding new entry "uid=kadmin,ou=kerberos,dc=example,dc=com"}}}##
	58	+adding new entry "ou=kerberos,ou=Services,dc=example,dc=com"
77	77
	60	+adding new entry "uid=kdc,ou=kerberos,ou=Services,dc=example,dc=com"
78	78
79		-Now, it was at this point that I had a problem, because the LDAP server on the Synology did not like adding users with placeholder passwords, because Synology puts in place password policies. I ended up working around it using a different construct:
	62	+adding new entry "uid=kadmin,ou=kerberos,ou=Services,dc=example,dc=com"}}}
80	80
81		-(% style="color:#400" %)
82		-##{{{dn: cn=kadmin,ou=kerberos,ou=Services,dc=example,dc=com}}}##
83		-##{{{sn: kadmin}}}##
84		-##{{{cn: kadmin}}}##
85		-##{{{objectClass: person}}}##
86		-##{{{objectClass: pwdPolicy}}}##
87		-##{{{pwdAttribute: userPassword}}}##
88		-##{{{pwdMinLength: 8}}}##
89		-##{{{pwdCheckQuality: 2}}}##
90		-##{{{pwdPolicySubentry: cn=kadmin,ou=kerberos,ou=Services,dc=example,dc=com}}}##
91		-##{{{userPassword: {SSHA}<hashed password>}}}##
92		-##{{{description: Kerberos Admin Server Account}}}##
93	93
94		-and that seems to have worked out fine as my KDC is fully functioning.
95		-
96		-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.
97		-
98		-A note on the above workaround. In order to add a password policy on ##kadmin## and ##kdc## in LDAP, they have to have an attribute that is "physical". And when adding that object class the entries could no longer be a ##uid##. Hence the ##sn## and ##cn## parts. I spent a fair time looking things up as whenever I thought I made progress, something else turned out to be a blocker. When you create the ##{SSHA}## password hash, use ##slappasswd## from the ##slapd## package.
	65	+