Allow for additional fields in JWT token to enable the use lobby if not authenticated
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
To enable the use of Jitsi/Prosody plugins like token_lobby_bypass (https://github.com/jitsi-contrib/prosody-plugins/tree/main/token_lobby_bypass) some more fields in the JWT should be configurable.
In the case of token_lobby_bypass the token element context.user.lobby_bypass should be set to true if the user is authenticated in NextCloud. In this case the user does not have to wait in the Jitsi lobby e.g. when the prosody plugin lobby_autostart ist active.
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.
Research direction
Start by locating where this JavaScript integration creates and configures JWT tokens, then compare the current token contents with the token_lobby_bypass plugin requirements. Done means allowing additional configurable fields and supporting context.user.lobby_bypass=true for authenticated Nextcloud users; no test or file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100