cloudfoundry / cloudfoundry/stratos
Distinguish between stratos login and endpoint register username field.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
This is really minor.
When registering a new endpoint and using the same username for both (admin, as an example), password managers want to override the stratos login credentials with the registered endpoint credentials.
I would imaging it's something to do to with the name given to the username field in both forms clashing with each other. This would also improve browser auto-complete.
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
Compare the Stratos login and endpoint registration forms, focusing on the username field names and browser autocomplete behavior. The work is done when password managers distinguish the two credential sets and autocomplete no longer offers endpoint credentials for the Stratos login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100