Changes for page KerberosAndLDAP

Summary

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

Details

Page properties

Content

...	...	@@ -2,26 +2,30 @@
2	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.
	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.
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.
	7	+Assumption is 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. It is also assumed 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.
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.
	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.
10	10
	11	+**The guide is for illustration. Expectation is that you do not follow it verbatim but adapt it to your needs.**
11	11
12		-===== Install the packages containing the LDAP-enabled Kerberos servers: =====
13	13
	14	+===== Install packages: =====
	15	+
14	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~#~#.
	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	16
17	17	(% style="color:#400" %)
18	18	##{{{$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}##
19	19
20	20
21		-===== Load the ##kerberos## schema into the LDAP server on your Synology: =====
	23	+===== Load ##kerberos LDAP## schema: =====
22	22
	25	+Now you need to load the kerberos schema into the LDAP server on the Synology. And here you need to use the ##cn=config## DN.
	26	+
23	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}}}##
	28	+##{{{$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldaps://nas.example.com/ -D cn=config -W}}}##
25	25	##{{{Enter LDAP Password:}}}##
26	26	##{{{adding new entry "cn=kerberos,cn=schema,cn=config"}}}##
27	27	##{{{$}}}##
...	...	@@ -29,10 +29,10 @@
29	29
30	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.
	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 is OpenLDAP 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.
33	33
34	34	(% style="color:#400" %)
35		-##{{{$ ldapmodify -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
	39	+##{{{$ ldapmodify -H ldaps://nas.example.com/ -D cn=config -W <<EOF}}}##
36	36	##{{{dn: olcDatabase={1}bdb,cn=config}}}##
37	37	##{{{add: olcDbIndex}}}##
38	38	##{{{olcDbIndex: krbPrincipalName eq,pres,sub}}}##
...	...	@@ -42,9 +42,9 @@
42	42	##{{{$}}}##
43	43
44	44
45		-===== Create the two principals kadmin and kdc: =====
	49	+===== Create principals kadmin and kdc: =====
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~#~#.
	51	+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 -h {SSHA}##.
48	48
49	49	(% style="color:#400" %)
50	50	##{{{$ ldapadd -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
...	...	@@ -52,47 +52,77 @@
52	52	##{{{objectClass: organizationalUnit}}}##
53	53	##{{{objectClass: top}}}##
54	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}}}##
	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>}}}##
61	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"}}}##
77	77
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:
80		-
81	81	(% style="color:#400" %)
82		-##{{{dn: cn=kadmin,ou=kerberos,ou=Services,dc=example,dc=com}}}##
83		-##{{{sn: kadmin}}}##
	74	+##{{{dn: cn=kadmin,ou=kerberos,dc=example,dc=com}}}##
84	84	##{{{cn: kadmin}}}##
	76	+##{{{sn: kadmin}}}##
85	85	##{{{objectClass: person}}}##
86	86	##{{{objectClass: pwdPolicy}}}##
87	87	##{{{pwdAttribute: userPassword}}}##
88	88	##{{{pwdMinLength: 8}}}##
89	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}}}##
	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:}}}##
93	93
94		-and that seems to have worked out fine as my KDC is fully functioning.
	88	+(% style="color:#400" %)
	89	+##{{{adding new entry "ou=kerberos,dc=example,dc=com"}}}##
95	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.
	91	+(% style="color:#400" %)
	92	+##{{{adding new entry "cn=kdc,ou=kerberos,dc=example,dc=com"}}}##
97	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.
	94	+(% style="color:#400" %)
	95	+##{{{adding new entry "cn=kadmin,ou=kerberos,dc=example,dc=com"}}}##
	96	+
	97	+
	98	+Synology LDAP server did not like adding users with placeholder passwords, because Synology puts in place password policies. Hence changing this to a ##cn## instead of a ##uid##. It seems to have worked out fine as my KDC is fully functioning.
	99	+
	100	+
	101	+===== Grant kdc and kadmin permissions: =====
	102	+
	103	+This switches back to the ##cn=config## DN as you are changing the permissions.
	104	+
	105	+$ ldapmodify -H ldaps:~/~/ds723.trudheim.com -W -D cn=config <<EOF
	106	+
	107	+dn: olcDatabase={1}bdb,cn=config
	108	+add: olcAccess
	109	+olcAccess: {0}to attrs=krbPrincipalKey
	110	+ by anonymous auth
	111	+ by dn.exact="cn=kdc,ou=kerberos,dc=trudheim,dc=com" write
	112	+ by dn.exact="cn=kadmin,ou=kerberos,dc=trudheim,dc=com" write
	113	+ by self write
	114	+ by * none
	115	+-
	116	+add: olcAccess
	117	+olcAccess: {1}to dn.subtree="cn=krbContainer,ou=kerberos,dc=example,dc=com"
	118	+ by dn.exact="cn=kdc,ou=kerberos,dc=trudheim,dc=com" write
	119	+ by dn.exact="cn=kadmin,ou=kerberos,dc=trudheim,dc=com" write
	120	+ by * none
	121	+
	122	+EOF
	123	+
	124	+Enter LDAP Password:
	125	+modifying entry "olcDatabase={1}bdb,cn=config"
	126	+
	127	+$
	128	+
	129	+
	130	+Note that we now reference our kdc and kadmin accounts and we grant them permission to the krbContainer which will house all our kerberos principals. Give both of them write access, because we do want to have the ability to track last login and lock accounts if there are login failures. We like security.
	131	+
	132	+