Skip to main content

Change Initial Password (Commissioning Required)

After installation, Studio creates one bootstrap administrator account. Since every installation uses the same credentials, you must change them before handing the system over to the field.

ItemValue
Usernameadmin
Passwordadmin123!
Created only when the user table is empty

This account is seeded only on first startup when no users exist. If you have already created accounts on an installation, a new one will not be generated. Therefore, restarting the system does not restore the default password.

How to change it — from the interface​

This is the easiest path. After logging in to Studio:

  1. Open the gear icon Settings → User Management in the lower left.
  2. Reset the password for the admin account.

If you have multiple operators, take this opportunity to create individual accounts for each person and keep the shared admin for administrators only.

Cannot be changed on the server​

The Studio administrator account is managed by the app. There is no reset path on the server side.

Editing .env has no effect

The server checks in this order when logging in: ① database → ② environment variables. Once an account is found in the database, it stops there, so changing .env is a dead value. Be especially careful—you may believe you changed something when you did not.

Not managed by bin/passwd.sh

What passwd.sh manages is database accounts and API keys. App login accounts are not on that list, and if you try to set them there, they are rejected just like a typo → Change Password · API Keys.

⇒ If you lose the administrator password, you must log in with another administrator account to reset it. In installations with only one administrator, losing that account is difficult to recover from. We recommend creating two or more administrator accounts during commissioning.

Infrastructure accounts and API keys​

Unlike app login accounts, database accounts and API keys are changed with bin/passwd.sh.

cd /opt/kopens/plantpulse-studio/bin

./passwd.sh --list          # 무엇을 바꿀 수 있는지 (현재값은 마스킹)
./passwd.sh --list --show   # 현재값 전체
./passwd.sh PG_PASSWORD     # 값은 프롬프트로 입력
KeyWhatWhere
PG_PASSWORDBundled PostgreSQL (PG_USER account)Change the DB account itself with ALTER ROLE
ANTHROPIC_API_KEYAnthropic key.env — loaded when agent-server starts
AI_API_KEYOpenAI-compatible key.env — loaded when agent-server starts
Do not paste the value on the command line

It remains in ps output and shell history. Omitting the value and entering it at the prompt is the recommended path.

Platform's PP_* is not on this list

Only those owned by Studio appear here. Platform passwords are not owned by Studio, so if you try to set them there, they are rejected just like a typo — change them in Platform Credential Rotation.

Other things to check​

Studio uses multiple keys beyond passwords. Review them all during commissioning.

TargetWhere
Platform · AI · Git · registry keysSecret Management
Key rotation procedure (bin/passwd.sh)Change Password · API Keys
PostgreSQL passwordInstallation — you must keep the value you set initially

Verification​

Log out and verify that login with admin123! fails. If it succeeds, the password was not changed.