an authorization target is needed, too.

owner: simo => sbose

introduced by c0a1d64228042c3d4bbf62447a49d085fd30fda1

resolution: => fixed
status: new => closed

Fields changed

doc: => 0
docupdated: => 0
fixedin: => 0.5.0
tests: => 0
testsupdated: => 0

Fields changed

tests: 0 => 1

I'm not exactly sure how this works. Can you provide use cases and example configuration? Thanks

If you want to allow password changes you have to set 'chpass_provider = ...' (I just realized that there is not entry in the sssd.conf man page for chpass_provider, I'll fix that)

A current use case would be an IPA environment. If you do not need the Kerberos ticket you can authenticate against the LDAP server (auth_provider = ldap). But currently it make sense to use Kerberos to change the password (chapass_provider = krb5), because only here the password policies are enforced. HTH

Thanks Sumit

Fields changed

coverity: =>
milestone: SSSD Deferred => SSSD 0.5.0

Fields changed

rhbz: => 0

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/1110

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.