OPA for front-end authorization #276
Unanswered
humbertoc-silva
asked this question in
OPA and Rego
Replies: 2 comments 4 replies
-
I don't have any hands on experience with this, but a talk on this topic was given at OPA Summit in the past. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Yeah, having the frontend query an OPA in the backend, or a service talking to OPA, in order to e.g. toggle what the user sees, seems like the most common approach. Wasm is an interesting option for front-end evaluation of policy. I don't know of any public open source project to point at for an example though. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
In all material that a read about OPA, the principal use case is to use it to authorize the back-end (and other cases like K8s, pipelines, etc.)
I would like to know if anyone already used OPA on front-end authorization, for example, to return a JSON response to the front-end with information related to the menus, buttons, and fields that a certain user can access based on certain rules.
If this is a valid use case, how can this be done? Maybe exposing an OPA instance to the front-end app get this information.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions