nextcloud / nextcloud/twofactor_gateway
Disabling second factor does not ask for confirmation
Open
Nobody has claimed this yet.
bug
gateway:signal
gateway:sms
gateway:telegram
- Dominant language
- PHP
- Stars
- 122
- Forks
- 63
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 23
Description
Just tried the thing using Signal and it's awsome, just works straight away.
Just a hint, disabling the second factor should probably ask for one last confirmation code ;)
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 or tests. Start by tracing the second-factor disable flow and how confirmation codes are handled; done means disabling the factor requires one final confirmation code, with coverage for this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100