Skip to Content
0 Votes

Changes for page KerberosAndLDAP

Last modified by Sirius Rayner-Karlsson on 2024/05/09 10:54
From version 26.1
edited by Sirius Rayner-Karlsson
on 2024/05/06 03:16
Change comment: There is no comment for this version
To version 34.1
edited by Sirius Rayner-Karlsson
on 2024/05/09 06:09
Change comment: There is no comment for this version

Summary

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,23 +20,23 @@
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 -Now you need to load the kerberos schema into the LDAP server on the Synology.
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.
26 26  
27 27  (% style="color:#400" %)
28 -##{{{$ 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}}}##
30 +##{{{$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldaps://nas.example.com/ -D cn=config -W}}}##
29 29  ##{{{Enter LDAP Password:}}}##
30 30  ##{{{adding new entry "cn=kerberos,cn=schema,cn=config"}}}##
31 31  ##{{{$}}}##
32 32  
33 33  
34 -===== Create Index on krbPrincipalName: =====
36 +=== Create Index on krbPrincipalName ===
35 35  
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.
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.
37 37  
38 38  (% style="color:#400" %)
39 -##{{{$ ldapmodify -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
41 +##{{{$ ldapmodify -H ldaps://nas.example.com/ -D cn=config -W <<EOF}}}##
40 40  ##{{{dn: olcDatabase={1}bdb,cn=config}}}##
41 41  ##{{{add: olcDbIndex}}}##
42 42  ##{{{olcDbIndex: krbPrincipalName eq,pres,sub}}}##
... ... @@ -46,9 +46,9 @@
46 46  ##{{{$}}}##
47 47  
48 48  
49 -===== Create principals kadmin and kdc: =====
51 +=== Create principals kadmin and kdc ===
50 50  
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##.
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}##.
52 52  
53 53  (% style="color:#400" %)
54 54  ##{{{$ ldapadd -H ldap://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W <<EOF}}}##
... ... @@ -56,47 +56,214 @@
56 56  ##{{{objectClass: organizationalUnit}}}##
57 57  ##{{{objectClass: top}}}##
58 58  ##{{{ou: kerberos}}}##
59 -## ##
60 -##{{{dn: uid=kdc,ou=kerberos,dc=example,dc=com}}}##
61 -##{{{uid: kdc}}}##
62 -##{{{objectClass: account}}}##
63 -##{{{objectClass: simpleSecurityObject}}}##
64 -##{{{userPassword: {CRYPT}x}}}##
61 +
62 +(% style="color:#400" %)
63 +##{{{dn: cn=kdc,ou=kerberos,dc=example,dc=com}}}##
64 +##{{{cn: kdc}}}##
65 +##{{{sn: kdc}}}##
66 +##{{{objectClass: person}}}##
67 +##{{{objectClass: pwdPolicy}}}##
68 +##{{{pwdAttribute: userPassword}}}##
69 +##{{{pwdMinLength: 8}}}##
70 +##{{{pwdCheckQuality: 2}}}##
71 +##{{{pwdPolicySubentry: cn=kdc,ou=kerberos,dc=example,dc=com}}}##
72 +##{{{userPassword: {SSHA}<password-hash>}}}##
65 65  ##{{{description: Kerberos KDC Account}}}##
66 -## ##
67 -##{{{dn: uid=kadmin,ou=kerberos,dc=example,dc=com}}}##
68 -##{{{uid: kadmin}}}##
69 -##{{{objectClass: account}}}##
70 -##{{{objectClass: simpleSecurityObject}}}##
71 -##{{{userPassword: {CRYPT}x}}}##
72 -##{{{description: Kerberos Admin Server Account}}}##
73 -##{{{EOF}}}##
74 -##{{{Enter LDAP Password:}}}##
75 -## ##
76 -##{{{adding new entry "ou=kerberos,dc=example,dc=com"}}}##
77 -## ##
78 -##{{{adding new entry "uid=kdc,ou=kerberos,dc=example,dc=com"}}}##
79 -## ##
80 -##{{{adding new entry "uid=kadmin,ou=kerberos,dc=example,dc=com"}}}##
81 81  
82 -
83 -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:
84 -
85 85  (% style="color:#400" %)
86 -##{{{dn: cn=kadmin,ou=kerberos,ou=Services,dc=example,dc=com}}}##
87 -##{{{sn: kadmin}}}##
76 +##{{{dn: cn=kadmin,ou=kerberos,dc=example,dc=com}}}##
88 88  ##{{{cn: kadmin}}}##
78 +##{{{sn: kadmin}}}##
89 89  ##{{{objectClass: person}}}##
90 90  ##{{{objectClass: pwdPolicy}}}##
91 91  ##{{{pwdAttribute: userPassword}}}##
92 92  ##{{{pwdMinLength: 8}}}##
93 93  ##{{{pwdCheckQuality: 2}}}##
94 -##{{{pwdPolicySubentry: cn=kadmin,ou=kerberos,ou=Services,dc=example,dc=com}}}##
95 -##{{{userPassword: {SSHA}<hashed password>}}}##
96 -##{{{description: Kerberos Admin Server Account}}}##
84 +##{{{pwdPolicySubentry: cn=kadmin,ou=kerberos,dc=example,dc=com}}}##
85 +##{{{userPassword: {SSHA}<password-hash>}}}##
86 +##{{{description: Kerberos KDC Account}}}##
87 +##{{{EOF}}}##
88 +##{{{Enter LDAP Password:}}}##
97 97  
98 -and that seems to have worked out fine as my KDC is fully functioning.
90 +(% style="color:#400" %)
91 +##{{{adding new entry "ou=kerberos,dc=example,dc=com"}}}##
99 99  
100 -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.
93 +(% style="color:#400" %)
94 +##{{{adding new entry "cn=kdc,ou=kerberos,dc=example,dc=com"}}}##
101 101  
102 -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.
96 +(% style="color:#400" %)
97 +##{{{adding new entry "cn=kadmin,ou=kerberos,dc=example,dc=com"}}}##
98 +
99 +
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 +
102 +
103 +=== Grant kdc and kadmin permissions ===
104 +
105 +This switches back to the ##cn=config## DN as you are changing the permissions.
106 +
107 +$ ldapmodify -H ldaps:~/~/ds723.trudheim.com -W -D cn=config <<EOF
108 +
109 +dn: olcDatabase={1}bdb,cn=config
110 +add: olcAccess
111 +olcAccess: {0}to attrs=krbPrincipalKey
112 + by anonymous auth
113 + by dn.exact="cn=kdc,ou=kerberos,dc=trudheim,dc=com" write
114 + by dn.exact="cn=kadmin,ou=kerberos,dc=trudheim,dc=com" write
115 + by self write
116 + by * none
117 +-
118 +add: olcAccess
119 +olcAccess: {1}to dn.subtree="cn=krbContainer,ou=kerberos,dc=example,dc=com"
120 + by dn.exact="cn=kdc,ou=kerberos,dc=trudheim,dc=com" write
121 + by dn.exact="cn=kadmin,ou=kerberos,dc=trudheim,dc=com" write
122 + by * none
123 +
124 +EOF
125 +
126 +Enter LDAP Password:
127 +modifying entry "olcDatabase={1}bdb,cn=config"
128 +
129 +$
130 +
131 +
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 +
134 +
135 +=== Create krb5.conf ===
136 +
137 +Over to adjusting /etc/krb5.conf so that it will point to the right thing later. It should look something like this:
138 +
139 +
140 +{{{[libdefaults]
141 + default_realm = EXAMPLE.COM
142 + dns_lookup_realm = false
143 + dns_lookup_kdc = false
144 + ticket_lifetime = 24h
145 + forwardable = true
146 + proxiable = true
147 + rdns = false
148 +
149 +[realms]
150 + EXAMPLE.COM = {
151 + kdc = debian.example.com
152 + admin_server = debian.example.com
153 + default_domain = example.com
154 + }
155 + [domain_realm]
156 + .example.com = EXAMPLE.COM
157 + example.com = EXAMPLE.COM}}}
158 +
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 +
161 +
162 +=== Create kdc.conf ===
163 +
164 +Next, we need to write up /etc/krb5kdc/kdc.conf. Something like this should work
165 +
166 +
167 +[libdefaults]
168 +
169 +[realms]
170 + TRUDHEIM.COM = {
171 + database_module = openldap_ldapconf
172 + max_life = 7d
173 + max_renewable_life = 6d
174 + }
175 +
176 +[dbdefaults]
177 + ldap_kerberos_container_dn = cn=krbContainer,ou=kerberos,dc=trudheim,dc=com
178 +
179 +[dbmodules]
180 + openldap_ldapconf = {
181 + db_library = kldap
182 + disable_last_success = false
183 + disable_lockout = false
184 + ldap_conns_per_server = 5
185 + ldap_servers = ldaps:~/~/ds723.trudheim.com
186 + ldap_kdc_dn = "cn=kdc,ou=kerberos,dc=trudheim,dc=com"
187 + ldap_kadmind_dn = "cn=kadmin,ou=kerberos,dc=trudheim,dc=com"
188 + ldap_service_password_file = /etc/krb5kdc/service.keyfile
189 + }
190 +
191 +
192 +=== Create kadm5.acl ===
193 +
194 +Then you need to create ##/etc/krb5kdc/kadm5.acl and put in it##
195 +
196 +##*/admin@EXAMPLE.COM *##
197 +
198 +
199 +so that administrator principals can run kadmin. Now we are ready to create the domain. And that we do with
200 +
201 +
202 +=== Create the kerberos domain ===
203 +
204 +#
205 +
206 +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
207 +Password for "uid=root,cn=users,dc=trudheim,dc=com":
208 +Initializing database for realm 'TRUDHEIM.COM'
209 +You will be prompted for the database Master Password.
210 +It is important that you NOT FORGET this password.
211 +Enter KDC database master key:
212 +Re-enter KDC database master key to verify:
213 +
214 +kdb5_ldap_util -D uid=root,cn=users,dc=trudheim,dc=com -H ldaps:~/~/ds723.trudheim.com stashsrvpw -f /etc/krb5kdc/service.keyfile cn=kdc,ou=kerberos,dc=trudheim,dc=com
215 +Password for "uid=root,cn=users,dc=trudheim,dc=com":
216 +Password for "cn=kdc,ou=kerberos,dc=trudheim,dc=com":
217 +Re-enter password for "cn=kdc,ou=kerberos,dc=trudheim,dc=com":
218 +
219 +kdb5_ldap_util -D uid=root,cn=users,dc=trudheim,dc=com -H ldaps:~/~/ds723.trudheim.com stashsrvpw -f /etc/krb5kdc/service.keyfile cn=kadmin,ou=kerberos,dc=trudheim,dc=com
220 +Password for "uid=root,cn=users,dc=trudheim,dc=com":
221 +Password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
222 +Re-enter password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
223 +
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 +