 1d5d096ffc
			
		
	
	1d5d096ffc
	
	
	
		
			
			* 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>
		
			
				
	
	
		
			28 lines
		
	
	
		
			786 B
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			28 lines
		
	
	
		
			786 B
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| ---
 | |
| 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
 | |
| 
 | |
| ```shell
 | |
| docker compose run --rm worker ldap_sync *slug of the source*
 | |
| ```
 | |
| 
 | |
| or, for Kubernetes, run
 | |
| 
 | |
| ```shell
 | |
| 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:
 | |
| 
 | |
| ```shell
 | |
| docker compose run --rm worker ldap_check_connection *slug of the source*
 | |
| ```
 | |
| 
 | |
| or, for Kubernetes, run
 | |
| 
 | |
| ```shell
 | |
| kubectl exec -it deployment/authentik-worker -c worker -- ak ldap_check_connection *slug of the source*
 | |
| ```
 |