Skip to main content
Available starting with FlowX.AI 5.5.0Container app authentication provides built-in authentication handling for applications that embed FlowX UI Flows.

Overview

A container app is any web or mobile application that embeds FlowX UI Flows using the FlowX renderers (Angular, React, iOS, or Android SDKs). Container apps are responsible for authenticating end users before rendering FlowX content. FlowX.AI 5.5.0 enhances the container app authentication flow with built-in support for OAuth2/OIDC authentication, custom landing pages, and improved session management.

Key features

Authentication providers

Support for multiple OAuth2/OIDC authentication providers via Keycloak integration

Custom landing page

Configure a landing page for unauthenticated users with organization branding

Session management

Automatic token refresh, silent refresh support, and redirect URI persistence

SSO integration

Single sign-on across container apps within the same organization

How it works

The container app authentication flow handles the following:
1

Organization resolution

The container app resolves the organization context using the hostname or an organization code. This determines which Keycloak realm and authentication configuration to use.
2

Authentication redirect

Unauthenticated users are redirected to the configured identity provider (Keycloak) for login. The redirect URI is persisted in local storage to restore the user’s navigation state after authentication.
3

Token management

After successful authentication, the container app manages access tokens with automatic refresh. Silent refresh keeps the session alive without requiring user interaction.
4

UI Flow rendering

Once authenticated, the container app renders FlowX UI Flows with the user’s identity and permissions.

Configuration

Authentication setup

Container apps authenticate using OAuth2/OIDC with the following configuration:
ParameterDescription
Organization codeIdentifies the organization for multi-tenant environments. Can be derived from the hostname or provided explicitly.
Keycloak realmThe Keycloak realm associated with the organization
Client IDThe OAuth2 client ID registered in Keycloak for the container app
Redirect URIThe URI to redirect to after authentication. Persisted across browser sessions.
For multi-tenant SaaS deployments, the organization code is typically extracted from the subdomain (e.g., acme.flowx.ai resolves to organization acme).

Landing page

You can configure a custom landing page that appears for unauthenticated users. This page can include:
  • Organization branding and logo
  • Login button that initiates the authentication flow
  • Links to support or documentation

Session behavior

BehaviorDescription
Token refreshAccess tokens are refreshed automatically before expiration
Silent refreshBackground token renewal without user interaction
Redirect persistenceThe user’s intended destination is stored and restored after login
Session timeoutConfigurable session duration based on Keycloak realm settings

SDK integration

Each FlowX renderer SDK handles container app authentication:
The Angular SDK integrates with angular-oauth2-oidc for authentication handling. Configure the OAuth2 module in your app with the Keycloak endpoints for your organization.For setup details, see the Angular SDK documentation.

Last modified on February 27, 2026