We have deployed the GD.CN with DEX after sucessfull installation we are able to bootstrap users,workspaces via cli . However UI login screen throwing the bad request
Kindly help us how to fix / add callbacks !
Best answer by Robert MouchaView original
the redirect_url has wrong schema (http instead of https). This error is caused by the fact the Ingress controller doesn’t pass X-Forwarded-* headers from upstream load balancer to application.
Please add the following annotations to ingress-nginx service helm chart (using values-ingress.yaml file) and perform rollout restart of ingress-nginx deployment:
Especially the “use-forwarded-headers” is very important.
Reapply the ingress-nginx helm chart with these updated values file and restart ingress-nginx deployment using “kubectl rollout restart deployment ...” command.
Then, delete your organization using “kubectl -n gooddata-cn delete org <<your-organization-name>>” and recreate it again with the original definition. This command will reconfigure Dex Oauth2 client with a correct redirect_url.
Dex user will be preserved, but you’ll need to recreate user mapping to organization as described here, with the same authenticationId as before.
@Robert Moucha Thanks for the response, However issue is not resolved I have followed all the above mentioned steps and alos tried with fresh new installation did’nt help same k8 cluster.
-- values-ingress.yaml --
Ah, my bad . I misplaced the configuration options I advised to a different section. These three (proxy-buffer-size, client-body-buffer-size, and use-forwarded-headers) do NOT belong to controller.service.annotations, but to controller.config.
So the correct structure is:
I’m very sorry.
Thanks for support Robert 👍