Learn more about these different git repos.
Other Git URLs
Related to https://fedorahosted.org/sssd/ticket/2476.
When using mod_intercept_form_submit with pam_sss.so, the user can authenticate with AD user credentials with login in uppercase, lowercase, or their combination. We'd need a way to obtain canonical username (and realm/domain), ideally the same as we get from Kerberos authentication, so that when the application has case-sensitive users, we don't autocreate new user record with every new case combination that is used.
Or should this be a task for mod_intercept_form_submit and mod_auth_kerb/mod_auth_gssapi, to (say) lowercase the username?
While it is possible to easy get the "normalized" name of a POSIX user with getpwnam() this will not work for non-POSIX user. In this case returning the name which is already available in the PAM responder via the PAM environment would be the best option because e.g. using infopipe would add additional dependencies.
But I think we should not use the Kerberos principal here but the name return by SSSD e.g. via getpwnam() because this will not change and is easily accessible for all application hence the best candidate for a normalized name. Additionally it does not limit authentication to Kerberos.
Fields changed
rhbz: => 0
milestone: NEEDS_TRIAGE => SSSD 1.13 alpha
Should not block Alpha
milestone: SSSD 1.13 alpha => SSSD 1.13 beta sensitive: => 0
Not strictly required by downstream
milestone: SSSD 1.13 beta => SSSD 1.13 priority: major => minor
owner: somebody => mzidek
This is important for the multitenancy case, but we're already trying to stabilize 1.13..moving to 1.14.
milestone: SSSD 1.13.2 => SSSD 1.14 beta
priority: minor => major
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1201262 (Red Hat Enterprise Linux 7)
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=1201262 1201262]
Because the bugzilla linked to this ticket was about sssd running in a container and this ticket is more about better support for Apache modules and similar 3rd party integration, I'm removing the bugzilla link.
Moreover, it looks like Jan doesn't need this ticket implemented in the immediate future, so I'm also moving the ticket to the 1.14 backlog.
milestone: SSSD 1.14 beta => SSSD 1.14 backlog rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1201262 1201262] => todo
Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.
milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)
Metadata Update from @adelton: - Issue assigned to mzidek - Issue set to the milestone: SSSD Future releases (no date set yet)
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
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)
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/3630
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.