Re: docker, 389ds/dirsrv:2.0, vendorVersion 2.1.0, ssca, certificate chain, orphan key, cert9.db, key4.db

[Lutz Berger <lutz.berger@xxxxxxxxxxxx>]

    Hi William,
    
    thanks for your help, please find my answers online!
    
    Best regards,
      Lutz

 

On 15.03.22 00:36, William Brown wrote:

> > On 15 Mar 2022, at 02:49, Lutz Berger <lutz.berger@xxxxxxxxxxxx> wrote:
> >
> > Hi there,
> >
> > I've a question regarding the docker image:
> > - vendorVersion: 389-Directory/2.1.0 B2022.015.0000
> >
> > My scenario:
> >
> > - I want to install a customer's certificate chain and run the DS with LDAPS on port 3636
> >
> > My steps to reproduce:
> >
> > - docker volume create 389ds
> > - cd /var/lib/docker/volumes/389ds/_data
> > - cp -r /root/389ds/tls .
> > - verify tls directory:
> >
> > [root@ur1 _data]# ls -lR tls
> > tls:
> > total 8
> > drwxr-xr-x. 2 root root   64 Mar 14 16:56 ca
> > -rw-r--r--. 1 root root 1419 Mar 14 16:56 server.crt
> > -rw-r--r--. 1 root root 1675 Mar 14 16:56 server.key
> >
> > tls/ca:
> > total 8
> > -rw-r--r--. 1 root root 2384 Mar 14 16:56 XXXXXXROOTCA2015.crt
> > -rw-r--r--. 1 root root 2032 Mar 14 16:56 XXXXXXServerCA2015.crt
> > [root@ur1 _data]# 
> >
> >
> > Starting the docker container with "docker-compose up -d" generates
> > a fresh DS, but installs a self-signed CA and cert. 
> >
> > docker-compose.yml
> > ldap:
> >   image: 389ds/dirsrv:2.0
> >   container_name: ur1
> >   volumes:
> >     -  389ds:/data
> >   environment:
> >     - DS_DM_PASSWORD=XXXXX
> >   ports:
> >     - 3389:3389
> >     - 3636:3636
> >   restart: always