Bridge Tokens
Create, copy and revoke the access tokens the Ableton Live bridge uses to connect as you.
The Live bridge runs outside the browser, so it cannot use your normal signed-in session. It authenticates with a bridge token instead — a long-lived credential you create, paste into the bridge's config, and revoke when you no longer need it.
Tokens are managed from Settings → Bridge.
Creating a token
Create a token from the settings page and it is displayed once, at the moment of creation. Copy it then.
The server never stores the token itself, only a cryptographic hash of it. That means nobody — including the Jam Club operators — can retrieve or display your token again afterwards. If you lose it, the fix is to revoke it and create a new one.
Using a token
The settings page gives you a ready-made configuration snippet to paste into the bridge's config file at ~/.fluento/config. That is the whole setup: the bridge reads the token from there and connects as you.
Revoking a token
Revoke a token from the same page and it stops working immediately. Do this if:
- You are no longer using the bridge on a given machine.
- You pasted a token somewhere it should not have gone.
- You are handing a machine to somebody else.
Revoking one token has no effect on any others, so you can safely run several — one per machine — and retire them individually.
Warning: A bridge token acts on your behalf. Treat it like a password: do not commit it to a repository, paste it into a shared document, or include it in a screenshot.
Good practice
Create a separate token per machine rather than reusing one everywhere. It costs nothing, and it means losing a laptop is a single revocation rather than a scramble to re-key everything you own.