Support for jwt per room feature like in jitsi meet ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- erlang
- Domain
- authentication, backend
Research direction
Start by reading lib-jitsi-meet's doc/tokens.md and the referenced jitsi-meet resources/prosody-plugins to understand the per-room JWT behavior. Compare that behavior with ejabberd's existing authentication and room handling; done means the Jitsi Meet use case works without a custom plugin, with the relevant behavior documented and tested.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Hello, i discovered some day ago that jitsi meet could be runned with ejabberd (https://blog.jabberhead.tk/2020/03/16/install-jitsi-meet-alongside-ejabberd/). I found the idea of jitsi meet just some component added to an existing xmpp server reallly nice. Jitsi meet is currently more a "all in one software" than just an external feature for xmpp.
As i read the article there seems to be only packaging and documentation issue to handle a better support.
In fact, that's not totally true. Jitsi meet made a tweak on prosody to handle per room access with jwt, see https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/tokens.md.
As far i read, we can't do that now on ejabberd. As the feature make sense in some context, it may be interesting to have way to make it work too in ejabberd without specific homemade plugin tweaking, for the jitsi meet usecase but not only.
Describe the solution you'd like
Make jwt auth per room feature of jitsi meet work with ejabberd.
Describe alternatives you've considered
Another solution may be some adaptation from jitsi-meet side. I'm not sure the way they tweak prosody is the "good way" to do. But it's working.
Additional context
Here are the customs plugins that prosody that jitsi meet team do create :https://github.com/jitsi/jitsi-meet/tree/master/resources/prosody-plugins . others plugins looks really specific to jitsi use case so i don't think there are important feature to support.
- Dominant language
- Erlang
- Stars
- 6.7k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from processone/ejabberd
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
processone/ejabberd#4597 ·
-
API permissions Open
processone/ejabberd#4619 · 3 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
processone/ejabberd#4616 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
processone/ejabberd#4614 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
processone/ejabberd#4613 · 1 comment ·
All issues in processone/ejabberd
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sisaku-security/sisakulint#647 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yunaremaia/driftcheck#246 ·
-
Docs say approvals.mode defaults to smart, but code falls back to manual when the key is absent Openarea/config comp/tools P2 sweeper:risk-compatibility type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#117341 · 1 comment ·
-
bug good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yunaremaia/taintrace#110 ·