f728bbb14b
* sources/ldap: add check command to verify ldap connectivity Signed-off-by: Jens Langhammer <jens@goauthentik.io> * default to checking all sources Signed-off-by: Jens Langhammer <jens@goauthentik.io> * start adding an API for ldap connectivity Signed-off-by: Jens Langhammer <jens@goauthentik.io> * add webui for ldap source connection status Signed-off-by: Jens Langhammer <jens@goauthentik.io> * better show sync status, clear previous tasks Signed-off-by: Jens Langhammer <jens@goauthentik.io> * set timeout on redis lock for ldap sync Signed-off-by: Jens Langhammer <jens@goauthentik.io> * fix py lint Signed-off-by: Jens Langhammer <jens@goauthentik.io> * fix web lint Signed-off-by: Jens Langhammer <jens@goauthentik.io> --------- Signed-off-by: Jens Langhammer <jens@goauthentik.io>
772 B
772 B
| 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 authentik -- 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 authentik -- ak ldap_check_connection *slug of the source*