-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Endpoint for jitsi tokenAuthUrl #207
Comments
@givors-anabasis Should the MM server act as the JWT provider or another service? |
@hanzei My thought was that when the MM jitsi plugin was configured to be a JWT provider, then it would be natural to also be able to use it as a JWT provider for this use-case (since MM jitsi knows the app secret and id and provides the well formed valid JWT). No need to use any external service. |
@givors-anabasis I trying work on this issue. Is there any jwt or other message that send to callback from jitsi? |
@catalintomai @hanzei @givors-anabasis is 6) possible. I am not aware of any features that allow us to do the same. I had a call with @lufty-demansol and this is the part we couldn't figure out. |
@maisnamraju I'm not sure about 6), If one try to access some plugin url without being logged to Mattermost, won't Mattermost ask the user to log in first? Anyway, this was a proposal, if the other points are implemented, it's really nice! (thank you @dimashasbi) |
Mattermost Version: 6.3
Plugin Version: 2.0.0
Describe the issue
There is no way to "login" as Host on an already existing jitsi room.
Additional context
Jitsi offers mechanism to ask to an authentication service for a JWT to connect to a room. As described here: jitsi/jitsi-meet#728
The mechanism works as follow:
https://instance.jitsi/room
where authentication is required to host a room, and the user is not identifiedhttps://instance.mattermost/plugins/jitsi/auth-callback?room={room}&roleUpgrade={roleUpgrade}
, where{room}
and{roleUpgrade}
are replaced with the room's name and a flag set tofalse
.auth-callback
endpoint checks whether the user is identified (some other criterion could be used too, should anyone logged have the right to join any room?)auth-callback
redirects the user tohttps://instance.jitsi/room?jwt=valid_token
Notice that the callback can be called with
roleUpgrade=true
, in that case, it shouldn't redirect back to the room, but only return the JWT. This seems to be used when a user asks for a promotion to moderator.The text was updated successfully, but these errors were encountered: