Platform features are currently in invite-only beta. You can
sign up here if you want to be considered for one of our next
phases. The open source CLI, the compiler and the standalone generator are not part of the beta
and are available now. Creating a key
On your instance, open your avatar menu and choose Personal Access Keys. The secret is shown
once, at creation.
Keys are managed under /api/me/access-keys:
A token is a dotted string with a fixed, scannable prefix.
The prefix exists so a leaked credential is recognisable to a secret scanner on sight. The key id
is separate from the secret so a key can be identified in a log or an audit entry without the log
holding anything usable.
An exchange token additionally encodes the instance address and tenant. That is a convenience for
cordango login, not an authority: the address inside a token is a claim the server confirms. See
Publishing.
What a key can do
A key acts as you. It carries your relationships and the roles those grant, so it can reach exactly
what you can reach and nothing else.
cordango logout forgets a credential on the machine it is run on. It does not revoke it. To make
a key stop working everywhere, delete it on the instance.
