ldap outpost

[caplam]

Hello,
I'm still learning authentik so i may have a misconfiguration.
Lastly i needed to add an ldap provider. As per the docs i created an ldap provider. It took me some time to understand that authentik would itself deploy a container for the ldap outpost. (i didn't succeded when trying to add a container for the outpost to the stack)
All is working correctly but a question remains.
Authentik deployed the docker container on the default bridge network.
I tried to bind it to the authentik custom bridge network with the parameter : "docker_network: authentik_default", restarted the the stack but the container ak-outpost-ldap remains on default bridge network.
Should i use the network id instead of network name or do i need to do something else ?

[caplam]

If i bring the stack down the ldap outpost container remains active and throw connection errors.
This container seems to communicate with authentik host through websocket; the communication flows through my reverse proxy.
I would have thought this would occur through docker network.
I find it strange that the outpost container is fired up and forgotten.
How does it work when there is an update ?

`

From here the stack is down but outpost container os running and is healthy

warning error=websocket: close 1006 (abnormal closure): unexpected EOF event=event read error logger=authentik.outpost.ak-api-controller loop=event-handler timestamp=2025-09-26T08:10:48Z

the first ip is the container ip; the second is my reverse proxy ip

warning error=write tcp 172.17.0.2:57040->192.168.2.1:443: write: broken pipe event=event write error logger=authentik.outpost.ak-api-controller loop=event-health timestamp=2025-09-26T08:10:49Z

warning error=websocket: close 1006 (abnormal closure): unexpected EOF event=event read error logger=authentik.outpost.ak-api-controller loop=event-handler timestamp=2025-09-26T08:10:53Z

DBG event=connecting to websocket logger=authentik.outpost.ak-api-controller timestamp=2025-09-26T08:10:54Z url=wss://auth.mydomain.tld/ws/outpost/60dda4ab-4e57-40ce-98da-5bf702af5a65/?attempt=7&instance_uuid=instance-id

Here the stack is up and all the containers are healthy

INF event=Successfully connected websocket logger=authentik.outpost.events outpost=60dda4ab-4e57-40ce-98da-5bf702af5a65 timestamp=2025-09-26T08:10:54Z

trace event=hello'd logger=authentik.outpost.ak-api-controller loop=event-health timestamp=2025-09-26T08:10:59Z

trace event=hello'd logger=authentik.outpost.ak-api-controller loop=event-health timestamp=2025-09-26T08:11:09Z

trace event=hello'd logger=authentik.outpost.ak-api-controller loop=event-health timestamp=2025-09-26T08:11:19Z

trace event=hello'd logger=authentik.outpost.ak-api-controller loop=event-health timestamp=2025-09-26T08:11:29Z

trace event=hello'd logger=authentik.outpost.ak-api-controller loop=event-health timestamp=2025-09-26T08:11:39Z

DBG event=Running interval update logger=authentik.outpost.ak-api-controller loop=interval-updater timestamp=2025-09-26T08:11:40Z

DBG event=Fetched outpost configuration logger=authentik.outpost.ak-api-controller name=ldap timestamp=2025-09-26T08:11:41Z

DBG event=re-initialised memory searcher logger=authentik.outpost.ldap.searcher.memory timestamp=2025-09-26T08:11:41Z

INF event=initialised direct binder logger=authentik.outpost.ldap.binder.direct timestamp=2025-09-26T08:11:41Z

INF event=Update providers logger=authentik.outpost.ldap timestamp=2025-09-26T08:11:41Z

trace event=hello'd logger=authentik.outpost.ak-api-controller loop=event-health timestamp=2025-09-26T08:11:49Z

trace event=hello'd logger=authentik.outpost.ak-api-controller loop=event-health timestamp=2025-09-26T08:11:59Z`