Sign in to CliqHub
Signs the daemon in to CliqHub with a username and password or a personal token, and
settles which realm it belongs to. Send credentials to sign in; send only realm
(with or without confirm_switch) to finish a realm choice with the sign-in already stored.
What happens to the realm:
- Already enrolled: it stays in its realm. Asking for another realm is refused unless
cliqd runs with
--allow-realm-override; then the first call lists the teams that would be removed (switch_requires_confirm) and a second call withconfirm_switch: truemoves it. - New daemon, one realm (or
realmgiven): it enrolls there. If it already has teams or runs made offline, the first call lists them (enroll_requires_confirm) and nothing changes until you confirm. - New daemon, several realms, no
realm:needs_realm_choice; call again withrealm.
A refused sign-in stores nothing and ends the session it opened on CliqHub. Moving realm is refused while runs are going or work for the old realm has not synced.
From the CLI: cliq login.
No credential is needed from this machine. From another host, send Authorization: Bearer with a dispatch token CliqHub signed for this daemon or a cliq_tok_… personal token of a user in the daemon’s realm; this only works once the daemon is connected to CliqHub. See Authentication.
Authorizations
Not needed from the same machine. From another host: a dispatch JWT CliqHub signed for this daemon, or a cliq_tok_… personal token whose user is in the daemon's realm.
Body
Provider credentials (username+password, or a user PAT as token); omit to reuse the stored session
Realm to enroll in / switch to (org.slug); omit to keep the current one or get the list to choose from
1Confirm the realm change: moving an enrolled daemon (needs --allow-realm-override) after seeing teams_to_remove, or enrolling with local teams/runs after seeing enroll_requires_confirm