#1837 [RFE] Use extended data blob to extract error msg on AD krb password changes
Closed: wontfix 4 years ago by pbrezina. Opened 11 years ago by simo.

When changing password AD returns an extended error message with the reason why a password change failed.
This data is a NDR encoded structure that includes a Windows NT Status error code.
The eData blob can be retrieved with krb5_init_creds_get_error(), then samba's ndr libraries should be used to decode the blob.


Fields changed

summary: Use extended data blob to extract error msg on AD krb password changes => [RFE] Use extended data blob to extract error msg on AD krb password changes
type: defect => enhancement

Fields changed

mark: => 0

Nice to have, not strictly required for 1.13

changelog: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => critical
review: => 0

Re-setting priority of 1.13 backlog tickets used for planning.

priority: critical => major

At the moment we don't plan on implementing this in the next upstream release. Patches are welcome.

milestone: SSSD 1.13 backlog => SSSD 1.15 beta
sensitive: => 0

Metadata Update from @simo:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

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

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.

Login to comment on this ticket.

Metadata