0 Votes

Changes for page KerberosAndLDAP

Last modified by Sirius Rayner-Karlsson on 2024/05/09 10:54

From 34.1 to 35.1

From version 35.1

edited by Sirius Rayner-Karlsson
on 2024/05/09 09:59

Change comment: There is no comment for this version

To version 37.1

edited by Sirius Rayner-Karlsson
on 2024/05/09 10:54

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -27,12 +27,7 @@
  Now you need to load the kerberos schema into the LDAP server on the Synology. Use the ##cn=config## DN.
  (% style="color:#400" %)
--##{{{
--$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldaps://nas.example.com/ -D cn=config -W
--Enter LDAP Password:
--adding new entry "cn=kerberos,cn=schema,cn=config"
--$
--}}}##
++##{{{$ zcat /usr/share/doc/krb5-kdc-ldap/kerberos.openldap.ldif.gz | ldapadd -H ldaps://nas.example.com/ -D cn=config -W Enter LDAP Password: adding new entry "cn=kerberos,cn=schema,cn=config" $}}}##
  === Create Index on krbPrincipalName ===
@@ -43,20 +43,20 @@
  ##{{{
  dn: olcDatabase={1}bdb,cn=config
  add: olcDbIndex
--olcDbIndex: krbPrincipalName eq,pres,sub
--}}}##
++olcDbIndex: krbPrincipalName eq,pres,sub}}}##
++
  and apply it with
  (% style="color:#400" %)
--##{{{
--$ ldapmodify -H ldaps://nas.example.com/ -D cn=config -W -f step1.ldif
++##{{{$ ldapmodify -H ldaps://nas.example.com/ -D cn=config -W -f step1.ldif
  Enter LDAP Password:
++
  modifying entry "olcDatabase={1}bdb,cn=config"
--$
--}}}##
++$ }}}##
++
  === Create principals kadmin and kdc ===
  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.
@@ -91,14 +91,13 @@
  pwdCheckQuality: 2
  pwdPolicySubentry: cn=kadmin,ou=kerberos,dc=example,dc=com
  userPassword: {SSHA}<password-hash>
--description: Kerberos KDC Account
--}}}##
++description: Kerberos KDC Account}}}##
++
  Apply it with
  (% style="color:#400" %)
--##{{{
--$ ldapadd -H ldaps://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W -f step2.ldif
++##{{{$ ldapadd -H ldaps://nas.example.com/ -D uid=root,cn=users,dc=example,dc=com -W -f step2.ldif
  Enter LDAP Password:
  adding new entry "ou=kerberos,dc=example,dc=com"
@@ -106,85 +106,100 @@
  adding new entry "cn=kdc,ou=kerberos,dc=example,dc=com"
  adding new entry "cn=kadmin,ou=kerberos,dc=example,dc=com"
--}}}##
++$ }}}##
++A small note on this section:
++The ##objectClass: pwdPolicy## must be added to a, to LDAP, physical thing. ##objectClass: person## fits the criteria, but can not have ##uid##. So to make it work, the ##uid## is replaced with ##sn## and ##cn## (yes, both are needed). Then you can set the other four attributes and add the hashed password you got from ##slappasswd##.
++
++
  === Grant kdc and kadmin permissions ===
--This switches back to the ##cn=config## DN as you are changing the permissions.
++This switches back to the ##cn=config## DN as you are changing the permissions. 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  too many login failures. We like security.
--$ ldapmodify -H ldaps:~/~/ds723.trudheim.com -W -D cn=config <<EOF
++Create ##step3.ldif## with the following content:
++(% style="color:#400" %)
++##{{{
  dn: olcDatabase={1}bdb,cn=config
  add: olcAccess
  olcAccess: {0}to attrs=krbPrincipalKey
    by anonymous auth
