Authenticate pangolin-client with machine credentials #62
Loading…
Reference in a new issue
No description provided.
Delete branch "pangolin-client-machine-auth"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Authenticate pangolin-client with machine credentials
Replace the one-time interactive pangolin login with machine-client
credentials (RAZER_MACHINE_*), ending all login state in containers.
Machine access is per-resource in the dashboard: a machine has no role
or standing permission, so for each private resource it needs, it must
be added to that resource's Machine Clients list. Without any grant
the client connects but no tunnel peer forms, and --org is a
user-session flag machines must never take (USER_ID_NOT_FOUND). The
interactive login this replaces died in the working tree: a fresh
clone of the fleet repo erased pangolin-client-config and crash-looped
the agent. Beelink and tower need the same compose change and their
machine credentials wired (keys already in .env).