Initial Password Change (Required at Commissioning)
Immediately after installation, Edge gateways come with the same default account for every installation. Be sure to change this before handing the system over to the field.
For the broader topic of periodic replacement and key rotation during operation, see Password · API Key Change. This page deals only with what you do once, right after installation.
What to Change
| Key | What | Default |
|---|---|---|
edge.admin_password | UI login password (username is fixed at admin) | admin123! |
edge.rest.api.key | REST API call key | Different per installation |
mqtt.server.password | MQTT account for sending to the upper platform | Different per installation |
Edge has only one user account: admin. It is not structured to assign separate accounts per person,
so anyone who knows this password can access the gateway.
How to Change
Change them using bin/config.sh. Change several at once and 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 were versions that wrote to a compatibility path rather than the authoritative config file. The change appears to have worked, but it was not actually applied. Always verify as shown below — for the exact version conditions, see Password · API Key Change.
Infrastructure Accounts and API Keys
In addition to the three above, Edge holds more keys. Go through them all at commissioning —
change them with 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 (for Sparkplug 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 installation |
ai.api.key | AI feature key | Left empty |
tse.server.password does not appear on the screenThe first six appear in the environment configuration screen (/ui/system/config), but the TSE password does not appear there. Change it via the configuration file or config.sh only.
For server.api_key and ai.api.key, you must also change them on the counterpart side — obtain the platform-side token and the AI gateway key, and match them accordingly.
Verification After Changing
# 1. 파일에 실제로 들어갔는가
grep '^edge.admin_password' /etc/kopens/conf/app.properties
# 2. 옛 비밀번호로 로그인이 막히는가 — 브라우저에서 직접
Login with admin123! must fail. If it succeeds, either the restart wasn't done or the value wasn't applied.
On the configuration screen (/ui/system/config), edge.admin_password is masked without an eye icon, so its value is not visible. Use config.sh --get above to see the current value.
Related Documentation
- Password · API Key Change — full rotation details,
config.sh - Post-Installation Inspection — first-time user setup overall
- app.properties Reference — key list