-
Notifications
You must be signed in to change notification settings - Fork 256
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 with poor connectivity #7811
Comments
And when connection is good? Do you call 'groups' without arguments or 'groups $user'? |
And what is output of |
I'm a novice DevOps specialist, I haven't tried any other teams, just groups. When the connection is excellent, if you enter the groups command from the domain user, the result will be something like this: domain users dialout . If the connection is bad and the user has logged in using cached data, then when entering groups it will be like this: domain users , i.e. without a local dialout group. The fact is that the dialout group, for example, is needed to access the COM ports on which the cash registers operate. And if the user loses access to the dialout group, then access to the COM ports is also lost. |
I will try it and then answer to you :) |
Output is: |
Sounds like initgroups list is set incorrectly / differently when logging in offline... When "connection is bad", can you also try |
In general, I tried logging in with my cached domain account on my PC with the network disconnected. The |
Still it returns a correct list of domain groups but local groups are missing?
Enable 'debug_level = 9' in 'nss' and domain sections of sssd.conf and the extract logs covering |
When the connection with the domain controller is good, the user logs into the system without any problems. On some PCs, I added domain users to local Linux groups such as dialout, but when the connection is bad and authorization takes place offline using the cache, when I enter the groups command from this user, I see that the local dialout group is missing. What could be the cause and how to fix it?
The text was updated successfully, but these errors were encountered: