-
-
Notifications
You must be signed in to change notification settings - Fork 673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.5.4 doesn't relate to credential recovery #2394
Comments
V2 is "do authentication correctly". If default credentials are used, from V2 perspective it is handled correctly. For me it is a V14 issue. Not a perfect match, but V14.1 deploy is dealing with "do not put test-code", "debug modes", "demo functionality" etc to the production. But this is just the first idea, does not give "let's go for the PR" feeling. |
@jmanico @ryarmst @randomstuff any thoughts on this? |
This is more user policy than general authN so I agree v14 seems better. |
I do not find it shocking to find it in V2. V14 is probably OK as well. |
V14 seems like a fine fit. |
V14.1 gives me the best vibes here, opened PR #2403 |
We have spoken about this requirement before but bottom line is that this doesn't seem to belong in "Credential Recovery"
I think we have a few potential target locations:
What do people think? @elarlang
The text was updated successfully, but these errors were encountered: