Skip to Content

Introduction

What the Identity & Access Management platform does: single sign-on, directories, strong authentication, provisioning, device trust, and audit.

The platform is a complete identity and access management system. It authenticates your users, gives them single sign-on to every connected application, and gives you the controls to govern who can access what, under which conditions. This page introduces the building blocks so the rest of the documentation makes sense.

Single sign-on for every application

Users sign in once and reach all of their applications without re-entering credentials. The platform speaks the three protocols that cover virtually every application in use today:

  • OpenID Connect (OIDC) — the modern standard for web, single-page, mobile, and machine-to-machine applications. Supports authorization-code with PKCE, refresh tokens, the device authorization grant, client credentials, token introspection and revocation, DPoP sender-constrained tokens, and back-channel logout.
  • SAML 2.0 — the established enterprise SSO standard. The platform acts as the Identity Provider (IdP): it issues signed (optionally encrypted) assertions, supports IdP- and SP-initiated flows, and Single Logout.
  • WS-Federation — for older Microsoft-oriented relying parties such as Exchange OWA and SharePoint. The platform issues signed SAML 1.1 tokens through a Security Token Service.

You configure each application once under Integrations → Applications, either from a catalog of pre-built integrations or as a custom OIDC/SAML/WS-Fed app.

Two directions of trust

The platform acts in two roles, depending on who trusts whom:

  • As an identity provider, it vouches for one of your users to an application. The app trusts a signed token (OIDC) or assertion (SAML/WS-Fed) the platform issues, instead of asking the user for a password itself. This is the direction described above.
  • As a relying party (also called brokering), the platform sends users out to an external identity provider, such as a social login or a partner's corporate IdP, and trusts the identity that comes back. You set this up with Connections.

In short: applications trust the platform; the platform, in turn, can trust upstream providers through Connections.

A directory for your users

Every user belongs to a directory. A directory is either:

  • a local directory — users stored and authenticated locally, or
  • an enterprise directory — users synchronized from Active Directory or LDAP, with authentication delegated to that source.

On top of directories you organize users into groups (for shared application access and roles) and, with the CIAM add-on, into organizations (for B2B multi-org scenarios). See Directories.

Strong, risk-based authentication

The platform supports a full range of authentication factors — passwords, passkeys, WebAuthn roaming security keys, TOTP authenticator apps, SMS one-time codes, and recovery codes. Password security is hardened by default with breached-password and dictionary checks.

Rather than forcing the same requirements on everyone, authentication policies let you decide when step-up authentication or MFA is required — based on network location, device state, risk, time of day, or user attributes. See Security → Conditional access.

Provisioning into downstream systems

When you create or change a user, the platform can automatically create, update, or deactivate the matching account in connected SaaS applications using outbound SCIM provisioning. Attribute mappings are defined per application, and a catalog of pre-built integrations ships with provisioning templates. See Integrations → Application provisioning.

APIs and machine-to-machine access

Not every caller is a person. The platform protects your own back-end APIs and lets services talk to each other without a user present, using the client-credentials grant (a service authenticates with a client ID and secret and gets a token scoped to exactly what it is allowed to do). You register a protected API and its scopes under Integrations → APIs; the platform's own management API works the same way.

Roles and permissions

With the RBAC add-on, you define roles — bundles of permissions — and assign them to users directly or through groups. The permissions a role grants can flow into the access token at sign-in, so an application can make authorization decisions without a separate lookup. See Integrations → Roles.

Federated login through Connections

Plan note: Social providers are part of every plan; enterprise providers (generic OIDC/SAML, Microsoft Entra) require the enterprise brokering feature (Advanced plan and above). See Connections.

A Connection lets your users sign in with an external identity — a social provider or a partner's corporate IdP — while the platform stays the single front door your applications trust. The platform acts as the relying party to that external provider and maps the returning identity onto a local account. See Integrations → Connections.

Device trust

Add-on required: Device management is part of the DIAM (Device Identity) add-on.

With DIAM, endpoints enroll with the platform through a lightweight agent and appear in the Device inventory. You can evaluate their security posture against device compliance policies, factor device state into authentication decisions, and run remote actions (such as isolating a compromised endpoint) directly from the console.

Audit and oversight

Every significant action is recorded in a tamper-evident audit log — each entry is sealed into a hash chain and cryptographically signed, so an exported log can be verified by a third party. Alongside it, the Security Health dashboard scores your configuration against established frameworks, and threat protection guards the login surface against bots, brute force, and breached credentials. See Monitoring and Security.

Where to go next

On this page