oxidecomputer / oxidecomputer/omicron
review password policy
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
We should decide if we want the public API to enforce any particular policy regarding password security (e.g., minimum length, characters used, etc.). I have no particular opinion on this but it seems like something we should decide explicitly before MVP.
References:
https://github.com/oxidecomputer/omicron/blob/9d1bd5539225b6a225ba3655ceab852c71baa04a/nexus/types/src/external_api/params.rs#L223-L225
https://github.com/oxidecomputer/omicron/blob/9d1bd5539225b6a225ba3655ceab852c71baa04a/nexus/types/src/external_api/params.rs#L252-L253
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
Start by reviewing the referenced sections of nexus/types/src/external_api/params.rs around lines 223-225 and 252-253, then trace how password input is handled in the public API. Done means reaching and recording an explicit password-policy decision, along with the implementation scope it requires.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100