[glkvm 2.0.0] admin user

[NeoXTof]

Hello,

I've installed today version 2.0.0 (fresh install as suggested, docker on x64 target). I created a new admin user (with a username matching one OIDC user). I then removed the default admin user.

But each time I'm recreating or restarting the stack, the default user admin is automatically recreated.

 2026-02-24T09:00:07Z |INFO| ==============================
[glkvm_cloud] 2026-02-24T09:00:07.602726411Z 2026-02-24T09:00:07Z |INFO| SslCert: /home/certificate/glkvm_cer,SslKey: /home/certificate/glkvm_key
[glkvm_cloud] 2026-02-24T09:00:07.605339245Z 2026-02-24T09:00:07Z |INFO| Listen http proxy on: [::]:10443
[glkvm_cloud] 2026-02-24T09:00:07.605506158Z 2026-02-24T09:00:07Z |INFO| Listen devices on: [::]:5912
[glkvm_cloud] 2026-02-24T09:00:07.954328735Z 
[glkvm_cloud] 2026-02-24T09:00:07.954416406Z 2026/02/24 09:00:07 /opt/work/golang/src/glkvm-cloud-both/glkvm-cloud/internal/server/api.go:129
[glkvm_cloud] 2026-02-24T09:00:07.954463017Z [9.313ms] [rows:1] INSERT INTO users (username, description, password_hash, role, status, is_system)
[glkvm_cloud] 2026-02-24T09:00:07.954497678Z          VALUES ('admin', 'Admin', "$2a$12$dY7/tFLgVSu5/m8nGBLviOheTItbZhrAMT3ZsxEI4h6Aln4obwP2G", 'admin', 'active', 1)
[glkvm_cloud] 2026-02-24T09:00:07.954523788Z          ON CONFLICT(username) DO UPDATE SET
[glkvm_cloud] 2026-02-24T09:00:07.954544468Z            password_hash=excluded.password_hash,
[glkvm_cloud] 2026-02-24T09:00:07.954560979Z            role='admin',
[glkvm_cloud] 2026-02-24T09:00:07.954577429Z            status='active',
[glkvm_cloud] 2026-02-24T09:00:07.954592519Z            is_system=1
[glkvm_cloud] 2026-02-24T09:00:07.997414283Z 2026-02-24T09:00:07Z |INFO| Listen users on: [::]:11443

is it possible to avoid doing this if there is already one admin created and active ?

[iclannad]

@NeoXTof In the current version, the built-in admin user is not allowed to be deleted.

From the system’s perspective, removing the system administrator is not a supported or safe operation.
At the moment, the only supported way to change the admin credentials is via the environment variables in the deployment configuration.

We plan to improve the handling of username conflicts between OIDC/LDAP and local accounts in upcoming releases.

[NeoXTof]

@iclannad as I defined another system admin, I don't see a problem to remove the default one. I configured the password for the admin in my .env but I did not find how to change the default "admin" name (it's too generic and known to be considered safe to use)

I'll roll back to 1.9.0 and wait for updates then.

[iclannad]

@NeoXTof In the next release, you’ll be able to customize the default admin username via env config instead of being forced to use admin.

[NeoXTof]

@iclannad perfect, I'm waiting for the next release to test it then

[iclannad]

@NeoXTof This feature has been released in v2.1.0, please check the release here: https://github.com/gl-inet/glkvm-cloud/releases/tag/v2.1.0

[NeoXTof]

@iclannad I tried the 2.1.0. It works but I have to erase the db becuse there was a conflict of username and I could not delete the user created in 2.0.0