# Glossary

Definitions of the identity, protocol, and platform terms used across the Admin Console and this documentation.

Concise definitions of the terms you meet across the Admin Console and these docs. Where a concept has its own section, the entry links to it.

### AAL (Authenticator Assurance Level)
A measure of how strongly a user's identity was proven at sign-in, defined by NIST SP 800-63B. AAL1 is single-factor, AAL2 is multi-factor, and AAL3 requires a hardware-bound, phishing-resistant authenticator. See [Authentication levels](https://dts-identity.com/docs/reference/authentication-levels.md).

### ACR (Authentication Context Class Reference)
A value that names the authentication strength achieved or required for a session — the platform's way of expressing an AAL in a policy or token. Authentication policies and applications request a minimum ACR; the platform resolves the ACR a session reached from the factors used. See [Authentication levels](https://dts-identity.com/docs/reference/authentication-levels.md).

### Add-on
A separately licensed capability area layered on top of your subscription tier. The two add-ons are **CIAM** (customer/external identity, organizations, social login) and **DIAM** (device identity and compliance). See [Plans & add-ons](https://dts-identity.com/docs/getting-started/plans-and-addons.md).

### AMR (Authentication Methods References)
The list of individual methods used during a sign-in (for example password, TOTP, security key), recorded per session and surfaced in tokens. The combination of methods determines the ACR a session reaches.

### Application
A relying service that delegates authentication to the platform, configured under [Integrations → Applications](https://dts-identity.com/docs/integrations/applications.md). An application uses one protocol — OIDC, SAML, or WS-Federation — and may also receive provisioned accounts via SCIM.

### Audit log
The tamper-evident record of significant events (sign-ins, configuration changes, lifecycle actions). Each entry is sealed into a hash chain and signed so an exported log can be verified independently. See [Audit logs](https://dts-identity.com/docs/monitoring/audit-logs.md) and [Audit event types](https://dts-identity.com/docs/reference/audit-event-types.md).

### Authentication policy
A conditional-access rule set that decides *when* multi-factor or step-up authentication is required, based on conditions such as the user's directory, group membership, specific users, network zone, or time window. See [Authentication policies](https://dts-identity.com/docs/security/conditional-access/authentication-policies.md).

### Back-channel logout
An OIDC mechanism in which the platform notifies each signed-in application server-to-server when a user logs out, so the user's session is ended everywhere without relying on browser redirects.

### Claim
A piece of information about a user (such as email, name, or group membership) carried in an ID token, an access token, or a SAML assertion, and delivered to applications according to the requested scopes and the attribute mapping.

### Client assertion (private key JWT)
A short-lived JWT an application signs with its own private key to authenticate itself, instead of sending a shared client secret. The platform verifies it against the public key registered on the application. Required by the Financial-grade API security profiles. See [Financial-grade API security](https://dts-identity.com/docs/integrations/applications.md#financial-grade-api-security).

### Connection
A federated login to an external identity provider — a social login (such as Google, GitHub, LinkedIn) or another enterprise IdP — letting users sign in with an existing account. Connections are inbound federation, distinct from applications. See [Connections](https://dts-identity.com/docs/integrations/connections.md).

### Device compliance
The evaluation of an enrolled device's security posture (disk encryption, firewall, installed or vulnerable software, and similar) against policy. Part of the DIAM add-on and usable as a condition in authentication policies.

### Directory
The source of a set of users. A **local** directory stores and authenticates users in the platform; an **enterprise** directory synchronizes users from Active Directory or LDAP and delegates authentication to that source. Every user belongs to exactly one directory.

### DPoP (Demonstrating Proof-of-Possession)
An OAuth 2.0 mechanism that binds an access token to a key held by the client, so a stolen token cannot be replayed by anyone who does not also hold the key (sender-constrained tokens).

### FAPI (Financial-grade API)
A set of hardened OAuth 2.0 and OIDC security profiles from the OpenID Foundation, written for high-value data such as open banking, payments, and health records. Applied per application as a security profile, which then pins key-based client authentication, pushed authorization requests, sender-constrained tokens, and stronger signatures. See [Financial-grade API security](https://dts-identity.com/docs/integrations/applications.md#financial-grade-api-security).

### FIDO2
The standards family (WebAuthn plus CTAP) behind passkeys and roaming security keys, enabling phishing-resistant, public-key-based authentication. See *WebAuthn* and *passkey*.

### Grant
A persisted record of the access a user has consented to give an application — the scopes and claims it may receive — issued during the OAuth 2.0 / OIDC authorization flow and reusable on subsequent sign-ins.

### Home Realm Discovery
Routing a sign-in to a federated connection automatically, based on the email domain the user enters: instead of the password screen, the user is sent straight to their organization's identity provider. Configured per connection via its email domains. See [Connections](https://dts-identity.com/docs/integrations/connections.md).

### IdP (Identity Provider)
A system that authenticates users and asserts their identity to other services. The platform acts as an IdP for OIDC, SAML, and WS-Federation. It can also consume an external IdP through a connection.

### Impersonation
An audited support tool that lets an authorized admin act as a user to reproduce what that user sees. The platform records the action in the audit log with the real actor kept distinct from the subject, and logs the start and end as separate events. On CIAM deployments the same mechanism backs "switch organization view," scoping the console to one customer's data. See [User lifecycle](https://dts-identity.com/docs/directories/user-lifecycle.md) and [Audit event types](https://dts-identity.com/docs/reference/audit-event-types.md).

### JWKS (JSON Web Key Set) / signing key
The set of public keys that applications use to verify tokens and assertions issued by the platform. The corresponding private signing keys are managed under [Settings → Signing keys](https://dts-identity.com/docs/settings/signing-keys.md) and can be rotated.

### MFA (Multi-Factor Authentication)
Requiring two or more independent factors (something you know, have, or are) to sign in. See [Multi-factor authentication](https://dts-identity.com/docs/security/multi-factor-authentication.md).

### Mail-domain reservation
A directory setting that claims one or more email domains exclusively for that directory. Once a domain is reserved, no account in a different directory can use an email in it — every path that creates a user or changes an email honors the claim. This stops open sign-up or a federated login from seizing a protected domain. See [User directories](https://dts-identity.com/docs/directories/user-directories.md).

### NameID
The identifier for a user inside a SAML assertion — the value an application uses to recognize the returning user. Its format and source attribute are configured per SAML application.

### Network zone
A named set of IP ranges (or, for dynamic zones, countries and known service networks) used as a condition in policies — for example a trusted corporate network where the second factor may be relaxed. A zone is either **trusted** or **untrusted**; an untrusted zone acts only through the policy that references it. See [Network zones](https://dts-identity.com/docs/security/conditional-access/network-zones.md).

### OAuth 2.0
The authorization framework underlying OIDC, governing how applications obtain access tokens to call APIs. The platform supports authorization-code with PKCE, client credentials, the device authorization grant, refresh tokens, token introspection, and revocation.

### OIDC (OpenID Connect)
The modern authentication layer built on OAuth 2.0, used by web, single-page, mobile, and machine-to-machine applications. Adds the ID token and a standard set of identity claims.

### Organization
A grouping for B2B scenarios — a customer company whose users and admins are scoped together, with its own member roster and delegated administrators. Requires the CIAM add-on. See [Organizations](https://dts-identity.com/docs/directories/organizations.md).

### PAR (Pushed Authorization Request)
An OAuth 2.0 extension where the application sends its authorization parameters to a back-channel endpoint first and receives a one-time reference, then redirects the user with only that reference. The parameters never appear in the browser URL, so they cannot be inspected or tampered with in transit. Required by the Financial-grade API security profiles.

### Passkey
A FIDO2/WebAuthn credential that replaces the password — a private key held on the user's device or password manager and verified with biometrics or a PIN. Phishing-resistant and synced or device-bound depending on the platform.

### PKCE (Proof Key for Code Exchange)
An extension to the authorization code flow in which the application sends the hash of a secret it generated (the challenge) with the authorization request, then the secret itself (the verifier) when redeeming the code. An intercepted code is therefore useless on its own. S256 is the only challenge method accepted; PKCE is required for public clients and under a Financial-grade API security profile, and recommended everywhere else.

### Provisioning-only application
An application configured for outbound SCIM provisioning without single sign-on — accounts are created, updated, and deactivated in the target app, but users do not log in to it through the platform. SSO and provisioning are independent toggles on an application. See [Application provisioning](https://dts-identity.com/docs/integrations/application-provisioning.md).

### RBAC (Role-Based Access Control)
Granting permissions through roles rather than to individuals directly. The platform's admin permissions and assignable roles use this model. See [Roles](https://dts-identity.com/docs/integrations/roles.md).

### Risk score
A per-user posture score combining factors such as breached credentials, login anomalies, and device state, used to inform conditional-access decisions and surfaced for monitoring.

### Role
A named bundle of permissions or application access that can be assigned to users or groups, the unit of RBAC.

### RP / SP (Relying Party / Service Provider)
The application that relies on the platform for authentication. "Relying Party" is the OIDC term; "Service Provider" is the SAML term. Both denote the same role: the consumer of an assertion the platform issues.

### SAML (Security Assertion Markup Language) 2.0
The established enterprise SSO standard. The platform acts as the SAML Identity Provider, issuing signed (optionally encrypted) assertions for IdP- and SP-initiated flows and supporting Single Logout.

### Scope
A label requested by an application that determines which claims and which API access it receives (for example `openid`, `profile`, `email`). Consent to scopes is captured in the grant.

### SCIM (System for Cross-domain Identity Management)
The standard for provisioning accounts between systems. The platform performs **outbound** SCIM provisioning — it creates, updates, and deactivates user accounts in connected downstream applications (it provisions users, not group objects). See [Application provisioning](https://dts-identity.com/docs/integrations/application-provisioning.md).

### SSO (Single Sign-On)
Signing in once and reaching every connected application without re-entering credentials. Delivered through OIDC, SAML, and WS-Federation.

### Step-up authentication
Prompting an already-signed-in user for an additional or stronger factor before a sensitive action or application — raising the session's ACR on demand rather than at initial login.

### TOTP (Time-based One-Time Password)
A six-digit code that rotates on a timer, generated by an authenticator app and used as a second factor.

### WebAuthn
The browser API of FIDO2 by which a website asks the device to create or use a public-key credential — the technology behind passkeys and roaming security keys. See [Multi-factor authentication](https://dts-identity.com/docs/security/multi-factor-authentication.md).

### WS-Federation
An older Microsoft-oriented federation protocol for relying parties such as Exchange OWA and SharePoint. The platform issues signed SAML 1.1 tokens through a Security Token Service.
