- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 10 for KeyCloak (0.12 sec)
-
internal/config/identity/openid/provider/keycloak.go
// WithAdminURL provide admin URL configuration for Keycloak func WithAdminURL(url string) Option { return func(p *KeycloakProvider) { p.adminURL = url } } // WithRealm provide realm configuration for Keycloak func WithRealm(realm string) Option { return func(p *KeycloakProvider) { p.realm = realm } } // KeyCloak initializes a new keycloak provider func KeyCloak(opts ...Option) (Provider, error) {
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Jul 14 18:12:07 UTC 2024 - 4.6K bytes - Viewed (0) -
internal/config/identity/openid/jwt_test.go
testConfig := providerCfg{ DiscoveryDoc: DiscoveryDoc{ TokenEndpoint: "http://keycloak.test/token/endpoint", }, } testKvs := config.KVS{} testKvs.Set(Vendor, "keycloak") testKvs.Set(KeyCloakRealm, "TestRealm") testKvs.Set(KeyCloakAdminURL, "http://keycloak.test/auth/admin") cfgGet := func(param string) string { return testKvs.Get(param) }
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri May 24 23:05:23 UTC 2024 - 8.3K bytes - Viewed (0) -
helm/minio/README.md
For instance, given that TLS is 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: ```
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Jan 24 07:27:57 UTC 2024 - 10.9K bytes - Viewed (0) -
internal/config/identity/openid/providercfg.go
ClientID: getCfgVal(ClientID), ClientSecret: getCfgVal(ClientSecret), RolePolicy: getCfgVal(RolePolicy), } } const ( keyCloakVendor = "keycloak" ) // initializeProvider initializes if any additional vendor specific information // was provided, initialization will return an error initial login fails.
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri May 24 23:05:23 UTC 2024 - 4.6K bytes - Viewed (0) -
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 Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Jul 10 20:16:44 UTC 2024 - 18.9K bytes - Viewed (0) -
compat/maven-model-builder/src/test/resources/dag.txt
quarkus/test-framework/junit5/pom.xml quarkus/test-framework/kafka-companion/pom.xml quarkus/integration-tests/keycloak-authorization/pom.xml quarkus/extensions/keycloak-authorization/runtime/pom.xml quarkus/extensions/keycloak-admin-client-reactive/runtime/pom.xml quarkus/extensions/resteasy-reactive/quarkus-resteasy-reactive-jackson/runtime/pom.xml quarkus/extensions/oidc/runtime/pom.xml
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 224K bytes - Viewed (0) -
helm-releases/minio-5.0.15.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Jan 12 18:18:57 UTC 2024 - 20.8K bytes - Viewed (0) -
helm-releases/minio-5.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Mar 03 18:49:37 UTC 2024 - 21.3K bytes - Viewed (0) -
helm-releases/minio-5.2.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Apr 28 10:14:37 UTC 2024 - 21.7K bytes - Viewed (0) -
helm-releases/minio-5.3.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Oct 11 12:21:05 UTC 2024 - 21.7K bytes - Viewed (0)