Authorization modes

Targets support two authorization modes.

Hosted Brokerr gateway

The public Brokerr gateway supplies provider application credentials. You approve access in the provider, then your instance stores the resulting token locally.

Choose hosted mode for the simplest setup. The gateway is needed for new connections and some token refreshes, but it does not keep your media data.

Custom OAuth application

You create an application at the provider and enter its client ID, secret, and callback details. Choose this mode when you do not want to depend on the hosted gateway.

Choose custom mode when you require independence from the hosted gateway or need provider quotas isolated to your own application.

Changing mode disconnects the target. Save, reconnect, then run Test connection.

Tokens are encrypted in the local database. Brokerr refreshes them when the provider supports refresh tokens; otherwise reconnect when requested.

Authorization mode is selected independently for every target instance.