--  by dn.exact="cn=kdc,ou=kerberos,dc=trudheim,dc=com" write
--  by dn.exact="cn=kadmin,ou=kerberos,dc=trudheim,dc=com" write
++  by dn.exact="cn=kdc,ou=kerberos,dc=example,dc=com" write
++  by dn.exact="cn=kadmin,ou=kerberos,dc=example,dc=com" write
    by self write
    by * none
  -
  add: olcAccess
  olcAccess: {1}to dn.subtree="cn=krbContainer,ou=kerberos,dc=example,dc=com"
--  by dn.exact="cn=kdc,ou=kerberos,dc=trudheim,dc=com" write
--  by dn.exact="cn=kadmin,ou=kerberos,dc=trudheim,dc=com" write
++  by dn.exact="cn=kdc,ou=kerberos,dc=example,dc=com" write
++  by dn.exact="cn=kadmin,ou=kerberos,dc=example,dc=com" write
    by * none
++}}}##
--EOF
--Enter LDAP Password:
--modifying entry "olcDatabase={1}bdb,cn=config"
++**Do not get the domain part above wrong. If you do, you may not be able to use ##kadmin## or ##kinit## and fixing the permissions without breaking something else is a nervous task. Trust me on this (as I screwed them up).**
--$
++Apply it with
++(% style="color:#400" %)
++##{{{
++$ ldapmodify -H ldaps://nas.example.com -W -D cn=config -f step3.ldif
++Enter LDAP Password:
--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.
++modifying entry "olcDatabase={1}bdb,cn=config"
++$ }}}##
++
  === Create krb5.conf ===
--Over to adjusting /etc/krb5.conf so that it will point to the right thing later. It should look something like this:
++Next we create (or modify)  ##/etc/krb5.conf## so that it will point to the right thing later. It should look something like this:
++(% style="color:#400" %)
++##{{{
++[libdefaults]
++    default_realm = EXAMPLE.COM
++    dns_lookup_realm = false
++    dns_lookup_kdc = false
++    ticket_lifetime = 24h
++    forwardable = true
++    proxiable = true
++    rdns = false
--{{{[libdefaults]
--        default_realm = EXAMPLE.COM
--        dns_lookup_realm = false
--        dns_lookup_kdc = false
--        ticket_lifetime = 24h
--        forwardable = true
--        proxiable = true
--        rdns = false
--
  [realms]
--        EXAMPLE.COM = {
--                kdc = debian.example.com
--                admin_server = debian.example.com
--                default_domain = example.com
--        }
-- [domain_realm]
--  .example.com = EXAMPLE.COM
--  example.com = EXAMPLE.COM}}}
++    EXAMPLE.COM = {
++        kdc = debian.example.com
++        admin_server = debian.example.com
++        default_domain = example.com
++    }
++[domain_realm]
++    .example.com = EXAMPLE.COM
++    example.com = EXAMPLE.COM
++}}}##
--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.
++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.
++
  === Create kdc.conf ===
--Next, we need to write up /etc/krb5kdc/kdc.conf. Something like this should work
++Now we do /etc/krb5kdc/kdc.conf. Something like this should work
--
++(% style="color:#400" %)
++##{{{
  [libdefaults]
  [realms]
--    TRUDHEIM.COM = {
--    database_module = openldap_ldapconf
--    max_life = 7d
--    max_renewable_life = 6d
++    EXAMPLE.COM = {
++        database_module = openldap_ldapconf
++        max_life = 7d
++        max_renewable_life = 6d
      }
  [dbdefaults]
--    ldap_kerberos_container_dn = cn=krbContainer,ou=kerberos,dc=trudheim,dc=com
++    ldap_kerberos_container_dn = cn=krbContainer,ou=kerberos,dc=example,dc=com
  [dbmodules]
      openldap_ldapconf = {
@@ -192,78 +192,110 @@
          disable_last_success = false
          disable_lockout = false
          ldap_conns_per_server = 5
--        ldap_servers = ldaps:~/~/ds723.trudheim.com
--        ldap_kdc_dn = "cn=kdc,ou=kerberos,dc=trudheim,dc=com"
--        ldap_kadmind_dn = "cn=kadmin,ou=kerberos,dc=trudheim,dc=com"
++        ldap_servers = ldaps:~/~/nas.example.com
++        ldap_kdc_dn = "cn=kdc,ou=kerberos,dc=example,dc=com"
++        ldap_kadmind_dn = "cn=kadmin,ou=kerberos,dc=example,dc=com"
          ldap_service_password_file = /etc/krb5kdc/service.keyfile
      }
++}}}##
  === Create kadm5.acl ===
