[389-users] Re: Replication manager with expired password

2020-02-27 Thread Marc Sauton
The internal suffix cn=config is not really designed to have a global password policy applied to it. A replication manager usually does not have a password policy. If it is required to have some special DNs with a password policy, they should be in a different suffix. Thanks, M. On Thu, Feb 27,

[389-users] Re: Replication manager with expired password

2020-02-27 Thread William Brown
> On 27 Feb 2020, at 00:04, Eugen Lamers wrote: > > Hi, > we have set up a multi master replication (two peers, SIMPLE authentication) > and added a global password policy to cn=config. We included the > passwordMustChange attribute to cn=config, which led to the fact that the > server

[389-users] Re: 389ds and dual stack IPV4/6, also...

2020-02-27 Thread William Brown
> On 28 Feb 2020, at 01:54, N R wrote: > > I've been able to find what was wrong in my configuration, I had a > typo in the /etc/hosts file. > ^_^' Can I ask what the typo was? I'm curious how that caused this to listen on v6 only? What was the setting of your securelisthost value in

[389-users] Re: 389ds and dual stack IPV4/6, also...

2020-02-27 Thread Mark Reynolds
On 2/27/20 10:54 AM, N R wrote: I've been able to find what was wrong in my configuration, I had a typo in the /etc/hosts file. ^_^' Thank you a lot for your time and your precious advices. Glad you figured it out! Best regards, Nick Rand 2020-02-27 16:25 UTC+01:00, Mark Reynolds : On

[389-users] Re: 389ds and dual stack IPV4/6, also...

2020-02-27 Thread N R
I've been able to find what was wrong in my configuration, I had a typo in the /etc/hosts file. ^_^' Thank you a lot for your time and your precious advices. Best regards, Nick Rand 2020-02-27 16:25 UTC+01:00, Mark Reynolds : > > On 2/27/20 10:13 AM, N R wrote: >> Hi Mark, >> >> Thanks for your

[389-users] Re: 389ds and dual stack IPV4/6, also...

2020-02-27 Thread Mark Reynolds
On 2/27/20 10:13 AM, N R wrote: Hi Mark, Thanks for your replies. How did you configure the instance exactly? The host is a Fedora 30 VM, I installed 389ds using the package manager (dnf) and the setup-ds-admin.pl script. I enabled LDAPS over TLS on the standard port (636). The VM has a

[389-users] Re: 389ds and dual stack IPV4/6, also...

2020-02-27 Thread N R
Hi Mark, Thanks for your replies. > How did you configure the instance exactly? The host is a Fedora 30 VM, I installed 389ds using the package manager (dnf) and the setup-ds-admin.pl script. I enabled LDAPS over TLS on the standard port (636). The VM has a single network interface with both

[389-users] Re: 389ds and dual stack IPV4/6, also...

2020-02-27 Thread Mark Reynolds
On 2/27/20 8:03 AM, Mark Reynolds wrote: On 2/27/20 5:30 AM, N R wrote: Hello all, It's my first message on this list thanks in advance for your answers. I've configured a 389ds instance with ipv6 address and it's working great with it. How did you configure the instance exactly? What do

[389-users] Re: 389ds and dual stack IPV4/6

2020-02-27 Thread Mark Reynolds
On 2/27/20 5:30 AM, N R wrote: Hello all, It's my first message on this list thanks in advance for your answers. I've configured a 389ds instance with ipv6 address and it's working great with it. I need for this instance to be reachable via ipv4 also but despite hours of research on the web

[389-users] 389ds and dual stack IPV4/6

2020-02-27 Thread N R
Hello all, It's my first message on this list thanks in advance for your answers. I've configured a 389ds instance with ipv6 address and it's working great with it. I need for this instance to be reachable via ipv4 also but despite hours of research on the web and the archive of the list, I