ipa s2n: do not try to update user-private-group #8002
+28
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Is this related to https://issues.redhat.com/browse/RHEL-94545 ? |
pbrezina
force-pushed
the
master
branch
2 times, most recently
from
f5d64b3 to
b854636
Compare
When an IPA client requests the details about a trusted user from the IPA server including its memberships the server will return the name of all groups including the user-private-group. Since this group is not a cached object on its own it is not needed to try to update it as a group but it will be updated when the user object is updated. This has to be taken into account especially after a client is assigned to a new id-view because now the SYSDB_OVERRIDE_DN attribute is required and all cached objects which are missing it must be updated. If the user-private-group was found for update it should be skipped because the calls to update group objects in the cache cannot handle user-private-groups. This is expected behavior as user-private-groups are not objects on their own.
sumit-bose
force-pushed
the
mpg_after_view_change
branch
from
88f9155 to
2c72fc0
Compare
Member
|
@sumit-bose, is there a related ticket? |
Contributor
Author
Yes, this issue is present in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When an IPA client requests the details about a trusted user from the
IPA server including its memberships the server will return the name of
all groups including the user-private-group. Since this group is not a
cached object on its own it is not needed to try to update it as a group
but it will be updated when the user object is updated.
This has to be taken into account especially after a client is assigned
to a new id-view because now the SYSDB_OVERRIDE_DN attribute is required
and all cached objects which are missing it must be updated. If the
user-private-group was found for update it should be skipped because the
calls to update group objects in the cache cannot handle
user-private-groups. This is expected behavior as user-private-groups
are not objects on their own.