You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The feature allows defining a custom model, where, for example, applications can be grouped by audience, or in application role/groups, and have permissions to different stores based on those.
In some cases, it's possible to get the Identity Provider that issues tokens to add claims that specify those relations (audience, application_roles).
It would be helpful to allow configuring the Authorization Control feature to map the token claims to contextual tuples, to avoid having to synchronize that data in OpenFGA.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
OpenFGA currently supports a way to specify per-application permissions with the Access Control feature https://openfga.dev/docs/getting-started/setup-openfga/access-control.
The feature allows defining a custom model, where, for example, applications can be grouped by audience, or in application role/groups, and have permissions to different stores based on those.
In some cases, it's possible to get the Identity Provider that issues tokens to add claims that specify those relations (audience, application_roles).
It would be helpful to allow configuring the Authorization Control feature to map the token claims to contextual tuples, to avoid having to synchronize that data in OpenFGA.
Beta Was this translation helpful? Give feedback.
All reactions