Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- content:serverbasics:docker-authentik [2025/03/29 19:19] – [Sync of FreeIPA/LDAP] Daniel
+++ content:serverbasics:docker-authentik [2025/04/14 19:26] (aktuell) – [Secure LDAP- Users with TOTP] Daniel
@@ Zeile 1: / Zeile 1: @@
 ====== Docker: Authentik ======
-Authentik is a middleware expanding the basic authentication- features of FreeIPA by many additional, modern ways of authentication which is used by modern Software. It will make SSO possible (Single-Sign-On: only logging into your pc will be enough to open all apps) by using the Kerberos-Credentials to login to authentik and than to authenticate the third-aprty app like Nextcloud without any user or Password.
+Authentik is a middleware expanding the basic authentication- features of FreeIPA by many additional, modern ways of authentication which is used by modern Software. It will make SSO possible (Single-Sign-On: only logging into your pc will be enough to open all apps) by using the Kerberos-Credentials to login to authentik and than to authenticate the third-aprty app like Nextcloud without any additional User or Password- Dialog.
-TODO
 ===== Dockerfile =====
@@ Zeile 63: / Zeile 61: @@
     volumes:
       - authentik_pgsql_data:/var/lib/postgresql/data
+      - authentik_backup:/tmp/backup
 #Defined in .env
 #    environment:
@@ Zeile 147: / Zeile 146: @@
 volumes:
   authentik_pgsql_data:
+  authentik_backup:
   authentik_media:
   authentik_custom_templates:
@@ Zeile 172: / Zeile 172: @@
 </file>
 ===== First start =====
@@ Zeile 179: / Zeile 180: @@
 and set the Password for the admin user ''akadmin''.
-===== Additional Doings =====
+===== Backup PostgresSQL Database =====
+This is really VERY Important! The reason is, that every PostgresDB- Version has it own Database- File- Format and if you update Postgres from on Major Version to the next, you WILL NOT BE ABLE to start your DB with the old Volume- Data!
+You NEED to have the DB-Backed up and restored to the next Version!
+Create a File in your Docker- Dir named e.g. ''docker_backup_authentik_db.sh:''
+<file>
+#!/bin/bash
+# Make Postgres-Backup of Authentik
+echo "Backup of authentik-postgres to servername-authentik_pgsql-1:/tmp/backup"
+/home/docker/bin/docker exec -t -e PGPASSWORD=YOURPASSWORD servername-authentik_pgsql-1 pg_dump --compress=zstd:8 -f /tmp/backup/pg_dump_authentik.sql -U authentik authentik
+echo "Done Backup of Authentik-DB."
+</file>
+Now add this script to  ''backup/docker_backup_all.sh'' .
 Don't forget to extend your ''backup/docker_backup_all.sh'' by adding ''authentik'' to the service- list if you have not done so far.
+If you Update the Major- Version, make sure to create a new Volume for your pgsql- data.
 ===== Configuring =====
@@ Zeile 190: / Zeile 211: @@
 Don't use Kerberos-Sync, because the kadmin-interface of FreeIPA is blocked to not have someone messing around with kerberos without FreeIPA not beeing informed. So use LDAP- Sync for the Users.
