Changes for page KerberosAndLDAP

Summary

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

Details

Page properties

Content

...	...	@@ -13,7 +13,7 @@
13	13	**The guide is for illustration. Expectation is that you do not follow it verbatim but adapt it to your needs.**
14	14
15	15
16		-===== Install packages: =====
	16	+=== Install packages ===
17	17
18	18	(% class="wikigeneratedid" %)
19	19	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.
...	...	@@ -22,7 +22,7 @@
22	22	##{{{$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}##
23	23
24	24
25		-===== Load ##kerberos LDAP## schema: =====
	25	+=== Load ##kerberos LDAP## schema ===
26	26
27	27	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.
28	28
...	...	@@ -33,7 +33,7 @@
33	33	##{{{$}}}##
34	34
35	35
36		-===== Create Index on krbPrincipalName: =====
	36	+=== Create Index on krbPrincipalName ===
37	37
38	38	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.
39	39
...	...	@@ -48,7 +48,7 @@
48	48	##{{{$}}}##
49	49
50	50
51		-===== Create principals kadmin and kdc: =====
	51	+=== Create principals kadmin and kdc ===
52	52
53	53	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}##.
54	54
...	...	@@ -100,7 +100,7 @@
100	100	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.
101	101
102	102
103		-===== Grant kdc and kadmin permissions: =====
	103	+=== Grant kdc and kadmin permissions ===
104	104
105	105	This switches back to the ##cn=config## DN as you are changing the permissions.
106	106
...	...	@@ -132,7 +132,7 @@
132	132	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.
133	133
134	134
135		-===== Create your krb5.conf: =====
	135	+=== Create krb5.conf ===
136	136
137	137	Over to adjusting /etc/krb5.conf so that it will point to the right thing later. It should look something like this:
138	138
...	...	@@ -158,6 +158,9 @@
158	158
159	159	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.
160	160
	161	+
	162	+=== Create kdc.conf ===
	163	+
161	161	Next, we need to write up /etc/krb5kdc/kdc.conf. Something like this should work
162	162
163	163
...	...	@@ -186,9 +186,10 @@
186	186	}
187	187
188	188
	192	+=== Create kadm5.acl ===
	193	+
189	189	Then you need to create ##/etc/krb5kdc/kadm5.acl and put in it##
190	190
191		-
192	192	##*/admin@EXAMPLE.COM *##
193	193
194	194
...	...	@@ -195,6 +195,8 @@
195	195	so that administrator principals can run kadmin. Now we are ready to create the domain. And that we do with
196	196
197	197
	202	+=== Create the kerberos domain ===
	203	+
198	198	#
199	199
200	200	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
...	...	@@ -215,3 +215,51 @@
215	215	Password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
216	216	Re-enter password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
217	217
	224	+
	225	+=== Create the first regular principals ===
	226	+
	227	+Here, you will run kadmin.local to create first a regular user, and then an admin version of that user.
	228	+
	229	+# kadmin.local
	230	+
	231	+Authenticating as principal root/admin@TRUDHEIM.COM with password.
	232	+kadmin.local:  addprinc user
	233	+
	234	+No policy specified for user@TRUDHEIM.COM; defaulting to no policy
	235	+Enter password for principal "user@TRUDHEIM.COM":
	236	+Re-enter password for principal "user@TRUDHEIM.COM":
	237	+Principal "user@TRUDHEIM.COM" created.
	238	+
	239	+kadmin.local:  addprinc user/admin
	240	+No policy specified for user/admin@TRUDHEIM.COM; defaulting to no policy
	241	+Enter password for principal "user/admin@TRUDHEIM.COM":
	242	+Re-enter password for principal "user/admin@TRUDHEIM.COM":
	243	+Principal "user/admin@TRUDHEIM.COM" created.
	244	+kadmin.local:  q
	245	+
	246	+#
	247	+
	248	+Worth to note here is that [[user@EXAMPLE.COM>>mailto:user@EXAMPLE.COM]] and [[user/admin@EXAMPLE.COM>>mailto:user/admin@EXAMPLE.COM]] can have (and should have) different passwords as the admin variant is allowed to do things to the kerberos database. And this is why you want to have the registering of failures to login enabled. Should you have the system exposed to the internet, you can and should expect intrusion attempts. Having Kerberos deployed makes it harder for perpetrators to gain access, but not impossible.
	249	+
	250	+If you later kerberise your storage and leverage it for NFS4 mounts from your NAS, you can have NFS exposed to the internet as well. Unless someone has a valid kerberos ticket, even if they somehow could mount the share, they see nothing on it without the krbtgt.
	251	+
	252	+
	253	+=== Test your new principal ===
	254	+
	255	+$ kinit [[user@EXAMPLE.COM>>mailto:user@EXAMPLE.COM]]
	256	+
	257	+Password for user@EXAMPLE.COM:
	258	+
	259	+$ klist
	260	+Ticket cache: FILE:/tmp/krb5cc_1000
	261	+Default principal: user@EXAMPLE.COM
	262	+
	263	+Valid starting     Expires            Service principal
	264	+09/05/24 08:07:35  10/05/24 08:07:35  krbtgt/EXAMPLE.COM@EXAMPLE.COM
	265	+
	266	+$
	267	+
	268	+
	269	+=== Set up pam and sssd ===
	270	+
	271	+