Skip to content

Commit 7f92392

Browse files
committed
docs: Fix wrong OPA configMapName docs
1 parent 49b63b3 commit 7f92392

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/modules/superset/pages/usage-guide/security.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -177,19 +177,19 @@ spec:
177177
clusterConfig:
178178
authorization:
179179
roleMappingFromOpa:
180-
configMapName: superset-opa-regorules # <1>
180+
configMapName: opa # <1>
181181
package: superset
182182
cache: # <2>
183183
entryTimeToLive: 10s # <3>
184184
maxEntries: 5 # <4>
185185
----
186186

187-
<1> ConfigMap name containing rego rules
188-
<2> Mandatory Opa caching. If not set, default settings apply.
189-
<3> Time for cached entries per user can live. Defaults to 30s.
190-
<4> Number of maximum entries, defaults to 1000. Cache will be disabled for maxEntries: 0.
187+
<1> Discovery ConfigMap of your OpaCluster
188+
<2> Optional caching of group memberships. If not set, default settings apply.
189+
<3> Time to live for cached user entries. Defaults to 30s.
190+
<4> Maximum number of entries, defaults to 1000. Cache will be disabled for maxEntries: 0.
191191

192-
IMPORTANT: Any role assignments done in the Superset UI are discarded and will be overridden by the OPA security manager.
192+
IMPORTANT: Any role assignments done in the Superset UI are discarded and will be overridden by the OPA security manager. Groups are only sync on log in!
193193

194194
=== Superset database
195195

0 commit comments

Comments
 (0)