Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 13 for Keycloak (1.29 sec)

  1. docs/sts/web-identity.md

    MINIO_IDENTITY_OPENID_KEYCLOAK_REALM        (string)    Specify Keycloak 'realm' name, only honored if vendor was set to 'keycloak' as value, if no realm is specified 'master' is default
    MINIO_IDENTITY_OPENID_KEYCLOAK_ADMIN_URL    (string)    Specify Keycloak 'admin' REST API endpoint e.g. http://localhost:8080/auth/admin/
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 18.9K bytes
    - Viewed (0)
  2. helm-releases/minio-2.0.1.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 31 09:09:09 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  3. helm-releases/minio-3.0.0.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  4. helm-releases/minio-1.0.2.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 24 18:58:05 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  5. helm-releases/minio-3.0.1.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  6. helm-releases/minio-3.0.2.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Sep 03 08:11:32 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  7. helm-releases/minio-3.1.0.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Sun Sep 12 18:19:27 UTC 2021
    - 14.3K bytes
    - Viewed (0)
  8. helm-releases/minio-1.0.0.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 20 22:30:54 UTC 2021
    - 13.5K bytes
    - Viewed (0)
  9. helm-releases/minio-1.0.1.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 20 22:32:29 UTC 2021
    - 13.5K bytes
    - Viewed (0)
  10. helm-releases/minio-1.0.3.tgz

    enabled and you need to add trust for Minio's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 24 19:04:07 UTC 2021
    - 13.6K bytes
    - Viewed (0)
Back to top