Transposit stores authentication in the form of Keys and Keychains. For a high-level explanation, read about how we've designed managed authentication in Transposit.
Transposit supports several authorization mechanisms including OAuth, auth via headers, username/password, and a few less common options such as WSDL auth and OAuth v1. When you enter credentials or complete an OAuth flow, Transposit securely stores them for future use as a key. Each Transposit application has its own keys that are not shared across applications or any other contexts.
When first adding a data connection to your application, Transposit will ask you to authorize the connection. After adding a data connection, keys for that dependency can be added or removed from the Keys section of the Transposit operations console.
Transposit keeps separate sets of development and production keys. The keys shown in the Transposit operation console are for development. Adding or removing production keys is done via Authentication > Production keys.
From Authentication > Production keys, you can also require the user to provide the credentials for a data connection.
Keys used when running scheduled tasks are kept separate from development and production keys. You can add keys to a selected task via Deploy > Scheduled tasks.
Keychains are sets of keys that you can enable in development, production, or other contexts. They are managed in Transposit via Authentication > Keychains.