Changes for page KerberosAndLDAP

Summary

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

Details

Page properties

Content

...	...	@@ -1,17 +1,19 @@
1	1	= Debian =
2	2
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.
	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.
4	4
	5	+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.
5	5
6		-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:
7	7
8		-(% style="color:red" %)
	8	+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 on your Debian host:
	9	+
	10	+(% style="color:#400" %)
9	9	##{{{$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}##
10	10
11	11
12	12	Then load the ##kerberos## schema:
13	13
14		-(% style="color:red" %)
	16	+(% style="color:#400" %)
15	15	##{{{$ 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 -W}}}##
16	16	##{{{Enter LDAP Password:}}}##
17	17	##{{{adding new entry "cn=kerberos,cn=schema,cn=config"}}}##
...	...	@@ -20,7 +20,7 @@
20	20
21	21	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##:
22	22
23		-(% style="color:red" %)
	25	+(% style="color:#400" %)
24	24	##{{{$ ldapmodify -H ldap://nas.fqdn/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
25	25	##{{{dn: olcDatabase={1}bdb,cn=config}}}##
26	26	##{{{add: olcDbIndex}}}##
...	...	@@ -33,7 +33,7 @@
33	33
34	34	Next, you need to 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##.
35	35
36		-(% style="color:red" %)
	38	+(% style="color:#400" %)
37	37	##{{{$ ldapadd -H ldap://nas.fqdn/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
38	38	##{{{dn: ou=Services,dc=example,dc=com}}}##
39	39	##{{{objectClass: organizationalUnit}}}##
...	...	@@ -72,7 +72,7 @@
72	72
73	73	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:
74	74
75		-(% style="color:red" %)
	77	+(% style="color:#400" %)
76	76	##{{{dn: cn=kadmin,ou=kerberos,ou=Services,dc=example,dc=com}}}##
77	77	##{{{sn: kadmin}}}##
78	78	##{{{cn: kadmin}}}##
...	...	@@ -90,5 +90,3 @@
90	90	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.
91	91
92	92	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.
93		-
94		-