Should `GenerateParameterDefault` regenerate if stored value no longer meets complexity requirements?
Open
area-app-model
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
I was using `GenerateParameterDefault` earlier today, and after messing up the initial configuration, I needed to increase the complexity, but my change was being ignored as the previous value had been persisted to user secrets.
If an existing password no longer meets the complexity requirements configured on `GenerateParameterDefault`, should the parameter value get re-generated (and re-persisted)?
Contributor guide
Assessment
This issue has not been assessed yet.