Before you can integrate with Transmit Security, you'll need to create an application. This application contains configuration details for your integration, including branding, authentication settings, and more. The application requires at least one client but it can have multiple clients associated with it—each client represents an implementation and has unique settings. The first client is created automatically and set as default.
Let's assume, you are integrating a food delivery service with Transmit Security, and you have created an application for it. The service has a web version as well as a native iOS app. Both the web app and mobile app are the clients of this application.
Certain settings are configured on the application level and are shared across clients. These are general details, branding, and authentication settings. Clients share signups—for example, if a new user signs up using a web app, they no longer need to register themselves in the mobile app as they have already signed up within the application.
The settings specific to a client include credentials used for generating client access tokens, client types, resources, and enabled flows. For example, you can enable a device flow for one client and keep it disabled for the other.
By default, Transmit app clients are first-party clients which assumes they are owned by you. To support integrations with other providers, Transmit enables you to create third-party clients. A third-party client is an external service that can request access to your app resources and leverage APIs while being controlled by someone else. For security reasons, third-party clients should only gain access to the app after explicitly obtaining a user's consent using your first-party client. Administrators can review and manage user consents.