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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The Stackable HDFS already takes care of this, you don't need to do anything in
26
26
27
27
- Set `dfs.namenode.inode.attributes.provider.class` in `hdfs-site.xml` to `tech.stackable.hadoop.StackableAuthorizer`
28
28
- Set `hadoop.security.authorization.opa.policy.url` in `core-site.xml` to the HTTP endpoint of your OPA rego rule, e.g. `http://opa.default.svc.cluster.local:8081/v1/data/hdfs/allow`
29
-
- The property `hadoop.security.authorization.opa.extended-requests` (defaults to `false`), which controls if all fields should be sent to OPA.
29
+
- The property `hadoop.security.authorization.opa.extended-requests` (defaults to `false`)controls if all fields (`true`) should be sent to OPA or only a subset
30
30
Sending all fields degrades the performance, but allows for more advanced authorization.
0 commit comments