Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

Auto-update documentation for master (#81619)

github-automation-metabase9e2fa97aa152
diff --git a/docs/api.json b/docs/api.json
index 5aefebcb4a6..1cb217fc27d 100644
--- a/docs/api.json
+++ b/docs/api.json
@@ -6378,7 +6378,7 @@
"required" : [ "metrics", "dimension_groups" ]
},
"metabase.explorations.api.ExplorationBlockNode" : {
- "description" : "A block (the FE's sidebar group): a heading plus its pages. `:type` is whether the block is\n anchored on its metric or its dimension; `:name` is the computed heading (the metric name, or\n `By <dimension>`). `:position` is the block's 0-indexed authoring slot.",
+ "description" : "A block (the FE's sidebar group): a heading plus its pages. `:name` is the computed heading\n (the metric name). `:position` is the block's 0-indexed authoring slot.",
"type" : "object",
"properties" : {
"explore_filters" : {
@@ -6500,13 +6500,9 @@
"description" : "value must be an integer greater or equal to than zero.",
"type" : "integer",
"minimum" : 0
- },
- "type" : {
- "type" : "string",
- "enum" : [ "metric", "dimension" ]
}
},
- "required" : [ "id", "type", "name", "position", "pages" ]
+ "required" : [ "id", "name", "position", "pages" ]
},
"metabase.explorations.api.ExplorationDimensionGroup" : {
"description" : "Schema for a dimension group in the /dimensions response. A group bundles together dimensions that\n refer to the same underlying source (same field/binning) so the FE can show a single user-facing\n entry while still tracking the actual per-metric dimensions needed by `start exploration`.",
@@ -37362,14 +37358,6 @@
}, {
"type" : "null"
} ]
- },
- "type" : {
- "oneOf" : [ {
- "type" : "string",
- "enum" : [ "metric", "dimension" ]
- }, {
- "type" : "null"
- } ]
}
}
}
diff --git a/docs/configuring-metabase/config-template.md b/docs/configuring-metabase/config-template.md
index fdcc721d140..f7fe921bfc1 100644
--- a/docs/configuring-metabase/config-template.md
+++ b/docs/configuring-metabase/config-template.md
@@ -201,8 +201,10 @@ config:
ldap-port: 389
ldap-security: none
ldap-sync-user-attributes: true
+ ldap-sync-user-attributes-allowlist: ''
ldap-sync-user-attributes-blacklist: userPassword,dn,distinguishedName
ldap-timeout-seconds: 15.0
+ ldap-trust-store: null
ldap-user-base: null
ldap-user-filter: (&(objectClass=inetOrgPerson)(|(uid={login})(mail={login})))
ldap-user-provisioning-enabled: true
diff --git a/docs/configuring-metabase/environment-variables.md b/docs/configuring-metabase/environment-variables.md
index 37d9aab824d..4eafb7e3ed4 100644
--- a/docs/configuring-metabase/environment-variables.md
+++ b/docs/configuring-metabase/environment-variables.md
@@ -1239,6 +1239,14 @@ Use SSL, TLS or plain text.
Should we sync user attributes when someone logs in via LDAP?
+### `MB_LDAP_SYNC_USER_ATTRIBUTES_ALLOWLIST`
+
+- Type: csv
+- Default: ``
+- [Configuration file name](./config-file.md): `ldap-sync-user-attributes-allowlist`
+
+Comma-separated list of user attributes to sync for LDAP users. Only these attributes are synced; leave blank to sync none.
+
### `MB_LDAP_SYNC_USER_ATTRIBUTES_BLACKLIST`
- Type: csv
@@ -1255,6 +1263,14 @@ Comma-separated list of user attributes to skip syncing for LDAP users.
Maximum time, in seconds, to wait for LDAP server before falling back to local authentication.
+### `MB_LDAP_TRUST_STORE`
+
+- Type: string
+- Default: `null`
+- [Configuration file name](./config-file.md): `ldap-trust-store`
+
+Path to a JKS trust store of CA certificates used to validate the LDAP server's TLS certificate. Leave blank to use the JVM default trust store.
+
### `MB_LDAP_USER_BASE`
- Type: string