hey, i am tying to connect oidc using azure and keycloak, after setting up everything i am redirected to the login page in azure finishing successfully ( according to azure) but then when redirecting back to my local frontend it looks like it fails and retry several times , and in the frontend logs i see

2023-03-08 13:37:28,465 [application-akka.actor.default-dispatcher-13] ERROR o.p.core.engine.DefaultCallbackLogic - Unable to renew the session. The session store may not support this feature

Hi @nice-river-27843 what’s your version and deployment method

hey, deployment method is k8s + we are using postgres. we took the latest from git ( v0.10.0) . we read previous posts but nothing helped

just curious if your keycloak client callback settings was updated between quickstart and helm deployment?

2023-03-08 13:37:28,465 [application-akka.actor.default-dispatcher-13] ERROR o.p.core.engine.DefaultCallbackLogic - Unable to renew the session. The session store may not support this feature

I don't think this line is the cause of the issue though

hey @better-orange-49102, in both cases it redirects to localhost:9092 ( didn’t change anything there ). i am running on local k8s cluster so it doesn’t need to be changed as far as i understand. please correct me if i am wrong.

other than port 9002, I can't think of anything else to check, unfortunately. (you're running frontend in port 9092?) Also im not using local k8s cluster

sorry 9002 🙂

The helm deployment process has some signficant changes from docker- have you reviewed the docs here? https://datahubproject.io/docs/deploy/kubernetes

yeah covered everything here, actually it works as expected if i am working without OIDC auth.

Let’s see if @big-carpet-38439 can help you out here!

can we get the rest of the configs you are using?

hey, yeah redirecting works when OIDC disabled