Learn more about these different git repos.
Other Git URLs
Currently the authentication, access and change password targets are using pam status codes like PAM_SUCCESS and PAM_SYSTEM_ERR to indicate the result of an operation. This code is sent to the client by the PAM responder.
Using these codes is becoming complicated, because there are conditions which needs to handled internally, e.g. when an provider is offline, where there is no good matching PAM status code.
It would be very helpful to introduce a set of SSSD specific internal status codes and let the PAM responder choose the right PAM status code just before sending the response to the client.
milestone: NEEDS_TRIAGE => SSSD 1.3
owner: somebody => sgallagh
milestone: SSSD 1.5.0 => SSSD 1.6.0
milestone: SSSD 1.6.0 => SSSD 1.7.0
upgrade: => 0
This is out of scope of the 1.8 release.
milestone: SSSD 1.8.0 => SSSD 1.9.0
patch: => 0
milestone: SSSD 1.9.0 => SSSD Deferred
rhbz: => 0
design_review: => 0
milestone: SSSD Deferred => NEEDS_TRIAGE
When solving this ticket, we should also take care of the static inline in util/auth_utils.h. It's ugly and only a workaround until this ticket is fixed.
Moving to 1.10 and bumping it up.
milestone: NEEDS_TRIAGE => SSSD 1.10 beta
priority: minor => blocker
summary: Replace pam status codes with sssd specific codes => [RFE] Replace pam status codes with sssd specific codes
owner: sgallagh => simo
status: new => assigned
selected: => May
priority: blocker => critical
priority: critical => major
The patches are on the list already.
patch: 0 => 1
The last patch that would convert the simple access provider is on the list.
review: => 0
The simple access provider was converted in commit 18f01e6
resolution: => fixed
status: assigned => closed
summary: [RFE] Replace pam status codes with sssd specific codes => Replace pam status codes with sssd specific codes
type: enhancement => task
Metadata Update from @sbose:
- Issue assigned to simo
- Issue set to the milestone: SSSD 1.10 beta
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:
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.
to comment on this ticket.