Changes for page KerberosAndLDAP

Summary

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

Details

Page properties

Content

...	...	@@ -1,4 +1,6 @@
	1	+{{box cssClass="floatinginfobox" title="**Contents**"}}
1	1	{{toc/}}
	3	+{{/box}}
2	2
3	3	= Debian =
4	4
...	...	@@ -11,7 +11,7 @@
11	11	**The guide is for illustration. Expectation is that you do not follow it verbatim but adapt it to your needs.**
12	12
13	13
14		-===== Install packages: =====
	16	+=== Install packages: ===
15	15
16	16	(% class="wikigeneratedid" %)
17	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.
...	...	@@ -20,7 +20,7 @@
20	20	##{{{$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}##
21	21
22	22
23		-===== Load ##kerberos LDAP## schema: =====
	25	+=== Load ##kerberos LDAP## schema: ===
24	24
25	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	26
...	...	@@ -31,7 +31,7 @@
31	31	##{{{$}}}##
32	32
33	33
34		-===== Create Index on krbPrincipalName: =====
	36	+=== Create Index on krbPrincipalName: ===
35	35
36	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.
37	37
...	...	@@ -46,7 +46,7 @@
46	46	##{{{$}}}##
47	47
48	48
49		-===== Create principals kadmin and kdc: =====
	51	+=== Create principals kadmin and kdc: ===
50	50
51	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}##.
52	52
...	...	@@ -98,7 +98,7 @@
98	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	99
100	100
101		-===== Grant kdc and kadmin permissions: =====
	103	+=== Grant kdc and kadmin permissions: ===
102	102
103	103	This switches back to the ##cn=config## DN as you are changing the permissions.
104	104
...	...	@@ -130,7 +130,7 @@
130	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	131
132	132
133		-===== Create your krb5.conf: =====
	135	+=== Create krb5.conf: ===
134	134
135	135	Over to adjusting /etc/krb5.conf so that it will point to the right thing later. It should look something like this:
136	136
...	...	@@ -156,6 +156,9 @@
156	156
157	157	Make sure your designated debian server have ports 88, 464 and 749 open, both for TCP and UDP, in its firewall. 88 is for the kdc, 464 and 749 is for kadmin.
158	158
	161	+
	162	+=== Create kdc.conf: ===
	163	+
159	159	Next, we need to write up /etc/krb5kdc/kdc.conf. Something like this should work
160	160
161	161
...	...	@@ -184,9 +184,10 @@
184	184	}
185	185
186	186
	192	+=== Create kadm5.acl: ===
	193	+
187	187	Then you need to create ##/etc/krb5kdc/kadm5.acl and put in it##
188	188
189		-
190	190	##*/admin@EXAMPLE.COM *##
191	191
192	192
...	...	@@ -193,6 +193,8 @@
193	193	so that administrator principals can run kadmin. Now we are ready to create the domain. And that we do with
194	194
195	195
	202	+=== Create the kerberos domain: ===
	203	+
196	196	#
197	197
198	198	kdb5_ldap_util -D uid=root,cn=users,dc=trudheim,dc=com -H ldaps:~/~/ds723.trudheim.com -r TRUDHEIM.COM create -subtrees dc=trudheim,dc=com -maxtktlife '7 Days' -maxrenewlife '6 Days' -s
...	...	@@ -213,4 +213,7 @@
213	213	Password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
214	214	Re-enter password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
215	215
	224	+
	225	+=== Create the first principals: ===
	226	+
216	216