nextcloud / nextcloud/twofactor_nextcloud_notification
Enable check
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 34
- Forks
- 13
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 67
Description
As mentioned by @tobiasKaminsky
Maybe it would make sense to force a notification acceptance from a device other than a browser. So either mobile device (IOS/Android) or the desktop client. At least not the same browser as we are working from.
That way we verify people at least at that point have access to a second device.
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
The issue names no files, tests, or entry points, so start by tracing the existing notification acceptance flow and how it identifies the approving device. Done means acceptance is rejected from the same browser and remains possible from a separate iOS, Android, or desktop client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100