On 06/26/2017 10:16 AM, Mitch Patenaude wrote:
I'm trying to migrate my organization of FDS, but policy requires a 90
day password expiration, and pam_ldap modules aren't forcing password
changes even after the password expired.
As far as I know, pam_ldap doesn't use passwordExpirationTime
On Mon, 2017-06-26 at 17:16 +, Mitch Patenaude wrote:
> I'm trying to migrate my organization of FDS, but policy requires a 90 day
> password expiration, and pam_ldap modules aren't forcing password changes
> even after the password expired.
>
> I saw in a thread back from 2011 that somebody
On Mon, 2017-06-26 at 09:30 -0700, ghiureai wrote:
> Hi List,
> I have an existing multimaster replication 389-DS , 2 hosts running :
> OS :el6.x86_64 #1 SMP
> with
> 389-ds-base-1.3.4.4-000.x86_64
>
> I need to bring the 3 host and cfg multimaster rep/ or any other rep
> if will work,
> the
I'm trying to migrate my organization of FDS, but policy requires a 90 day
password expiration, and pam_ldap modules aren't forcing password changes even
after the password expired.
I saw in a thread back from 2011 that somebody was having an issue where
setting passwordExpirationTime to 197001
Hi List,
I have an existing multimaster replication 389-DS , 2 hosts running :
OS :el6.x86_64 #1 SMP
with
389-ds-base-1.3.4.4-000.x86_64
I need to bring the 3 host and cfg multimaster rep/ or any other rep
if will work,
the new host will run:
OS: fc24.x86_64 #1
with
389-ds-base-libs-1.3.5
Mark, thank you for reply.
Is low values of this attributes affect server performance? What ldap
attributes is corresponding to these db's?
From: Mark Reynolds [mailto:marey...@redhat.com]
Sent: Friday, June 23, 2017 8:15 PM
To: General discussion list for the 389 Directory server project.
<389-