-To Sync FreeIPA with Authentik, follow this Guide: https://docs.goauthentik.io/docs/users-sources/sources/directory-sync/freeipa/
+To Sync FreeIPA with Authentik, follow this Guide: [[https://docs.goauthentik.io/docs/users-sources/sources/directory-sync/freeipa/|https://docs.goauthentik.io/docs/users-sources/sources/directory-sync/freeipa/]]
+When the Sync has been configured, all FreeIPA- Users should show up in Authentik.
+After SVC- user is created, use the following commands to modify password reset as written in the doc:
+<file>
+ldapmodify -x -D "cn=Directory Manager" -H ldaps://ipa.domain.tld:636 -W
+dn: cn=ipa_pwd_extop,cn=plugins,cn=config
+changetype: modify
+add: passSyncManagersDNs
+passSyncManagersDNs: uid=svc_authentik,cn=users,cn=accounts,dc=domain,dc=tld
+</file>
+At the next line, hit CTRL+D and the modification should be set, check with:
+<file>
+ldapsearch -xv -Z -W -H ldap://ipa.domain.tld -b "cn=ipa_pwd_extop,cn=plugins,cn=config" -D "cn=Directory Manager"
+</file>
+which should show the entry for ''passsyncmanagersdns'' .
+=== Secure LDAP- Users with TOTP ===
+Now any User can login with its FreeIPA- Password, also if SPNEGO/ kerberos as beneath is not setup yet.
+This is quite insecure, so you shoul add a second factor for that type of Login (for SPNEGO the second factor is your integrated Machine, which has the key stored already).
+To do so, in the Autentik Admin- Panel go to Stages and edit the Stage "default-authentication-mfa-validation"\\
+Change "Not configured action" → Force…\\
+At "Configuration stages" → default.authenticator-totp-setup
+The Next time you are logging in with User and Password in Authentik, it will ask to setup a TOTP- Device. You can for example use [[https://f-droid.org/de/packages/org.liberty.android.freeotpplus/|https://f-droid.org/de/packages/org.liberty.android.freeotpplus/]]
+Hint: There is also an default Flow for this to import in Authentik here [[https://docs.goauthentik.io/docs/add-secure-apps/flows-stages/flow/examples/flows#two-factor-login|https://docs.goauthentik.io/docs/add-secure-apps/flows-stages/flow/examples/flows#two-factor-login]]
+== Current Bug ==
+At the time of writing this, there was a bug here: https://github.com/goauthentik/authentik/issues/5972#issuecomment-2075631779
+So if you have to enter the OTP twice, than go to Flows, click on ''default-authentication-flow'', Tab Stage Bindings and delete the ''default-authentication-mfa-validation'' Stage (not the other MFA!)
 ==== Attaching SPNEGO ====
@@ Zeile 196: / Zeile 259: @@
 With SPNEGO, you gain access to SSO in Authentik.
-Here is the lonk to the Docs: [[https://docs.goauthentik.io/docs/users-sources/sources/protocols/kerberos/|https://docs.goauthentik.io/docs/users-sources/sources/protocols/kerberos/]]
+Here is the link to the Docs: [[https://docs.goauthentik.io/docs/users-sources/sources/protocols/kerberos/|https://docs.goauthentik.io/docs/users-sources/sources/protocols/kerberos/]]
 You need to logon to FreeIPA as Admin and do the following:
   * Go to Hosts, add Host ''authentik.domain.tld''
-  * Go to Services, Add an new HTTP- Service for that Host
+  * Go to Services, Add an new HTTP- Service for that Host, called HTTP/ipa.domain.tld@DOMAIN.TLD
+  * Add the Ipa- User admin to the "Allowed to create Keytab"- Section
-After that, you need to Console into the running FreeIPA-Container and use the commands there:
+After that, you need to the Docker- Console into the running FreeIPA-Container and use the commands there:
 <code>
+#~> docker exec -it servername-ipa-1 bash
 # Logon as Admin
 kinit admin
@@ Zeile 215: / Zeile 280: @@
 </code>
-This is the Keytab that you will use for SPNEGO.
+This is the Keytab (a better "Password") that you will use for SPNEGO in Authentik.
-Use the Servicename ''HTTP/authentik.domain.tld''  as the Servername!
+Use the Servicename ''HTTP@authentik.domain.tld''  as the Servername!
 Important: Use "User matching mode" = "Link to User with identical Username. …“ - otherwise Kerberos may fail!
 Than activate Kerberos in Flows and Stages > Stages > default-authentication-identification > Source settings
+Make sure, that your client is able to login with FreeIPA using SSSD/Kerberos as written in [[.:docker-freeipa#client_setup|docker-freeipa]] - or at least, that krb5 client is installed and is able to login to your IPA- Instance with ''kinit username''  and that you have configured your Browser to work with the certificate. You can also check your Browser on the site ipa.damon.tld after using kinit - it should automatically log you into ipa without a new Password.