gray380
gray380
To be more specific, I have jitsi-web: https://jitsi.example.com jitsi-keycloak: https://auth-jitsi.example.com JITSI ENV: ``` ENABLE_AUTH=1 AUTH_TYPE=jwt JWT_APP_ID=jitsi JWT_APP_SECRET=supersecret TOKEN_AUTH_URL=https://auth-jitsi.example.com ``` JITSI KEYCLOAK ENV: ``` JITSI_SECRET=supersecret DEFAULT_ROOM=meeting JITSI_URL=https://jitsi.example.com JITSI_SUB=example.com ``` And at...
Seems that `jitsi-keycloak` can not get token from the `keycloak`; ``` Access to XMLHttpRequest at 'https://keycloak.test.lan/auth/realms/jitsi/protocol/openid-connect/auth?client_id=jitsi&state=841d9353-4895-4f23-80fc-61d23908c9f6&redirect_uri=http%3A%2F%2Fauth-jitsi.test.lan%2Fapi%2Fconfig%3Fauth_callback%3D1&scope=openid&response_type=code' (redirected from 'https://auth-jitsi.test.lan/api/config') from origin 'https://auth-jitsi.bank.lan' has been blocked by CORS policy: Response to...
If replace correct Web Origins URI with "*" (keycloak client's configuration) then no more 'Access-Control-Allow-Origin', but the following error has appear: ``` keycloak.js:790 POST https://keycloak.test.lan/auth/realms/jitsi/protocol/openid-connect/token net::ERR_FAILED 200 ```
Pay attention to this `rect_uri=http%3A%2F%2Fauth-jitsi.test` `http` instead of `https`
Hi, yes I do. I've tried `Web Origins` with `https://auth-jitsi.bank.lan`, with `*` and `+`. Actions log with `https://auth-jitsi.bank.lan`: login to the Keycloak ``` Access to XMLHttpRequest at 'https://keycloakdmz.test.lan/auth/realms/jitsi/protocol/openid-connect/auth?client_id=jitsi&state=bf3d4fd0-363b-47d3-a388-80d974e95c1b&redirect_uri=http%3A%2F%2Fauth-jitsi.test.lan%2Fapi%2Fconfig%3Fauth_callback%3D1&scope=openid&response_type=code' (redirected from...
BTW, if I set wrong `Web Origins` it stops at the `token` stage:  with correct settings it stops `auth?client_id` I've tried the following keycloak versions: 16.1.1, 19.0.1 (in the...
BTW  points to `config`  ``` Invalid parameter: redirect_uri ``` Update: Keycloak (16 --> 19) changes `auth/realms/{realm}/protocol/openid-connect/token` to `realms/{realm}/protocol/openid-connect/token`.