📝(self-hosted) update collaboration vars #1075
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
As an aside, to login with Keycloak I had to change the backend to use http instead of https. I don't understand why this is necessary, since the backend container is already mounting the CA certificate. diff --git a/docs/examples/impress.values.yaml b/docs/examples/impress.values.yaml
index d0f04bf5..10f1797a 100644
--- a/docs/examples/impress.values.yaml
+++ b/docs/examples/impress.values.yaml
@@ -23,10 +23,10 @@ backend:
LOGGING_LEVEL_HANDLERS_CONSOLE: ERROR
LOGGING_LEVEL_LOGGERS_ROOT: INFO
LOGGING_LEVEL_LOGGERS_APP: INFO
- OIDC_OP_JWKS_ENDPOINT: https://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/certs
- OIDC_OP_AUTHORIZATION_ENDPOINT: https://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/auth
- OIDC_OP_TOKEN_ENDPOINT: https://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/token
- OIDC_OP_USER_ENDPOINT: https://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/userinfo
+ OIDC_OP_JWKS_ENDPOINT: http://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/certs
+ OIDC_OP_AUTHORIZATION_ENDPOINT: http://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/auth
+ OIDC_OP_TOKEN_ENDPOINT: http://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/token
+ OIDC_OP_USER_ENDPOINT: http://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/userinfo
OIDC_OP_LOGOUT_ENDPOINT: https://keycloak.127.0.0.1.nip.io/realms/impress/protocol/openid-connect/session/end
OIDC_RP_CLIENT_ID: impress
OIDC_RP_CLIENT_SECRET: ThisIsAnExampleKeyForDevPurposeOnly |
Remove the `auth-url` annotation and add the `COLLABORATION_BACKEND_BASE_URL` variable, introduced in 3.0.0. Mount the development CA to the yProvider container to allow TLS connections with the backend. Signed-off-by: eduxstad <eduxstad@gmail.com>
eduxstad
force-pushed
the
update-example-helm-values
branch
from
71fcf22 to
cde2227
Compare
eduxstad
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove the
auth-urlannotation and add theCOLLABORATION_BACKEND_BASE_URLvariable, introduced in 3.0.0.Mount the development CA to the yProvider container to allow TLS connections with the backend.
Purpose
The helm charts are outdated as of release 3.0.0. This adds the correct variables and certificates for yProvider when deploying to the example kind cluster.