-
Notifications
You must be signed in to change notification settings - Fork 274
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
[META] Admin user should have a custom non-hardcoded password #3622
Comments
github-actions
bot
added
the
untriaged
Require the attention of the repository maintainers and may need to be prioritized
label
Oct 30, 2023
[Triage] This is the last of the meta issues tracking progress removing the use of default credentials in the cluster. Marking as triaged given clear action items and exit criteria. |
stephen-crawford
added
triaged
Issues labeled as 'Triaged' have been reviewed and are deemed actionable.
and removed
untriaged
Require the attention of the repository maintainers and may need to be prioritized
labels
Oct 30, 2023
23 tasks
2 tasks
Closing this as all sub-tasks are now complete. |
5 tasks
32 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
High-level Idea
As one of the outcome of this spike, this feature-request is to replace admin password, which is currently hard coded in demo configuration, with a custom password. If none is provided, a random password should be generated and set for admin user. Here is the intended design:
Acceptance Criteria
- [ ] If no custom password is provided, the script should generate a new one, set it for admin and let the end user know(no longer considered)Exit Criteria
install_demo_configuration
script to a standalone Java Tool #3633Would like
The text was updated successfully, but these errors were encountered: