Client Authentication

Client auth is cookie-JWT based, with token stored locally in ~/.config/cookiefarm/session.

Login

ckc login -u <username> -P <password> [-H <host>] [-p <port>]

Example:

ckc login -u team01 -P SuperSecret -H 127.0.0.1 -p 8080

What it does:

1. if -H/-p are given, updates and persists local config (client.yml) with the new host/port
2. logs in through /api/v1/auth/login
3. stores session token
4. fetches shared config and writes shared.yml

Logout

ckc logout

Removes local session file.

Show current config

ckc config show

Common Errors

• Login failed: wrong password or server unreachable.
• shared configuration has changed: run login again (ckc login -u <user> -P <password>) to resync shared.yml.