Learn more about these different git repos.
Other Git URLs
Create a way to test whether SSSD is properly configured and able to perform authentication and identity lookup for a layered application like Keycloak (or one that uses Apache modules as described here: Web App Authentication).
User story:
As an administrator debugging authentication failure in my layered application I want to determine whether SSSD is working properly performing authentication via PAM and delivering attributes needed for the layered application via infopipe. I would like to have a tool that would mimic my layered application and execute the same interfaces from SSSD that my application is supposed to use in the way it is supposed to use them and report any issues or inconsistencies found.
Fields changed
rhbz: => todo
milestone: NEEDS_TRIAGE => SSSD Future releases (no date set yet)
Metadata Update from @dpal: - Issue set to the milestone: SSSD Future releases (no date set yet)
This would be really helpful utility, will help in reducing number of incoming SSSD cases. How? 1. We can ask customer to run this utility to do SSSD Authentication health check. 2. This utility can prompt the Issue area{Eg: Join not done or so}, if system is not able to join AD(for example) using SSSD.
You can see the code of this RFE at https://github.com/SSSD/sssd/pull/200
Metadata Update from @jhrozek: - 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
Isn't this ticket a duplicate to #3292? If yes, let's close it as such, to track in a single place.
Metadata Update from @mkosek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
Yes, sorry, we already closed some downstream duplicates, but not upstream
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Duplicate of https://pagure.io/SSSD/sssd/issue/3292
Metadata Update from @lslebodn: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
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/4291
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.