Account keys
How a node sees the traveller instead of the hub.
Updated 2026-10-15
After sign-in Asembla sends two things on every call: the hub's shared key, which proves the call came through Asembla, and the traveller's own account key in the header the node declared.
- Keys are stored encrypted on the passport.
- If a node answers 401 or 403, Asembla signs in again once and repeats the action.
- If a password is refused, Asembla stops trying it and asks for a working one or a key.
Was this helpful? No — ask support
Still stuck? Ask support.