Skip to Content
0 Votes

Changes for page KerberosAndLDAP

Last modified by Sirius Rayner-Karlsson on 2024/05/09 10:54
From version 31.1
edited by Sirius Rayner-Karlsson
on 2024/05/09 05:52
Change comment: There is no comment for this version
To version 35.1
edited by Sirius Rayner-Karlsson
on 2024/05/09 09:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,15 +13,3 @@
1 -(% data-xwiki-non-generated-content="java.util.List" %)
2 -(((
3 -" data-xwiki-parameter-name="title" class="xwiki-metadata-container">**Contents**
4 -)))
5 -
6 -(% data-xwiki-non-generated-content="java.util.List" %)
7 -(((
8 -" class="xwiki-metadata-container">
9 -
10 -{{toc/}}
11 -)))
12 -
13 13  {{box cssClass="floatinginfobox" title="**Contents**"}}
14 14  {{toc/}}
15 15  {{/box}}
... ... @@ -25,7 +25,7 @@
25 25  **The guide is for illustration. Expectation is that you do not follow it verbatim but adapt it to your needs.**
26 26  
27 27  
28 -===== Install packages: =====
16 +=== Install packages ===
29 29  
30 30  (% class="wikigeneratedid" %)
31 31  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.
... ... @@ -34,86 +34,96 @@
34 34  ##{{{$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}##
35 35  
36 36  
37 -===== Load ##kerberos LDAP## schema: =====
25 +=== Load kerberos LDAP schema ===
38 38  
39 -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.
27 +Now you need to load the kerberos schema into the LDAP server on the Synology. Use the ##cn=config## DN.
40 40  
41 41  (% style="color:#400" %)
42 -##{{{$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldaps://nas.example.com/ -D cn=config -W}}}##
43 -##{{{Enter LDAP Password:}}}##
44 -##{{{adding new entry "cn=kerberos,cn=schema,cn=config"}}}##
45 -##{{{$}}}##
30 +##{{{
31 +$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldaps://nas.example.com/ -D cn=config -W
32 +Enter LDAP Password:
33 +adding new entry "cn=kerberos,cn=schema,cn=config"
34 +$
35 +}}}##
46 46  
47 47  
48 -===== Create Index on krbPrincipalName: =====
38 +=== Create Index on krbPrincipalName ===
49 49  
50 -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.
40 +Having an index on the ##krbPrincipalName## improves performance. Synology OpenLDAP does not use ##mdb## format, it uses ##bdb##. Debian ##slapd## 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##. Use the main password you set for the Synology LDAP server. Create a file ##step1.ldif## with the following content:
51 51  
52 52  (% style="color:#400" %)
53 -##{{{$ ldapmodify -H ldaps://nas.example.com/ -D cn=config -W <<EOF}}}##
54 -##{{{dn: olcDatabase={1}bdb,cn=config}}}##
55 -##{{{add: olcDbIndex}}}##
56 -##{{{olcDbIndex: krbPrincipalName eq,pres,sub}}}##
57 -##{{{EOF}}}##
58 -##{{{Enter LDAP Password:}}}##
59 -##{{{modifying entry "olcDatabase={1}bdb,cn=config"}}}##
60 -##{{{$}}}##
43 +##{{{
44 +dn: olcDatabase={1}bdb,cn=config
45 +add: olcDbIndex
46 +olcDbIndex: krbPrincipalName eq,pres,sub
47 +}}}##
61 61  
49 +and apply it with
62 62  
63 -===== Create principals kadmin and kdc: =====
51 +(% style="color:#400" %)
52 +##{{{
53 +$ ldapmodify -H ldaps://nas.example.com/ -D cn=config -W -f step1.ldif
54 +Enter LDAP Password:
55 +modifying entry "olcDatabase={1}bdb,cn=config"
56 +$
57 +}}}##
64 64  
65 -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}##.
66 66  
67 -(% style="color:#400" %)
68 -##{{{$ ldapadd -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
69 -##{{{dn: ou=kerberos,dc=example,dc=com}}}##
70 -##{{{objectClass: organizationalUnit}}}##
71 -##{{{objectClass: top}}}##
72 -##{{{ou: kerberos}}}##
60 +=== Create principals kadmin and kdc ===
73 73  
74 -(% style="color:#400" %)
75 -##{{{dn: cn=kdc,ou=kerberos,dc=example,dc=com}}}##
76 -##{{{cn: kdc}}}##
77 -##{{{sn: kdc}}}##
78 -##{{{objectClass: person}}}##
79 -##{{{objectClass: pwdPolicy}}}##
80 -##{{{pwdAttribute: userPassword}}}##
81 -##{{{pwdMinLength: 8}}}##
82 -##{{{pwdCheckQuality: 2}}}##
83 -##{{{pwdPolicySubentry: cn=kdc,ou=kerberos,dc=example,dc=com}}}##
84 -##{{{userPassword: {SSHA}<password-hash>}}}##
85 -##{{{description: Kerberos KDC Account}}}##
62 +Next, you create and configure two entries which will be used by the Kerberos servers to connect to OpenLDAP. Not running the Kerberos KDC and Admin Server on the same host as OpenLDAP, these steps are required. Keeping things confined, everything will be created under a separate ##organizationalUnit##. My guide differs from the official Debian guide here. Due to Synology OpenLDAP having a strict password policy, it was necessary to adjust the DNs of ##kdc## and ##kadmin##. The official guide use placeholder passwords which does not work with the Synology LDAP server.
63 +Generate the passwords upfront with ##slappasswd -h {SSHA}##. Then create a file ##step2.ldif## with the following content:
86 86  
87 87  (% style="color:#400" %)
88 -##{{{dn: cn=kadmin,ou=kerberos,dc=example,dc=com}}}##
89 -##{{{cn: kadmin}}}##
90 -##{{{sn: kadmin}}}##
91 -##{{{objectClass: person}}}##
92 -##{{{objectClass: pwdPolicy}}}##
93 -##{{{pwdAttribute: userPassword}}}##
94 -##{{{pwdMinLength: 8}}}##
95 -##{{{pwdCheckQuality: 2}}}##
96 -##{{{pwdPolicySubentry: cn=kadmin,ou=kerberos,dc=example,dc=com}}}##
97 -##{{{userPassword: {SSHA}<password-hash>}}}##
98 -##{{{description: Kerberos KDC Account}}}##
99 -##{{{EOF}}}##
100 -##{{{Enter LDAP Password:}}}##
66 +##{{{
67 +dn: ou=kerberos,dc=example,dc=com
68 +objectClass: organizationalUnit
69 +objectClass: top
70 +ou: kerberos
101 101  
102 -(% style="color:#400" %)
103 -##{{{adding new entry "ou=kerberos,dc=example,dc=com"}}}##
72 +dn: cn=kdc,ou=kerberos,dc=example,dc=com
73 +cn: kdc
74 +sn: kdc
75 +objectClass: person
76 +objectClass: pwdPolicy
77 +pwdAttribute: userPassword
78 +pwdMinLength: 8
79 +pwdCheckQuality: 2
80 +pwdPolicySubentry: cn=kdc,ou=kerberos,dc=example,dc=com
81 +userPassword: {SSHA}<password-hash>
82 +description: Kerberos KDC Account
104 104  
105 -(% style="color:#400" %)
106 -##{{{adding new entry "cn=kdc,ou=kerberos,dc=example,dc=com"}}}##
84 +dn: cn=kadmin,ou=kerberos,dc=example,dc=com
85 +cn: kadmin
86 +sn: kadmin
87 +objectClass: person
88 +objectClass: pwdPolicy
89 +pwdAttribute: userPassword
90 +pwdMinLength: 8
91 +pwdCheckQuality: 2
92 +pwdPolicySubentry: cn=kadmin,ou=kerberos,dc=example,dc=com
93 +userPassword: {SSHA}<password-hash>
94 +description: Kerberos KDC Account
95 +}}}##
107 107  
97 +Apply it with
98 +
108 108  (% style="color:#400" %)
109 -##{{{adding new entry "cn=kadmin,ou=kerberos,dc=example,dc=com"}}}##
100 +##{{{
101 +$ ldapadd -H ldaps://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W -f step2.ldif
102 +Enter LDAP Password:
110 110  
104 +adding new entry "ou=kerberos,dc=example,dc=com"
111 111  
112 -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.
106 +adding new entry "cn=kdc,ou=kerberos,dc=example,dc=com"
113 113  
108 +adding new entry "cn=kadmin,ou=kerberos,dc=example,dc=com"
109 +}}}##
114 114  
115 -===== Grant kdc and kadmin permissions: =====
116 116  
112 +
113 +=== Grant kdc and kadmin permissions ===
114 +
117 117  This switches back to the ##cn=config## DN as you are changing the permissions.
118 118  
119 119  $ ldapmodify -H ldaps:~/~/ds723.trudheim.com -W -D cn=config <<EOF
... ... @@ -144,7 +144,7 @@
144 144  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.
145 145  
146 146  
147 -===== Create your krb5.conf: =====
145 +=== Create krb5.conf ===
148 148  
149 149  Over to adjusting /etc/krb5.conf so that it will point to the right thing later. It should look something like this:
150 150  
... ... @@ -170,6 +170,9 @@
170 170  
171 171  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.
172 172  
171 +
172 +=== Create kdc.conf ===
173 +
173 173  Next, we need to write up /etc/krb5kdc/kdc.conf. Something like this should work
174 174  
175 175  
... ... @@ -198,9 +198,10 @@
198 198   }
199 199  
200 200  
202 +=== Create kadm5.acl ===
203 +
201 201  Then you need to create ##/etc/krb5kdc/kadm5.acl and put in it##
202 202  
203 -
204 204  ##*/admin@EXAMPLE.COM *##
205 205  
206 206  
... ... @@ -207,6 +207,8 @@
207 207  so that administrator principals can run kadmin. Now we are ready to create the domain. And that we do with
208 208  
209 209  
212 +=== Create the kerberos domain ===
213 +
210 210  #
211 211  
212 212  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
... ... @@ -227,4 +227,51 @@
227 227  Password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
228 228  Re-enter password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
229 229  
234 +
235 +=== Create the first regular principals ===
236 +
237 +Here, you will run kadmin.local to create first a regular user, and then an admin version of that user.
238 +
239 +# kadmin.local
240 +
241 +Authenticating as principal root/admin@TRUDHEIM.COM with password.
242 +kadmin.local:  addprinc user
243 +
244 +No policy specified for user@TRUDHEIM.COM; defaulting to no policy
245 +Enter password for principal "user@TRUDHEIM.COM":
246 +Re-enter password for principal "user@TRUDHEIM.COM":
247 +Principal "user@TRUDHEIM.COM" created.
248 +
249 +kadmin.local:  addprinc user/admin
250 +No policy specified for user/admin@TRUDHEIM.COM; defaulting to no policy
251 +Enter password for principal "user/admin@TRUDHEIM.COM":
252 +Re-enter password for principal "user/admin@TRUDHEIM.COM":
253 +Principal "user/admin@TRUDHEIM.COM" created.
254 +kadmin.local:  q
255 +
256 +#
257 +
258 +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.
259 +
260 +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.
261 +
262 +
263 +=== Test your new principal ===
264 +
265 +$ kinit [[user@EXAMPLE.COM>>mailto:user@EXAMPLE.COM]]
266 +
267 +Password for user@EXAMPLE.COM:
268 +
269 +$ klist
270 +Ticket cache: FILE:/tmp/krb5cc_1000
271 +Default principal: user@EXAMPLE.COM
272 +
273 +Valid starting     Expires            Service principal
274 +09/05/24 08:07:35  10/05/24 08:07:35  krbtgt/EXAMPLE.COM@EXAMPLE.COM
275 +
276 +$
277 +
278 +
279 +=== Set up pam and sssd ===
280 +
230 230