-
Notifications
You must be signed in to change notification settings - Fork 143
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
[ISSUE] Invalid Redirect URI in Camunda Platform 8.3.3 #1116
Comments
Hi @failnix thanks for reporting this. Your guess is correct, the issue comes from the static trim Do you like to make a PR to fix that? |
Hi @aabouzaid sorry I think I've created a new issue #1118 with my PR. |
…1118) * fix: #1116 Invalid Redirect URI in Camunda Platform 8.3.3 fixed the trimSuffix-Expression of the *IDENTITY_REDIRECT_ROOT_URL-env-variable in tasklist and operate * test: adds unit tests for trimming contextPaths --------- Co-authored-by: Jesse Simpson <[email protected]>
…1118) * fix: #1116 Invalid Redirect URI in Camunda Platform 8.3.3 fixed the trimSuffix-Expression of the *IDENTITY_REDIRECT_ROOT_URL-env-variable in tasklist and operate * test: adds unit tests for trimming contextPaths --------- Co-authored-by: Jesse Simpson <[email protected]>
Describe the issue:
The issue refers to #714 where it was already marked as fixed.
I'm trying to host a self-manged Camunda-Installation and group the following camunda-services within a url-prefix with ingress f.ex.
A snipped of my value-file looks like
When trying to login, for example, http://acme.com/operate, Keycloak shows the error Invalid parameter: redirect_uri in the browser and it's not possible to login.
The redirectUrl looks like http://acme.com/camunda/camunda/operate which is not correct ("camunda" is listed twice)
I think the problem for the operate-example is located in camunda-platform-helm/charts/camunda-platform/templates/operate/deployment.yaml L88
trimSuffix should not delete static "/operate" but the content of contextPath.
Expected behavior:
It should be possible to login into the apps normally.
How to reproduce:
Deploy any Helm chart v8.3.x with apps v8.3.x with combined Ingress enabled.
Logs:
Out of the keycloak-container
2023-12-06 07:59:21,354 WARN [org.keycloak.events] (executor-thread-20) type=LOGIN_ERROR, realmId=camunda-platform, clientId=operate, userId=null, ipAddress=10.42.0.1, error=invalid_redirect_uri, redirect_uri=http://acme.com/camunda/camunda/operate/identity-callback
Environment:
The text was updated successfully, but these errors were encountered: