Include link to alternative examples to Auth0 in the validator auth setup docs (#2149)

Signed-off-by: Brian Healey <brian.healey@daml.com>
Signed-off-by: Brian Healey <brian.healey@digitalasset.com>

Author: dasormeter

docs/src/community/docker-compose-helm-chart.rst

@@ -8,6 +8,11 @@
 Alternative Docker Compose Deployment
 =====================================
 
+.. warning::
+
+   This section features solutions shared by community members. While they haven’t been formally tested by the Splice maintainers, 
+   users are encouraged to verify the information independently. Contributions to enhance accuracy and completeness are always welcome.
+
 This guide introduces a community-contributed Docker Compose solution for deploying Canton validator nodes and supporting infrastructure, following the ``x-docker`` standard used by Mario Delgado’s team for onboarding blockchains.
 Note that while it was tested during a scheduled upgrade on DevNet, that required
 updating the ``.env`` file with the migration ID, renaming the databases (with a planned change to use standardized names like ``participant_${MIGRATION_ID}`` and ``validator_${MIGRATION_ID}``), and including ``validator-migration.yaml`` as part of the migration setup. For further information, please contact the authors of the contribution.

docs/src/community/helm-kubernetes-templating-tool.rst

@@ -8,6 +8,13 @@
 Automated Helm/Kubernetes Templating Tool
 =========================================
 
+.. warning::
+
+   This section features solutions shared by community members. 
+   While they haven’t been formally tested by the Splice maintainers, 
+   users are encouraged to verify the information independently. 
+   Contributions to enhance accuracy and completeness are always welcome.
+
 Managing deployments for Validator and Super Validator nodes using Kubernetes, Helm, and Git can be challenging,
 especially when keeping multiple environments (DevNet, TestNet, MainNet) in sync with evolving configuration files and values.
 Frequent version bumps, new variables, and hard migrations often require manual, error-prone updates to numerous ``values-*.yml`` files.

docs/src/community/oidc-config-okta-keycloak.rst

@@ -8,6 +8,13 @@
 Okta and Keycloak OIDC Configuration Guide
 ==========================================
 
+.. warning::
+
+   This section features solutions shared by community members. 
+   While they haven’t been formally tested by the Splice maintainers, 
+   users are encouraged to verify the information independently. 
+   Contributions to enhance accuracy and completeness are always welcome.
+
 To deploy a validator node, configure authentication using your preferred OIDC provider. 
 This section provides instructions for Okta and Keycloak. 
 For Auth0 instructions and more details on configuring authentication, see :ref:`Configuring Authentication <helm-validator-auth>`.

docs/src/validator_operator/validator_helm.rst

@@ -119,7 +119,9 @@ OIDC Provider Requirements
 ++++++++++++++++++++++++++
 
 This section provides pointers for setting up an OIDC provider for use with your Validator node.
-Feel free to skip directly to :ref:`helm-validator-auth0` if you plan to use `Auth0 <https://auth0.com>`_ for your Validator node's authentication needs.
+Feel free to skip directly to :ref:`helm-validator-auth0` if you plan to use `Auth0 <https://auth0.com>`_ for your Validator node's authentication needs.  
+
+These docs focus on Auth0, and are being continuously tested and maintained. Other OIDC providers can be used, and are in active use by various community members, who have contributed some notes and examples in `Okta and Keycloak community authored examples </community/oidc-config-okta-keycloak.html>`.
 
 Your OIDC provider must be reachable [#reach]_ at a well known (HTTPS) URL.
 In the following, we will refer to this URL as ``OIDC_AUTHORITY_URL``.