Skip to content

📝(self-hosted) update collaboration vars #1075

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 24, 2025

Conversation

eduxstad
Copy link
Contributor

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.

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.

Screenshot from 2025-06-15 12-54-00

@eduxstad
Copy link
Contributor Author

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

@eduxstad eduxstad force-pushed the update-example-helm-values branch from 71fcf22 to cde2227 Compare June 18, 2025 06:00
@eduxstad eduxstad changed the title 📝(self-hosted) Update collaboration vars 📝(self-hosted) update collaboration vars Jun 18, 2025
@eduxstad eduxstad force-pushed the update-example-helm-values branch from cde2227 to 82cd921 Compare June 22, 2025 02:28
@eduxstad
Copy link
Contributor Author

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.

Figured this one out. Updated.

@lunika
Copy link
Member

lunika commented Jun 23, 2025

Hi @eduxstad can you rebase your branch with the main one and fix the lint-git job ?
Thanks

@eduxstad eduxstad force-pushed the update-example-helm-values branch 3 times, most recently from 0b57544 to 9e739cb Compare June 24, 2025 05:57
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.

Fix the mount path for development CA in the backend container.

Signed-off-by: eduxstad <[email protected]>
@eduxstad eduxstad force-pushed the update-example-helm-values branch from 9e739cb to eead1ad Compare June 24, 2025 06:00
@eduxstad
Copy link
Contributor Author

updated and rebased

@lunika lunika enabled auto-merge (squash) June 24, 2025 06:09
@lunika lunika merged commit ff8275f into suitenumerique:main Jun 24, 2025
18 of 20 checks passed
@lunika
Copy link
Member

lunika commented Jun 24, 2025

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants