Thanks for the confirmation regarding secure connections and the clarification
regarding dsgw. I will focus on other alternatives. I would be interested in
exploring cli tools and the API. Any resources to which you could point me
would be appreciated. Thanks for the help.
-Original
On Wed, 2018-03-07 at 23:50 +, tda...@email.arizona.edu wrote:
> > On Wed, 2018-03-07 at 08:52 +0100, Alberto García Sola wrote:
> >
> > Hi there,
> >
> > I'm currently working on docker support in 389-ds.
>
> William, I'm really glad to hear this. We've been running 389 server
> in docker
> On Wed, 2018-03-07 at 08:52 +0100, Alberto García Sola wrote:
>
> Hi there,
>
> I'm currently working on docker support in 389-ds.
William, I'm really glad to hear this. We've been running 389 server in docker
in EC2 instances for months now and it works great. We have home grown scripts
On Wed, 2018-03-07 at 01:18 +, Eric Wheeler wrote:
> How does one properly configure the Directory Server Gateway to run
> over https? Is such a setup necessary for secure connections if ldaps
> over 636 is active?
Yes, because you have:
client -> https -> ldaps
So you have to protect each
On Wed, 2018-03-07 at 08:52 +0100, Alberto García Sola wrote:
> Reading the documentation I find little or none information regarding
> containers and Docker, but I've found a few comments in the changelog
> regarding Docker. I plan to use them in a highly scalable and elastic
> environment.
> I
Hello,
Looking for some guidance with password policies.
About a year ago I migrated a very old instance of Red Hat Directory server to
389-ds version 1.3.5.10. I did this with a db export and import. I did not
enable the password policy which was active on the old Red Hat Directory
instance.
