Password policy behavior when policy settings are edited

ab@novell.com,

> I have duplicated this and it's a bit surprising to me, though I've found
> some bug entries that may explain why. I have asked others who are the
> NMAS authorities what their thoughts are and so far it may have been a
> design change. The password expirations should still apply even though,
> on a login, the Password Expiration Time attribute is not being set.
>

They certainly should, but as far as I can tell they're not.


> With that said I can work around this by checking the 'Verify existing
> passwords comply with password policy' (or whatever it is) checkbox within
> the UP policy. When this is done everything is done as I think it should
> be (in small amounts of testing anyway).

That's definitely worth a try.

> I would guess you get sporadic
> results, perhaps, because you hit different servers with different
> versions of eDirectory and/or NMAS. This is still a bit of speculation
> but it's what I have so far. I'll report back more as I find it,
> including a bug number of that is appropriate.
>

There are only two eDirectory servers in my test environment. They are
in separate trees. I do see that one is still at NW65SP7/eDir8.8SP2,
while the other is NW65SP8/eDir8.8SP4. I'll try patching the SP7 box to
SP8 and see if that changes anything.

Thanks