Learn more about these different git repos.
Other Git URLs
Sudo responder search rules only with user name which may fail on case insensitive domains. We should also search by alias on such configuration.
By the way, this ticket is different for 1.13 and 1.14 as we found out with Pavel. In 1.13, we would only search for the original case (so, the rules should have Administrator) and in 1.14, we search for the lowercase only.
Both are wrong, we should search for name and nameAlias for lowercase domains.
_comment0: By the way, this ticket is different for 1.13 and 1.14 as we found out in master. In 1.13, we would only search for the original case (so, the rules should have Administrator) and in 1.14, we search for the lowercase only.
Both are wrong, we should search for name and nameAlias for lowercase domains. => 1474972592269677
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.14.2 priority: major => critical
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1380436
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1380436 1380436]
owner: somebody => pcech status: new => assigned
cc: => john@redux.org.uk
patch: 0 => 1
Moving tickets that didn't make it into the 1.14.2 release into the next point release.
milestone: SSSD 1.14.2 => SSSD 1.14.3
resolution: => fixed status: assigned => closed
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1372440 (Red Hat Enterprise Linux 7)
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1380436 1380436] => [https://bugzilla.redhat.com/show_bug.cgi?id=1380436 1380436], [https://bugzilla.redhat.com/show_bug.cgi?id=1372440 1372440]
Additional patch for sssd-1-13 only that fixes a coverity warning
Metadata Update from @pbrezina: - Issue assigned to pcech - Issue set to the milestone: SSSD 1.14.3
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/4236
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.