Files
authentik/website/docs/troubleshooting/ldap_source.md
rickra 1d5d096ffc website/docs: use default container name from helm chart in recovery documentation for kubernetes (#10919)
* use default container name from helm chart

the default name for the worker container is worker and not authentik.
see https://github.com/goauthentik/helm/blob/main/charts/authentik/values.yaml#L603

Signed-off-by: rickra <richardkraus98@pm.me>

* fix container name everywhere

Signed-off-by: Jens Langhammer <jens@goauthentik.io>

---------

Signed-off-by: rickra <richardkraus98@pm.me>
Signed-off-by: Jens Langhammer <jens@goauthentik.io>
Co-authored-by: Jens Langhammer <jens@goauthentik.io>
2024-08-15 14:56:52 +02:00

786 B

title
title
Troubleshooting LDAP Synchronization

To troubleshoot LDAP sources, you can run the command below to run a synchronization in the foreground and see any errors or warnings that might happen directly

docker compose run --rm worker ldap_sync *slug of the source*

or, for Kubernetes, run

kubectl exec -it deployment/authentik-worker -c worker -- ak ldap_sync *slug of the source*

Starting with authentik 2023.10, you can also run command below to explicitly check the connectivity to the configured LDAP Servers:

docker compose run --rm worker ldap_check_connection *slug of the source*

or, for Kubernetes, run

kubectl exec -it deployment/authentik-worker -c worker -- ak ldap_check_connection *slug of the source*