Adding LDAP Configuration on SSP shows the service down on SSP UI.

Products

• VMware vDefend Firewall with Advanced Threat Prevention

Issue/Introduction

•  After configuring LDAP settings on SSP, authelia pod goes in CrashLoopBackOff state.
• User can not login to SSP UI with local user. it shows service down.
• You will see similar error for authelia-ldap container, when describing authelia pod.
  
  Login to SSP installer as root and run below commands.

k get pods -n nsxi-platform | grep authelia

k describe pod <authelia-pod name from previous command> -n nsxi-platform

-----Output Truncated-----
Containers:
  authelia-ldap:
    Container ID:  cri-o://e425f159c88f912eecf2411378091ce506a2cbfe573117663437c5735c2e9e30
    Image:         sspi.example.com/clustering/authelia@sha256:7e1cb866f1af51c234ca5f113303e8274099b8dbeb5a5cbd7b28ae21928b1fe8
    Image ID:      sspi.example.com/clustering/authelia@sha256:7e1cb866f1af51c234ca5f113303e8274099b8dbeb5a5cbd7b28ae21928b1fe8
    Port:          9092/TCP
    Host Port:     0/TCP
    Command:
      ldap-entrypoint.sh
    State:          Running
      Started:      Thu, 31 Jul 2025 20:54:14 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Thu, 31 Jul 2025 20:53:07 +0000
      Finished:     Thu, 31 Jul 2025 20:54:14 +0000
    Ready:          False
    Restart Count:  25

And pod will show similar error in the events in the same output.

Warning  Unhealthy  13m (x1726 over 17h)  kubelet  (combined from similar events): Startup probe failed: 2025-07-31T20:53:09.812Z  ERROR  ldap/main.go:8  execution failure  {"error": "failed to query health API: Get \"https://127.0.0.1:9092/api/health\": dial tcp 127.0.0.1:9092: connect: connection refused"}

Environment

SSP 5.0.0

Cause

• This can happen when the search DN operation takes longer time due to high number of LDAP users.
• As a side effect authelia-ldap container startup is also slow.

Resolution

• Contact Broadcom Support for Resolution.

Additional Information

• This issue will be fixed in the next release of SSP.