nextcloud / nextcloud/twofactor_gateway
RFE: use name from theming in authentication code message
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 122
- Forks
- 63
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 23
Description
In a world of phishers, it seems sensible to ensure the messages sent by a system are not generic, especially when we train people to be suspicious of messages. So if we can use the "name" element from the NC theming in the message sent to the user this increases its trust level.
So in the Signal message it currently reads "123654 is your Nextcloud authentication code" and with this enhancement it would read "123654 is your My Site Name authentication 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
No file or test is named in the issue. Start by locating the code that builds the Signal authentication-code message and how the Nextcloud theming name is retrieved; done means the configured name appears in that message instead of the generic product name, with existing authentication-message tests updated or added if present.
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