Fix getImplicitPermissionsForUser for wildcard domain policies in role hierarchies #527
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.
getImplicitPermissionsForUser()fails to retrieve permissions when roles inherit from abstract roles with wildcard domain policies (*). This prevents role hierarchy patterns where permissions are defined once with domain*and inherited by domain-specific roles.Changes
getImplicitRolesForUser*when retrieving rolesg(r.sub, p.sub, r.dom) || g(r.sub, p.sub, '*')getImplicitPermissionsForUsermodel.getFieldIndex()to locate domain field instead of assuming sequential position*Example
Test coverage added for role hierarchy with wildcard domains. All existing tests pass.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.