Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@pedroigor
Copy link
Contributor

Closes #38566

@pedroigor pedroigor requested a review from a team as a code owner April 3, 2025 14:35
@pedroigor
Copy link
Contributor Author

@sschu Can you please check this one? I think it is aligned with what we discussed ...

@vramik
Copy link
Contributor

vramik commented Apr 3, 2025

@pedroigor I believe we should update this:

** The *user-impersonated* user permission has been _removed_.

by saying something like:

  ** The *user-impersonated* user permission has been _removed_ and _replaced_ by *impersonate-members* group permission.

@pedroigor
Copy link
Contributor Author

@pedroigor I believe we should update this:

** The *user-impersonated* user permission has been _removed_.

by saying something like:

  ** The *user-impersonated* user permission has been _removed_ and _replaced_ by *impersonate-members* group permission.

Makes sense, I'll update the docs.

@pedroigor
Copy link
Contributor Author

@vramik Added your suggestion to the upgrade guide.

@vramik
Copy link
Contributor

vramik commented Apr 3, 2025

@pedroigor thanks, lgtm. I'd love to have @sschu's review as well.

@sschu
Copy link
Contributor

sschu commented Apr 3, 2025

@pedroigor @vramik I'll have a look. Will probably only finish tomorrow, I hope thats OK.

The evaluation takes permissions for specific resources (specific user permissions and specific group permissions) first.
See <<_resolving-conflicting-permissions, Resolving Conflicting Permissions>> for more information.
- Similarly, the *manage* operation takes *manage-members* into account when managing group members.
- Similarly, the *manage* operation takes *manage-members* into account when managing group members.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pedroigor we should probably mention here that this "taking-into-account" applies to impersonation as well, wdyt?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a second commit with some updates to the docs. I can send a separate PR if you prefer, but perhaps we can just agree on it here.

@pedroigor pedroigor force-pushed the issue-38566 branch 2 times, most recently from e49c2a5 to 5045b62 Compare April 4, 2025 10:45
@sschu
Copy link
Contributor

sschu commented Apr 4, 2025

@pedroigor @vramik I finally tested this branch and the impersonate-part works as expected. However, I found some issues with the view-members and manage-members permissions. I'll send you a reproducer directly via mail.

@pedroigor pedroigor force-pushed the issue-38566 branch 2 times, most recently from e10192c to c609e34 Compare April 7, 2025 12:54
@ahus1 ahus1 enabled auto-merge (squash) April 7, 2025 12:58
Copy link
Contributor

@ahus1 ahus1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving based on @vramik's review

@ahus1 ahus1 merged commit 87430fc into keycloak:main Apr 7, 2025
77 checks passed
@pedroigor pedroigor deleted the issue-38566 branch April 7, 2025 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add impersonate-members scope to group resource type

4 participants