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
Copy file name to clipboardExpand all lines: docs/modules/superset/pages/usage-guide/security.adoc
+60Lines changed: 60 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,6 +126,66 @@ Further information for specifying an AuthenticationClass for an OIDC provider c
126
126
Superset has a concept called `Roles` which allows you to grant user permissions based on roles.
127
127
Have a look at the {superset-security}[Superset documentation on Security^{external-link-icon}^].
128
128
129
+
=== [[Opa]] Opa Roles Mapping
130
+
131
+
Superset can sync roles from open policy agent. Currently only mapping is enabled as a larger refactoring of the upstream superset concerning their security management is announced.
132
+
133
+
In order to map roles from Opa into superset, we expect rego rules with a rule name `user_roles`. In the below example two users `admin` and `testuser` have roles defined as rego rule in Rego V1 to be complient with OPA v1.0.0 release.
134
+
135
+
IMPORTANT: Only role mapping is enabled. Permissions can only be added through the Superset UI. RBAC through OPA is not implemented.
0 commit comments