feat(auth): add inGroup() method for owner authorization #643
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
Add support for requiring group membership with owner-based auth rules. The new `owner().inGroup()` API allows defining authorization rules where users must be both the owner AND a member of specified groups. - Add `inGroup()` method to owner, ownerDefinedIn, and ownersDefinedIn - Groups specified via inGroup() are passed to the transformer for AND logic - Add comprehensive tests for inGroup() with various combinations 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: c99ebac The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
Currently, owner-based authorization and group-based authorization are separate strategies that work with OR logic. There's no way to require that a user must be both the owner AND a member of a specific group to access a resource (AND logic).
Issue number, if available: aws-amplify/amplify-category-api#3381
Changes
Add
inGroup()method to owner authorization rules that allows requiring group membership in addition to owner matching:inGroup(...groups: string[])method toowner(),ownerDefinedIn(), andownersDefinedIn()inGroup()are passed to the transformer via thegroupsfield on owner rulesgroupson an owner rule as AND logic (must be owner AND in group)Example usage:
Corresponding docs PR, if applicable: TBD
Validation
inGroup()with various combinations (552 tests passed)groupson owner rulesChecklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.