Skip to content

Identity for applications

Authentication for every app you build.

Add secure signup, login, sessions and trusted machine connections across web, mobile and SaaS products — without rebuilding authentication from the ground up.

The situation

What this usually looks like

Three things we are describing, not three things we are offering. If two of them match the system you have, you are reading the right page.

  1. 01

    Each service implements token validation slightly differently, and nobody is certain which is correct.

  2. 02

    Rotating a signing key means a coordinated release across every application.

  3. 03

    Test environments share production credentials because separating them was never finished.

The approach

How this is addressed.

What the platform does about the situation above, layer by layer, before any service names are involved.

One identity, many applications
Connect applications within a consistent identity ecosystem. Share sign-in where appropriate, separate customer organizations, and preserve application-specific contexts and privacy boundaries.
Standards-based foundations
Use OpenID Connect for sign-in and OAuth 2.0 for token-based delegated access. Integrate enterprise SSO through SAML or OIDC, and support directory provisioning through SCIM.
Applications, services and APIs
Register user-facing applications, backend services and partner integrations. Authenticate each type of client with the appropriate method, issuance profile and credential lifecycle.

The services involved

What this is built from.

A solution is a reading path through the catalogue, not a separate product. These are the services it draws on — each one with its own page, scope and integration detail.

Every service above establishes who or what is making a request. Deciding whether that authenticated principal may perform a particular action is authorization, and it stays with the consuming application or a separate authorization layer. Each service page states where it stops.

Identity for applications

Where this starts.

Create a development tenant and connect one application, or talk the architecture through first — tenancy, evidence, credential lifecycle, and which parts stay in your own stack.

Reading first is fine too: the developer portal covers APIs, SDKs and the standards each flow follows, and pricing sets out the packages and what is metered — the figures themselves are agreed with our team.