Fields changed

description: Support the pwdLastSet Active Directory server LDAP attribute value 0 to
force a password change.

Related information:
http://msdn.microsoft.com/en-us/library/cc220785(v=prot.10).aspx
https://fedorahosted.org/pipermail/sssd-devel/2011-April/005960.html => Support the pwdLastSet Active Directory server LDAP attribute value 0 to
force a password change.

Related information:
* http://msdn.microsoft.com/en-us/library/cc220785(v=prot.10).aspx
* https://fedorahosted.org/pipermail/sssd-devel/2011-April/005960.html

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.7.0
owner: somebody => jzeleny
priority: blocker => major

Based on the referenced email conversation, I think the right approach here is to implement the entire AD password policy.

I already started to do some work on that, but it proved to be more complex than I originally anticipated. Therefore I'm moving this ticket to NEEDS_TRIAGE and propose that we do it in 1.8 instead of 1.7.

milestone: SSSD 1.7.0 => NEEDS_TRIAGE
rhbz: =>
status: new => assigned

This can't be fixed.

milestone: NEEDS_TRIAGE => SSSD 1.6.1
resolution: => wontfix
status: assigned => closed

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1961

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.