Skip to content

Accept Multiple Providers in TagBasedAccessPolicy -- ON HOLD#1352

Open
genematx wants to merge 1 commit into
bluesky:mainfrom
genematx:access-policy-multi-provider
Open

Accept Multiple Providers in TagBasedAccessPolicy -- ON HOLD#1352
genematx wants to merge 1 commit into
bluesky:mainfrom
genematx:access-policy-multi-provider

Conversation

@genematx
Copy link
Copy Markdown
Contributor

Allow configuring multiple identity providers in TagBasedAccessPolicy by accepting either a single string or a list of strings for the provider parameter.

Checklist

  • Add a Changelog entry
  • Add the ticket number which this PR closes to the comment section

Allow configuring multiple identity providers in TagBasedAccessPolicy
by accepting either a single string or a list of strings for the
provider parameter.
@genematx genematx mentioned this pull request Apr 22, 2026
1 task
@nmaytan
Copy link
Copy Markdown
Contributor

nmaytan commented Apr 22, 2026

I'm a bit concerned about this under the current implementation, as there is no protection against a case like this:

personA is identity1 according to providerX
personB is identity2 according to providerX

personA is identity2 according to providerY

If identity2 is used in AuthZ, this could give access meant for personB to personA. I wrote up some thoughts about what to do about this, I can share them.

This is why the access policy was locked to a single provider for now.

@genematx genematx changed the title Accept Multiple Providers in TagBasedAccessPolicy Accept Multiple Providers in TagBasedAccessPolicy -- ON HOLD Apr 28, 2026
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.

2 participants