--Then you need to create ##/etc/krb5kdc/kadm5.acl and put in it##
++Create ##/etc/krb5kdc/kadm5.acl with the following content so that kerberos administrator principals can run ##kadmin##
--##*/admin@EXAMPLE.COM *##
++(% style="color:#400" %)
++##{{{
++*/admin@EXAMPLE.COM *
++}}}##
--so that administrator principals can run kadmin. Now we are ready to create the domain. And that we do with
--
--
  === Create the kerberos domain ===
--#
++Now we are ready to create the domain. And that we do with ##kdb5_ldap_util## as ##root##. Note that this commandline is deceptive and you need all of it.
--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
++(% style="color:#400" %)
++##{{{
++# kdb5_ldap_util -D uid=root,cn=users,dc=example,dc=com -H ldaps://nas.example.com -r EXAMPLE.COM create -subtrees dc=example,dc=com -maxtktlife '7 Days' -maxrenewlife '6 Days' -s
  Password for "uid=root,cn=users,dc=trudheim,dc=com":
--Initializing database for realm 'TRUDHEIM.COM'
++Initializing database for realm 'EXAMPLE.COM'
  You will be prompted for the database Master Password.
  It is important that you NOT FORGET this password.
  Enter KDC database master key:
  Re-enter KDC database master key to verify:
++# }}}##
--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
--Password for "uid=root,cn=users,dc=trudheim,dc=com":
--Password for "cn=kdc,ou=kerberos,dc=trudheim,dc=com":
--Re-enter password for "cn=kdc,ou=kerberos,dc=trudheim,dc=com":
--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
--Password for "uid=root,cn=users,dc=trudheim,dc=com":
--Password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
--Re-enter password for "cn=kadmin,ou=kerberos,dc=trudheim,dc=com":
++=== Stash the passwords for ##kdc## and ##kadmin## ===
++Most likely, you will want your KDC and KAdmin server to start at boot, and for that, we can stash the passwords (into LDAP) for ##cn=kdc,ou=kerberos,dc=example,dc=com## and ##cn=kdc,ou=kerberos,dc=example,dc=com## using the same tool as in the previous step.
++(% style="color:#400" %)
++##{{{
++# kdb5_ldap_util -D uid=root,cn=users,dc=example,dc=com -H ldaps://nas.example.com stashsrvpw -f /etc/krb5kdc/service.keyfile cn=kdc,ou=kerberos,dc=example,dc=com
++Password for "uid=root,cn=users,dc=example,dc=com":
++Password for "cn=kdc,ou=kerberos,dc=example,dc=com":
++Re-enter password for "cn=kdc,ou=kerberos,dc=example,dc=com":
++# kdb5_ldap_util -D uid=root,cn=users,dc=example,dc=com -H ldaps://nas.example.com stashsrvpw -f /etc/krb5kdc/service.keyfile cn=kadmin,ou=kerberos,dc=example,dc=com
++Password for "uid=root,cn=users,dc=example,dc=com":
++Password for "cn=kadmin,ou=kerberos,dc=example,dc=com":
++Re-enter password for "cn=kadmin,ou=kerberos,dc=example,dc=com":
++# }}}##
++
++
++=== Start the services ===
++
++We are now ready to start the services. If this does not work, you need to backtrack and find out where you made a mistake, rectify it, and then walk forward again.
++
++(% style="color:#400" %)
++##{{{
++# systemctl enable --now krb5-kdc krb5-admin-server
++#
++}}}##
++
++
++Check that they are running and not giving off errors with ##systemctl status krb5-kdc## and ##systemctl status krb5-admin-server##.
++
++
  === Create the first regular principals ===
