Originally created by @b- on GitHub (Jan 24, 2025).
It would be super helpful if I could programmatically define the initial admin user for Komodo Core via the value of a file, or some other kind of secret. Perhaps a command can create a hash for a password, and then you can supply a username and password in the config?
This way registration doesn't have to ever be enabled
Originally created by @b- on GitHub (Jan 24, 2025).
It would be super helpful if I could programmatically define the initial admin user for Komodo Core via the value of a file, or some other kind of secret. Perhaps a command can create a hash for a password, and then you can supply a username and password in the config?
This way registration doesn't have to ever be enabled
Now available starting 1.19.0, but its just simple, and the intention is for admin to change it after logging in first time from the UI.
@mbecker20 commented on GitHub (Aug 26, 2025):
Now available starting 1.19.0, but its just simple, and the intention is for admin to change it after logging in first time from the UI.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @b- on GitHub (Jan 24, 2025).
It would be super helpful if I could programmatically define the initial admin user for Komodo Core via the value of a file, or some other kind of secret. Perhaps a command can create a hash for a password, and then you can supply a username and password in the config?
This way registration doesn't have to ever be enabled
@mbecker20 commented on GitHub (Aug 26, 2025):
Now available starting 1.19.0, but its just simple, and the intention is for admin to change it after logging in first time from the UI.