Sorry about the misunderstanding. Please file a ticket with the expected
behaviour.
https://fedorahosted.org/389/newticket
Thanks.
On 01/05/2017 06:34 PM, Gordon Messmer wrote:
On 01/05/2017 04:00 PM, William Brown wrote:
http://www.port389.org/docs/389ds/design/shadow-account-support.html
On 01/05/2017 04:00 PM, William Brown wrote:
http://www.port389.org/docs/389ds/design/shadow-account-support.html
I feel like I must be missing something, because this makes *no* sense
at all. When a search is performed, shadowExpire will reflect the
current time plus the maximum password ag
On Thu, 2017-01-05 at 15:35 -0800, Gordon Messmer wrote:
> On 01/05/2017 03:15 PM, William Brown wrote:
> > The shadowexpire value now is handled differently on 1.3.5 if I recall.
>
>
> I'm unable to find documentation of this change in the release notes.
> Am I overlooking something?
>
> http
On 01/05/2017 03:15 PM, William Brown wrote:
The shadowexpire value now is handled differently on 1.3.5 if I recall.
I'm unable to find documentation of this change in the release notes.
Am I overlooking something?
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/ht
On Thu, 2017-01-05 at 15:09 -0800, Gordon Messmer wrote:
> After upgrading to CentOS 7.3, I found that shadowExpire attributes were
> not returned correctly. Searching for an account shows:
>
> dn: UID=gmessmer,ou=People,dc=...
> uid: gmessmer
> shadowexpire: 117170
>
> The same value is shown
After upgrading to CentOS 7.3, I found that shadowExpire attributes were
not returned correctly. Searching for an account shows:
dn: UID=gmessmer,ou=People,dc=...
uid: gmessmer
shadowexpire: 117170
The same value is shown in the 389-ds console. The correct value,
however, appears in our dail