--Here, you will run kadmin.local to create first a regular user, and then an admin version of that user.
++Providing you got to here without issues it is now time to generate your principals that you will use to authenticate into systems with. Run ##kadmin.local## as root to create first a regular user, and then an admin version of that user.
++(% style="color:#400" %)
++##{{{
  # kadmin.local
--Authenticating as principal root/admin@TRUDHEIM.COM with password.
++Authenticating as principal root/admin@EXAMPLE.COM with password.
  kadmin.local:  addprinc user
--No policy specified for user@TRUDHEIM.COM; defaulting to no policy
--Enter password for principal "user@TRUDHEIM.COM":
--Re-enter password for principal "user@TRUDHEIM.COM":
--Principal "user@TRUDHEIM.COM" created.
++No policy specified for user@EXAMPLE.COM; defaulting to no policy
++Enter password for principal "user@EXAMPLE.COM":
++Re-enter password for principal "user@EXAMPLE.COM":
++Principal "user@EXAMPLE.COM" created.
  kadmin.local:  addprinc user/admin
--No policy specified for user/admin@TRUDHEIM.COM; defaulting to no policy
--Enter password for principal "user/admin@TRUDHEIM.COM":
--Re-enter password for principal "user/admin@TRUDHEIM.COM":
--Principal "user/admin@TRUDHEIM.COM" created.
++No policy specified for user/admin@EXAMPLE.COM; defaulting to no policy
++Enter password for principal "user/admin@EXAMPLE.COM":
++Re-enter password for principal "user/admin@EXAMPLE.COM":
++Principal "user/admin@EXAMPLE.COM" created.
  kadmin.local:  q
--#
++# }}}##
--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.
--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.
++Worth to note here is that ##user@EXAMPLE.COM## and ##user/admin@EXAMPLE.COM## can have (and probably should have) different passwords. The admin variant is allowed to do things to the kerberos database and should therefore have greater security. 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.
++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 a share, they see nothing on it without the krbtgt.
++
  === Test your new principal ===
--$ kinit [[user@EXAMPLE.COM>>mailto:user@EXAMPLE.COM]]
++Acid test is, can you authenticate with kinit?
++(% style="color:#400" %)
++##{{{
++$ kinit user@EXAMPLE.COM
++
  Password for user@EXAMPLE.COM:
  $ klist
@@ -273,9 +273,29 @@
  Valid starting     Expires            Service principal
 /05/24 08:07:35  10/05/24 08:07:35  krbtgt/EXAMPLE.COM@EXAMPLE.COM
--$
++$ }}}##
++Congratulations - you now have Kerberos working, and to boot, the database sits in LDAP. Which you can inspect with something like:
++
++(% style="color:#400" %)
++##{{{
++$ ldapsearch -H ldaps://nas.example.com -D uid=root,cn=users,dc=example,dc=com -W -b ou=kerberos,dc=example,dc=com
++}}}##
++
++
  === Set up pam and sssd ===
--
++ To fully leverage your shiny new KDC, you will want to install the Kerberos authentication pieces for ##PAM## and also ##sssd## to facilitate caching of authentication, in case your KDC is offline for some reason when you try to authenticate into another system.
++
++(% style="color:#400" %)
++##{{{
++$ sudo apt install krb5-user libpam-krb5 sssd-krb5
++...
++$ sudo pam-auth-update
++}}}##
++
++
++With ##pam-auth-update## you want to enable Kerberos and SSS authentication (and flip on the auto-creation of home directories while you are there). If you now want to test login on another system with kerberos, you need ##/etc/krb5.conf## and the ##krb5-user##, ##libpam-krb5## and ##sssd-krb5## packages installed on this new system and you need to run ##pam-auth-update## to enable Kerberos and SSS. After that, the system does not need local ##user## (in /etc/passwd) - the kerberos ##user## will work instead.
++
++/S

Changes for page KerberosAndLDAP

Summary

Details

Quick Links

Recent Blog Posts