Description of problem:
When we configure AD auth using ktpass (or ktutil in past), and the RHEL VM is domain joined directly with Windows AD server, S4U2Self protocol functions correctly and we see no issues. But when RHEL VM is joined via IdM, the group refresh process done via S4U2Self protocol fails. That breaks the logged in user’s privilege and overall functionality suffers.
Version-Release number of selected component (if applicable):
How reproducible:
When running some elevated SQL commands which involve activities such as creating logins or granting/revoking privileges
Steps to Reproduce:
1. Configure AD login to MSSQL with https://access.redhat.com/articles/4094741
2. Create two SQL logins
3. Try to run elevated commands with both users logged in
Actual results:
AD authentication works but then users(who is ever logged in with AD authentication) get kicked out from sessions and when running some elevated SQL commands which involve activities such as creating logins or granting/revoking privileges and in krb5.log we see events like:
-1765328243/Matching credential not found [25649] 1583325123.545595: Getting credentials EXAMPLE2$@NIX.EXAMPLE.COM -> krbtgt/EXAMPLE.COM.COM using ccache MEMORY:pal 25837 [25649] 1583325123.545596: Retrieving EXAMPLE$@NIX.EXAMPLE.COM -> krbtgt/EXAMPLE.COM.COM from MEMORY:pal 25837 with result: -1765328243/Matching credential not found [25649] 1583325123.545597: Retrieving EXAMPLE$@NIX.EXAMPLE.COM -> krbtgt/NIX.EXAMPLE.COM.COM from MEMORY:pal 25837 with result: -1765328243/Matching credential not found
In the client we see the following:
Error:15404 (Could Not obtain information about Windows NT group/User' ' Error Code 0x80090304
Expected results:
Users to not get kicked out from sessions and commands to work
Additional info:
I will include more details in the next comment.
Comment 10Alexander Bokovoy
2020-05-11 17:02:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: idm:DL1 and idm:client security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4670