0 Votes

Wiki source code of KerberosAndLDAP

Version 14.1 by Sirius Rayner-Karlsson on 2024/05/01 17:15

Show last authors
1 = Debian =
2
3 The guide I followed was [[https:~~/~~/wiki.debian.org/LDAP/OpenLDAPSetup#Kerberos>>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.
4
5
6 First, install the packages containing the LDAP-enabled Kerberos servers ([[krb5-kdc-ldap>>url:https://packages.debian.org/krb5-kdc-ldap]] and [[krb5-admin-server>>url:https://packages.debian.org/krb5-admin-server]]) and the [[schema2ldif>>url:https://packages.debian.org/schema2ldif]] tool:
7
8 ##{{{$ sudo apt install krb5-kdc-ldap krb5-admin-server schema2ldif}}}##
9
10
11 Then load the ##kerberos## schema:
12
13 ##{{{$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldap:~/~/nas.fqdn/ -D uid=root,cn=users,dc=example,dc=com}}}##
14
15 ##{{{Password:}}}##
16
17 ##{{{adding new entry "cn=kerberos,cn=schema,cn=config"}}}##
18
19 ##{{{$}}}##
20
21
22 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:
23
24 ##{{{$ sudo ldapmodify -H ldap://nas.fqhn <<EOF
25 dn: olcDatabase={1}bdb,cn=config
26 add: olcDbIndex
27 olcDbIndex: krbPrincipalName eq,pres,sub
28 EOF
29 Password:
30
31 modifying entry "olcDatabase={1}bdb,cn=config"
32 $
33 }}}##
34
35
36
37 Next, you need to create and configure two entries which will be used by the Kerberos servers to connect to OpenLDAP. If you are running Kerberos and OpenLDAP on the same system, these steps are optional, but recommended. In order to keep things nicely separated, everything will be created under a separate ##organizationalUnit##. Note that a simple bind (##-x -D##) is used instead of an ##EXTERNAL## bind since write access to the dc=example,dc=com DIT is necessary:
38
39
40 {{{# ldapadd -x -D cn=admin,dc=example,dc=com -W <<EOF
41 dn: ou=Services,dc=example,dc=com
42 objectClass: organizationalUnit
43 objectClass: top
44 ou: Services
45
46 dn: ou=kerberos,ou=Services,dc=example,dc=com
47 objectClass: organizationalUnit
48 objectClass: top
49 ou: kerberos
50
51 dn: uid=kdc,ou=kerberos,ou=Services,dc=example,dc=com
52 uid: kdc
53 objectClass: account
54 objectClass: simpleSecurityObject
55 userPassword: {CRYPT}x
56 description: Kerberos KDC Account
57
58 dn: uid=kadmin,ou=kerberos,ou=Services,dc=example,dc=com
59 uid: kadmin
60 objectClass: account
61 objectClass: simpleSecurityObject
62 userPassword: {CRYPT}x
63 description: Kerberos Admin Server Account
64 EOF
65 Enter LDAP Password: SECRET
66
67 adding new entry "ou=Services,dc=example,dc=com"
68
69 adding new entry "ou=kerberos,ou=Services,dc=example,dc=com"
70
71 adding new entry "uid=kdc,ou=kerberos,ou=Services,dc=example,dc=com"
72
73 adding new entry "uid=kadmin,ou=kerberos,ou=Services,dc=example,dc=com"}}}
74
75
76