search

SURFscz / SRAM-deploy

Deploy scripts for the SCZ
Apache License 2.0
4 stars 5 forks source link

ldap traffic is unencrypted between haproxy and container host #523

Open baszoetekouw opened 3 weeks ago

baszoetekouw commented 3 weeks ago

Currently the ldap container exposes a plain text port 389 to the outside. This means that all traffic between the haproxy and ldap container is plain text, which we don't want.

There are two solutions:

  1. (preferrred) loop the ldap traffic also through Traefik; according to @quartje it is also able to handle plain TCP traffic and should be able to do TLS termination. This is the preferred solution, because it allows us to treat all containers and traffic (HTTP and TCP) identical, and we don't have to expose the ldap container port on the Docker host at all.
  2. let slapd handle the TLS termination and expose an ldaps-port on the container host. In that case, make sure we expose a non-standard port (e.g., 1636 instead of 636).
mrvanes commented 3 weeks ago

No, LDAP traffic flow through traefik and traefik connects to 389 on the container host. Let's discuss when I'm back.

mrvanes commented 21 hours ago

SURFConext test docker host needs extra config:

entryPoints:
  ldaps:
    address: ":636"