Change Default Password (Commissioning Required)
Immediately after installation, every Edge gateway instance shares the same default account. You must change it before handing the device over to the field.
For routine rotation and key management during operation, see Password · API Key Changes. This page covers one-time setup right after installation only.
What to change
| Key | What | Default |
|---|---|---|
edge.admin_password | UI login password (username is admin fixed) | admin123! |
edge.rest.api.key | REST API call key | Unique per instance |
mqtt.server.password | MQTT account for upstream Platform | Unique per instance |
Edge has only admin user account. There is no per-person account structure, so
whoever knows this password can access the gateway.
How to change
Change via bin/config.sh. Batch all changes at once, then restart only once at the end.
cd /opt/kopens/plantpulse-edge/bin
./config.sh --get edge.admin_password # 현재 값 확인
./config.sh --set edge.admin_password '<new-password>'
./config.sh --set edge.rest.api.key '<new-key>'
./config.sh --set mqtt.server.password '<new-password>'
./config.sh --diff # 직전 백업과 비교 — 의도한 것만 바뀌었는지
./config.sh --restart # 마지막에 한 번만
config.sh --set versions silently lose valuesThere was a version that wrote to a compatibility path instead of the canonical file. It shows as changed but does not actually take effect. Verify it below — see Password · API Key Changes for detailed version conditions.
Infrastructure accounts and API keys
Edge holds additional keys beyond those three. Sweep through them all during commissioning —
change them using the same config.sh --set and restart only once at the end.
| Key | What | Initial value |
|---|---|---|
edge.admin_password | UI login password (admin) | admin123! |
edge.rest.api.key | REST API authentication key (X-API-Key / Bearer) | Fixed default |
mqtt.server.password | Built-in HiveMQ broker (Sparkplug B transmission) | edge123! |
opc.ua.server.password | OPC UA server (northbound) | edge123! |
tse.server.password | Built-in time series engine (TSE) | tse123! |
server.api_key | Platform integration token | Injected at install |
ai.api.key | AI feature key | Empty |
tse.server.password is not on screenThe first six appear in the settings UI (/ui/system/config), but the TSE password has no screen interface
and is changed via config file or config.sh only.
server.api_key and ai.api.key must also be rotated on the peer side — obtain fresh Platform tokens and
AI gateway keys from the counterpart and sync them.
Verification after change
# 1. 파일에 실제로 들어갔는가
grep '^edge.admin_password' /etc/kopens/conf/app.properties
# 2. 옛 비밀번호로 로그인이 막히는가 — 브라우저에서 직접
Login with admin123! must fail. If it succeeds, the restart did not complete or the value was not applied.
In the settings screen (/ui/system/config), edge.admin_password fields are masked without an eye icon so
the value never shows. To see the current value, use config.sh --get above.
Related documentation
- Password · API Key Changes — Full rotation procedures,
config.shdetails - Post-Installation Checklist — Complete first-user setup
- app.properties Guide — Key reference