[Task] Do not need consent for app websocket
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
What should be done
In the OAuth flow we first ask the user to login and then to consent for the asked scopes.
For external Lenra clients, the only scope asked for is app:websocket that does not really give access to user information.
To give a better user experience to our users we will skip the consent page when the only asked scope is app:websocket.
Technical recommandation
See if Hydra manages skipping consent in the acceptation of the connection.
If not we can validate the consent when loading the consent page, but it's not the best solution.
Contributor guide
No contributing guide indexed for this repository
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 tracing the OAuth connection-acceptance and consent-page flow, then check whether Hydra can skip consent when the sole scope is app:websocket. Done means external Lenra clients with only that scope bypass consent while other scopes retain consent; the issue names no files or tests, so locate those entry points first.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100