You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
opencode-cloud uses **PAM (Pluggable Authentication Modules)** for authentication. Users created via `occ user add` authenticate to the opencode web UI.
350
+
opencode-cloud uses **PAM (Pluggable Authentication Modules)** for authentication.
351
+
352
+
First boot path:
353
+
- If no users are configured, startup logs print an Initial One-Time Password (IOTP).
354
+
- Extract only the IOTP quickly: `occ logs | grep -F "INITIAL ONE-TIME PASSWORD (IOTP): " | tail -n1 | sed 's/.*INITIAL ONE-TIME PASSWORD (IOTP): //'`
355
+
- Enter that IOTP in the web login page first-time setup panel.
356
+
- Complete signup (username + password) to create the first Linux user account in the container.
357
+
- The IOTP is deleted after the first successful signup.
358
+
359
+
Admin path:
360
+
- You can always create/manage users directly via `occ user add`, `occ user passwd`, and related user commands.
342
361
343
362
### Creating Users
344
363
@@ -365,14 +384,6 @@ User accounts (including password hashes and lock status) persist across contain
365
384
The CLI stores user records in a managed Docker volume mounted at `/var/lib/opencode-users` inside the container.
366
385
No plaintext passwords are stored on the host.
367
386
368
-
### Legacy Authentication Fields
369
-
370
-
The `auth_username` and `auth_password` config fields are **deprecated** and ignored. They are kept in the config schema for backward compatibility with existing deployments, but new users should be created via `occ user add` instead.
371
-
372
-
To migrate from legacy fields:
373
-
1. Create a PAM user: `occ user add <username>`
374
-
2. The legacy fields will be automatically cleared on next config save
375
-
376
387
### Rebuilding the Docker Image
377
388
378
389
When developing locally or after updating opencode-cloud, you may need to rebuild the Docker image to pick up changes in the embedded Dockerfile:
opencode-cloud uses **PAM (Pluggable Authentication Modules)** for authentication. Users created via `occ user add` authenticate to the opencode web UI.
350
+
opencode-cloud uses **PAM (Pluggable Authentication Modules)** for authentication.
351
+
352
+
First boot path:
353
+
- If no users are configured, startup logs print an Initial One-Time Password (IOTP).
354
+
- Extract only the IOTP quickly: `occ logs | grep -F "INITIAL ONE-TIME PASSWORD (IOTP): " | tail -n1 | sed 's/.*INITIAL ONE-TIME PASSWORD (IOTP): //'`
355
+
- Enter that IOTP in the web login page first-time setup panel.
356
+
- Complete signup (username + password) to create the first Linux user account in the container.
357
+
- The IOTP is deleted after the first successful signup.
358
+
359
+
Admin path:
360
+
- You can always create/manage users directly via `occ user add`, `occ user passwd`, and related user commands.
342
361
343
362
### Creating Users
344
363
@@ -365,14 +384,6 @@ User accounts (including password hashes and lock status) persist across contain
365
384
The CLI stores user records in a managed Docker volume mounted at `/var/lib/opencode-users` inside the container.
366
385
No plaintext passwords are stored on the host.
367
386
368
-
### Legacy Authentication Fields
369
-
370
-
The `auth_username` and `auth_password` config fields are **deprecated** and ignored. They are kept in the config schema for backward compatibility with existing deployments, but new users should be created via `occ user add` instead.
371
-
372
-
To migrate from legacy fields:
373
-
1. Create a PAM user: `occ user add <username>`
374
-
2. The legacy fields will be automatically cleared on next config save
375
-
376
387
### Rebuilding the Docker Image
377
388
378
389
When developing locally or after updating opencode-cloud, you may need to rebuild the Docker image to pick up changes in the embedded Dockerfile:
0 commit comments