-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[sssd] User lookup on IPA client fails with 's2n get_fqlist request failed' #6720
Labels
Comments
Bugzilla Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2192708 |
sumit-bose
added a commit
to sumit-bose/sssd
that referenced
this issue
May 10, 2023
When checking if the input group-name is the original name from AD or an overwritten one the comparison is currently done case sensitive. Since AD handles names case-insensitive and hence SSSD should do this as well this comparison might cause issues. The patch replace the case sensitive comparison with a comparison with respects the case_sensitive of the domain the object is coming from. Resolves: SSSD#6720
pbrezina
pushed a commit
that referenced
this issue
May 15, 2023
When checking if the input group-name is the original name from AD or an overwritten one the comparison is currently done case sensitive. Since AD handles names case-insensitive and hence SSSD should do this as well this comparison might cause issues. The patch replace the case sensitive comparison with a comparison with respects the case_sensitive of the domain the object is coming from. Resolves: #6720 Reviewed-by: Alexey Tikhonov <atikhono@redhat.com> Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com> (cherry picked from commit 01d0279)
alexey-tikhonov
pushed a commit
to alexey-tikhonov/sssd
that referenced
this issue
May 15, 2023
When checking if the input group-name is the original name from AD or an overwritten one the comparison is currently done case sensitive. Since AD handles names case-insensitive and hence SSSD should do this as well this comparison might cause issues. The patch replace the case sensitive comparison with a comparison with respects the case_sensitive of the domain the object is coming from. Resolves: SSSD#6720 Reviewed-by: Alexey Tikhonov <atikhono@redhat.com> Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com> (cherry picked from commit 01d0279)
alexey-tikhonov
pushed a commit
that referenced
this issue
May 16, 2023
When checking if the input group-name is the original name from AD or an overwritten one the comparison is currently done case sensitive. Since AD handles names case-insensitive and hence SSSD should do this as well this comparison might cause issues. The patch replace the case sensitive comparison with a comparison with respects the case_sensitive of the domain the object is coming from. Resolves: #6720 Reviewed-by: Alexey Tikhonov <atikhono@redhat.com> Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com> (cherry picked from commit 01d0279) Reviewed-by: Alexey Tikhonov <atikhono@redhat.com>
etrunko
pushed a commit
to etrunko/sssd
that referenced
this issue
Oct 11, 2023
When checking if the input group-name is the original name from AD or an overwritten one the comparison is currently done case sensitive. Since AD handles names case-insensitive and hence SSSD should do this as well this comparison might cause issues. The patch replace the case sensitive comparison with a comparison with respects the case_sensitive of the domain the object is coming from. Resolves: SSSD#6720 Reviewed-by: Alexey Tikhonov <atikhono@redhat.com> Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com> (cherry picked from commit 01d0279)
etrunko
pushed a commit
to etrunko/sssd
that referenced
this issue
Oct 11, 2023
When checking if the input group-name is the original name from AD or an overwritten one the comparison is currently done case sensitive. Since AD handles names case-insensitive and hence SSSD should do this as well this comparison might cause issues. The patch replace the case sensitive comparison with a comparison with respects the case_sensitive of the domain the object is coming from. Resolves: SSSD#6720 Reviewed-by: Alexey Tikhonov <atikhono@redhat.com> Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com> (cherry picked from commit 01d0279)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem
Trusted AD user information cannot be retrieved from IPA clients if trusted user name contains upper/mixed case characters and is configured with overrides.
IDM server is able to see the user running the same pkg release.
Operation returns:
Version-Release number of selected component (if applicable)
sssd-2.7.3-4.el8_7.3.x86_64
How reproducible
Always
Steps to Reproduce
Actual results
id: ‘con81001@ad.example.com’: no such user
Expected results
uid=645601103(con81001@ad.example.com) gid=645601103(con81001@ad.example.com) groups=645601103(con81001@ad.example.com)
Additional info
Request from client fails with:
The text was updated successfully, but these errors were encountered: