Issue with external authentication with JWT with latest build
See original GitHub issueHello,
Sorry if I missed some patch notes or something! I recently set up Keycloak with jitsi-meet and this was working with jitsi/web:stable-5390-3
(the latest build at the time). I am running everything in docker. If I attempted to start a meeting without authenticating, it would redirect me to my Keycloak app to authenticate first.
I am using the following env variables:
ENABLE_AUTH=1
ENABLE_GUESTS=1
AUTH_TYPE=jwt
JWT_APP_ID=myId
JWT_APP_SECRET=mySecret
TOKEN_AUTH_URL=https://auth.mysite.com/{room}
However, the latest update broke that integration. No matter what I do, it seems to authenticate internally. Is there something I am missing?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
JWT authentication: Best practices and when to use it
Learn how to best use JWT to trust requests by using signatures, exchanging information between parties, and preventing basic security ...
Read more >External Authentication supports Json Web Tokens (JWT) #68
Ambassador needs to support Json Web Token ("JWT") an an authentication mechanism. Information we need to collect: Which algorithms?
Read more >Issue with ImpersonateTenant after implementing external ...
We have a Blazor server application where we did implement external login. To do so, we did create a method that create us...
Read more >Implementing JWT Authentication in ASP.NET Core 5
JWT authentication is a standard way for protecting APIs - it's adept at verifying the data that's transmitted over the wire between APIs ......
Read more >Asp.core JWT and external authentication - Stack Overflow
I'm in a scenario where there is a Blazor app that has to be protected. This app need a login on local user...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sure, here are the steps I took:
public
client and I didn’t set a root URL for the client app but I did set the base URL to the Keycloak address. In my case, it washttps://auth.mysite.com/
.jitsi-keycloak
to act as an intermediary to perform the OAuth redirects: https://github.com/D3473R/jitsi-keycloak. I also used the docker image here with environment variables. The address for this washttps://portal.mysite.com/
. I followed the steps exactly as it was written. The only difference here was I setTOKEN_AUTH_URL
to be the portal site:https://portal.mysite.com/{room}
. I also gotkeycloak.json
fromClients > myClient > Installation > Keycloak OIDC JSON
. This gets mounted to/config
in the image.You may have to tweak the address in the JSON file.
Valid Redirect URIs
under the client that you just created with the URI for the portal:https://portal.mysite.com/*
.Web Origins
to either*
or+
. In order to use this for security reasons, you will have to addweb-origins
as one of the default client scopes for the client in Keycloak.The
keycloak.json
config file should letkeycloak-jitsi
know where the auth server is and all the environment variables should connect the portal and jitsi.I hope this was clear enough!
Thanks a lot!