Authentication
The daemon's HTTP authentication surface (/auth/*) and the
JWT issuance / refresh / revocation flows are not part of the
public documentation contract.
Public clients should use the SDK or CLI to obtain and refresh tokens automatically. Manual token handling is not recommended.
| Need | Use |
|---|---|
| Log in from the terminal | digitorn login (CLI) |
| Check who you're signed in as | digitorn whoami (CLI) |
| Pair a daemon with a hosted Digitorn account | Via cloud pairing config |
For direct HTTP integration outside of the SDKs, contact your daemon administrator.
Install visibility, not "scope"
There's no per-user "scope" that installs a private copy of an app for each user. Who can see and run an app is a debug/production visibility state, tied to who installed it - see Install visibility.