Any fix for this issue?
We are also facing the exact same issue, the only difference being that we are using our own GENERIC OIDC instead of keycloak.
Hi @chirag - as I mentioned, I am unable to replicate the issue, so Iām not exactly sure what the issue might be yet. Have you inspected the JWT to see what it contains? Can you share that here?
Hey Nathan,
Got to know the fix for this. We had to pass CORS configuration in identity.
- name: IDENTITY_CORS_ALLOWED_ORIGIN_PATTERNS
value: "*domain.com"
- name: IDENTITY_CORS_ALLOWED_METHODS
value: "GET,POST,PUT,OPTIONS,DELETE,PATCH"
The error message is a bit misleading which makes you think it has something to do with permissions.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.