Application clients

Application clients define the relationship between Strivacity and the brand portal’s preferred authentication protocol. Strivacity supports both modern and legacy approaches to ensure you can modernize what you can while still supporting legacy systems.

Application clients include:

• OIDC using no-code components: Enables the full power of Strivacity's login and registration workflows implemented via OAuth2/OIDC and no-code components. This client can also be configured to enable the Strivacity Admin portal APIs.
• OIDC using a simple API: Enables ONLY a simple username/password check using an OAuth2/OIDC API endpoint.
• OIDC using the Journey Flow API: Enables native client experience via an OAuth2/OIDC and the Strivacity Journey-flow API for Native Clients.
• OIDC using the token exchange mechanism: The OAuth token exchange is a mechanism that allows a client to trade one access token for another, typically with different scopes, audiences, or subject identities.
• SAML2 using no-code components: Enables the full power of Strivacity's login and registration workflows implemented via SAML2 and no-code components.
• Login Gateway: Enables headers-based authentication via connection to an on-premise Login Gateway component.

Two additional clients integrate with Strivacity-provided applications: the Organization portal and the Self-service portal.

Creating a client

You can create a client after creating and saving an application.

1. Open Applications.
2. Select the application you want to configure.
3. Open the Clients tab.
4. Select Create client.
5. Choose the client type.
6. Configure the client settings.

After creating a client, you can open it from the client list to edit its configuration.

Client configuration

After creating a client, you can configure how the client interacts with Strivacity authentication.

Client configuration is managed in the Admin Console under:

Applications → select application → Clients → select client

Each client contains several configuration tabs. These tabs define how the client behaves during authentication and how it integrates with the brand application.

The available configuration tabs depend on the selected client type.

The following pages describe the configuration options for each client type:

• OIDC client (using no-code components)
• OIDC client (using a simple API)
• OIDC client (using the Journey Flow API)
• SAML2 client