UNIAC_PLATFORM_URL
selects the platform API origin for auth login and auth token, with
https://api.uniac.ai as the default.
Sign-in
login obtains a token through browser sign-in, where account creation is
also available. Sign-in requires user interaction. The CLI prints the sign-in
URL and reports the browser-launch attempt.
Without
--manual, login receives the redirect through a listener on a random
localhost port and waits up to five minutes. The default platform uses
uniac.ai for sign-in. Another platform requires an explicit --host or
UNIAC_AUTH_HOST; the CLI does not infer a website from the platform origin.
Successful sign-in stores the returned token in ~/.uniac/auth.json, with
file permissions 0600. There is one stored session per platform; signing
in replaces that platform’s session and preserves the others. The CLI does
not validate the token with the platform API before storing it.
Credential selection and renewal
project create, link, deploy, status and auth token use a nonempty
UNIAC_ACCESS_TOKEN first, otherwise the stored session for the platform they
address. The environment override receives no local expiry check. A stored
token becomes unusable 60 seconds before its recorded expiry.
The CLI does not refresh tokens automatically. Another auth login obtains
and stores the token returned by sign-in; it does not guarantee a different
token or a later expiry.
Stored sessions
auth status reads local storage only. Its Logged in. message means stored
sessions exist; it neither checks them with the platform nor inspects
UNIAC_ACCESS_TOKEN. Logout does not clear that environment variable or
revoke tokens at the platform.
uniac auth -h lists subcommands; each subcommand’s -h prints its usage.
status, token and logout accept no flags or arguments. Help and invalid
invocations perform no authentication operation. Only login uses the
network.