jakarta.ws.rs.ForbiddenException: HTTP 403 Forbidden (camunda-platform-identity)

[touch.teng]

Hi everyone,

I am facing the error in Camunda Platform Identify.
Message: 2025-07-02 04:16:34.361 ERROR 1 — [ main] i.c.i.i.k.c.KeycloakConfiguration : jakarta.ws.rs.ForbiddenException: HTTP 403 Forbidden.

Identity trying to connect to KeyCloak but having the error as above.

Regards,
Teng

[Alex_Voloshyn]

Hi @touch.teng
Can you share what IPs are assigned to Keycloak and Identity pods?

Is it from some value of the following 127.0.0.1, 10.x.x.x, 192.168.x.x, 172.16.x.x?

Regards,
Alex

[touch.teng]

Hi @Alex_Voloshyn ,

Thanks your always support. I’m not sure about IP assigned. I just follow GitHub repository in version 8.7 Helm Chart and use Argo CD to deploy to Kubernetes. There are a lot of configuration in value.yaml file.

Very appreciated if you read my value file.

values.yaml (231.1 KB)

Thanks,

[Alex_Voloshyn]

"Unfortunately, the information about assigned IPs cannot be obtained from the values file. You can retrieve it using kubectl get pods -n or by checking the ArgoCD user interface.
If for some reason, you can’t check it, you can simply try following these directions to see if they help resolve the issue: Troubleshooting Identity | Camunda 8 Docs

Regards,
Alex

[azizlol]

I got the same error when linking Camunda to Keycloak, and it was a concern about client ID or missing role in Keycloak. Make sure that the client has the correct scopes and that the endpoint token URL is correct. Once fixed, the 403 error disappeared in my house.

[touch.teng]

[quote="azizlol, post:5,

Could you please share the configuration related? I have no idea on how to check those info.