Skip to content
← All scenarios

Business applications

Your applications. Your identity platform.

Give employees, partners and customers a common identity foundation. Integrate the accounts you already use, configure the sign-in experience you need and keep the platform in your environment.

Plan your implementation

The business situation

A new application, an existing directory

A team is building a business application. Employees should use their enterprise accounts, while external users need accounts managed by the application team. Both groups need access to the same product.

01 / Working model

Connect your applications once

ProAuth acts as the identity provider your applications trust. Behind that integration, configure one or more OIDC providers and ProAuth user stores. Multiple identity sources do not require separate ProAuth installations.

Compatible applications use standard OIDC/OAuth integration. Your team defines application permissions and validates how identities map to business access. Existing integrations can be assessed individually.

Make the integration concrete.

Client type, security profile and permitted flows are part of your application configuration.

ProAuth client configuration showing flows and security profile
Configuration for each client applicationProduct preview · example data

Identity sources behind one integration.

ProAuth is the OpenID Provider for your application and the client of the upstream identity provider.

One integration, multiple identity sourcesApplications trust ProAuth as OpenID Provider. ProAuth is the client of the upstream OIDC provider and can use locally managed accounts.Your applicationsOIDC / OAuth clientsProAuthOpenID Provider / ASUpstream: RP / clientCorporate IdPUpstream OIDC providerProAuth user storeProAuth-managed accountsOIDC / OAuth 2.0OIDC federationLocal accounts
One integration, multiple identity sourcesApplications trust ProAuth as OpenID Provider. ProAuth is the client of the upstream OIDC provider and can use locally managed accounts.Your applicationsOIDC / OAuth clientsProAuthOpenID Provider / ASUpstream: RP / clientUser storeProAuth-managedLocal identitiesCorporate IdPUpstream OIDCExternal providerOIDC / OAuth 2.0Local accountsOIDC federation
One integration, multiple identity sourcesApplications trust ProAuth as OpenID Provider. ProAuth is the client of the upstream OIDC provider and can use locally managed accounts.Your applicationsOIDC / OAuth clientsProAuthOpenID Provider / ASUpstream: RP / clientProAuth user storeProAuth-managed accountsCorporate IdPUpstream OIDC providerOIDC / OAuth 2.0Local accountsOIDC federation

What your team gains

One application integration
Connect to ProAuth through OIDC and OAuth while it handles the configured identity sources.
Your existing accounts still fit
Combine enterprise federation and ProAuth user stores within the same deployment.
A product your team can shape
Use APIs and configurable authentication views to bring identity into your application experience.
02

Configure the experience around your organisation

Use the Management API and configuration tooling to manage tenants and supported settings at runtime. Your tools can integrate user administration through the user-store APIs.

Authentication views can follow your product design. Tenant-specific login views and SCIM provisioning require Enterprise. Your directory administrator configures the federation and any separate provisioning connection.

03

Own the platform and its lifecycle

Run ProAuth on your chosen Kubernetes infrastructure, with supported databases and the required shared services. Identity data, configuration and operating access stay under your administration.

ProAuth supplies the maintained product and product support. Your team owns application integration, infrastructure, deployment of updates and recovery validation; consultancy can help with those decisions.

Details for your decision.

Let’s plan your implementation.

Bring your application landscape and deployment requirements. We can review identity sources, integration boundaries and an appropriate edition together.

Discuss your identity platform

Image detail