keybase / keybase/keybase-issues
Passphrase requirements on web client when registering
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
#### Current behavior
When creating an account, the dialog shows the passphrase inputs at the bottom but without any hint as to the passphrase requirements. When the user enters an invalid passphrase, nothing happens to let them know that it's invalid.
#### What should happen instead
The passphrase requirements should be presented up front, and when the user inputs a bad passphrase the broken requirements should be highlighted or something, letting them know the reasons why the passphrase was invalid.
#### Steps to reproduce:
1. Click the invitation link (for the web client).
2. Fill out the form with a passphrase that's less than 12 characters long.
3. Press enter.
#### Workarounds
The way I got around it was by using the cli installer and creating the account from there. On the cli installer it tells the user how long the passphrase needs to be.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the web client registration dialog reached through an invitation link, and compare its passphrase validation with the CLI installer, which states the minimum length. Done means the web form presents the requirements before submission and explains which requirement fails for an invalid passphrase.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100