not been active, it probably makes sense to set applicable user’s
passwordexpirationtime attribute to sometime in the future so there isn’t a
flood of “password lockout” complaints?
[cid:EL-logo_7ba48a57-966c-4a07-b478-7857c99d9581.png] Kirk MacDonald | System
Analyst II
Eastlink | Internet
ssword policy is only for when the passwords need to be
changed/expired, as opposed to syntax/strength.
Is there a way around this without changing our app/tool to send the plain
password over SSL/TLS/STARTTLS?
Thanks
Kirk MacDonald
Eastlink
___
389-u
.
==
Do you want to register a remote server with the local configuration server
(y/n)? y
- Kirk
From: Mark Reynolds [mailto:marey...@redhat.com]
Sent: Thursday, August 24, 2017 4:04 PM
To: Kirk MacDonald <kirk.mac
OK scratch that – it of course does work interactively. I was just being thrown
off by the fact one has to (re)config/specify the local Admin instance each
time. Later on in the interactive it asks for the remote hosts. Silly me.
-Kirk
From: Kirk MacDonald [mailto:kirk.macdon
Thanks for the reply. I am struggling with the script because it only seems to
see local instances, when running the script interactively.
- Kirk
From: Mark Reynolds
Sent: Thursday, August 24, 2017 1:30 PM
To: General discussion list for the 389 Directory server project.; Kirk
MacDonald
://www.port389.org/docs/389ds/design/console-remote-reg-design.html ?
Or, is there a more “simplistic” approach that can be done via each Admin
console UI?
Thanks,
Kirk MacDonald
Eastlink
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe
.
Based on some experience I have with another LDAP system this feels like an
ancestorid problem.
Can anyone offer any tips/thoughts or questions to clarify my problem?
Thank you
Kirk MacDonald
___
389-users mailing list -- 389-users@lists.fedoraproject.org
