Identity glossary: 64 terms
Reviewed 2026-11-10
Definitions come first in this glossary, followed by the access decision each term describes. Read identity, authentication and authorization as separate jobs. Each entry links to its source and the comparison where it matters. The examples are illustrative exercises, not customer stories or claims that both vendors implement every term identically.
Adaptive MFA
Multifactor authentication that selects additional proof using context. Microsoft's Conditional Access evaluates identity and access signals. The policy determines when extra authentication is required. Compare the relevant signals and controls rather than assuming similarly named products enforce the same decision.
Agent 365
Microsoft Agent 365 is Microsoft's control plane for managing agents. Its documentation distinguishes the wider product from Entra Agent ID and describes commercial availability. Buying it is a separate licensing decision from issuing an agent identity. Confirm the prerequisites and the particular controls your workflow requires before extending an existing subscription.
Agent identity
An identity representing a software agent, rather than a human employee. It lets administrators assign ownership, control connections and revoke access. The identity alone does not approve every action. Okta and Microsoft document dedicated agent identity models. Action governance remains a separate decision from employee sign-in and application login.
Agent sponsor
An accountable person associated with an agent's identity and lifecycle. Microsoft's agent documentation describes sponsorship as part of governance. A sponsor is not automatically the approver for each operation. Define who maintains the agent, who can revoke it, and who authorizes sensitive actions before granting the agent access to resources.
AI agent identity
An identity issued to a software agent so that its access can be granted, limited, logged and revoked like a person's. Microsoft Entra Agent ID and Okta for AI Agents document dedicated agent identities.
Authenticator assurance level (AAL)
NIST defines authenticator assurance levels in SP 800-63B-4, published 31 July 2025. Each level has technical requirements. A provider's product claim is not a verification of your configuration. Read the normative requirements and test the chosen authenticator and enrollment path against them.
Certificate-based authentication
Signing in with an X.509 certificate held on a smart card or device instead of a password. Microsoft lists it among the phishing-resistant methods for Entra ID.
Conditional Access
Microsoft Entra ID's policy engine: if-then rules that combine signals about the user or agent, location, device, application and risk, then block access or require steps such as MFA. It needs Entra ID P1.
Context-Aware Access
Google Cloud Identity's policy feature for allowing or blocking access based on context such as the user's device. Google lists it as a Premium edition feature.
Continuous Access Evaluation Profile (CAEP)
An OpenID Foundation specification, built on the Shared Signals Framework, that lets providers send changes in a user's session or risk posture so access can be re-evaluated during a session rather than only at sign-in. The OpenID Foundation says NIST IR 8587 recommends it.
Cross App Access
An open standard Okta supports for short-lived, scoped tokens that let one app or agent act in another app on a user's behalf, instead of storing long-lived keys.
Cross App Access (XAA)
Cross App Access lets an enterprise identity provider govern an application's delegated connection to another application. Okta's Agent SSO announcement describes short-lived tokens for agents supporting this standard. Connection authorization is not approval for every later action. The resource, requested scope and user context still determine what a token should permit.
Cross-tenant synchronization
An Entra ID feature for organisations that own several Entra tenants: it creates, updates and removes B2B collaboration users across them. Each synced user needs P1 in the source tenant.
Device assurance
Okta's device-security checks use configured assurance attributes in app sign-in policy rules. The policy must be incorporated into a rule before it applies. Define the expected result for enrolled, unmanaged and unknown devices rather than assuming device information is always complete.
Entra app gallery
Microsoft's catalog of pre-integrated applications for Entra ID. Microsoft says it contains thousands of applications and lists SAML, OpenID Connect, password-based and linked SSO, but publishes no count.
Entra ID P1 and P2
Microsoft's paid Entra ID plans. P1 includes Conditional Access. P2 adds Identity Protection, risk-based controls and privileged identity management. The pricing explainer records current figures and read dates. Confirm existing entitlements before buying another licence, and check Governance capabilities separately.
External MFA
An Entra ID option in which Entra keeps enforcing sign-in policy while another provider handles the MFA factor. Microsoft lists it as generally available in February 2026.
Federated and managed domains
In Microsoft 365, a federated domain sends users to an outside identity provider, such as Okta, to sign in; a managed domain signs them in with Entra ID itself. Moving off Okta ends with converting the domain from federated to managed.
Federation server
Software that issues sign-in tokens to applications over protocols such as SAML, OpenID Connect and WS-Federation. PingFederate is one that Ping Identity offers as a dedicated cloud tenant or as software you deploy in containers.
FedRAMP High
FedRAMP High is a government cloud-security authorization baseline. Ping's opened PingFederate page describes government deployment options. An authorization or product claim applies to its documented scope, not every installation. Confirm the actual service and deployment before relying on the label.
FIDO2 and WebAuthn
The open standards behind security keys and passkeys: the device holds a private key and proves possession to the site, so there is no shared secret to phish.
Golden SAML
An attack in which someone who obtains an identity provider's SAML token-signing key can forge sign-in tokens for any user. Protecting signing authority and validating tokens are distinct controls.
HR-driven provisioning
Using the HR system as the source of truth, so that hiring, role changes and departures create, change and disable accounts automatically. Okta and Entra ID each list the HR systems they support.
Human approval (CIBA)
CIBA is Client-Initiated Backchannel Authentication. Auth0 documents asynchronous authorization using this flow so an agent can request user involvement for a critical action. Approval must relate to the proposed operation, not merely the agent's existence. Define who approves, how long approval lasts and what happens when the request is refused or expires.
ID-JAG
ID-JAG means Identity Assertion JWT Authorization Grant. The MCP Enterprise-Managed Authorization explanation uses it to connect identity-provider assertions with resource authorization. It is a grant mechanism, not a universal agent permission. Administrators still define which resources and scopes are allowed, and resource servers still validate the resulting access token.
Identity provider (IdP)
The service that authenticates users and tells applications who they are, usually over SAML or OpenID Connect. Okta, Microsoft Entra ID and Ping Identity are identity providers.
LDAP and RADIUS
LDAP and RADIUS serve different directory and network authentication roles. Google's Cloud Identity edition comparison lists Secure LDAP under Premium. JumpCloud's pricing page lists Cloud LDAP and RADIUS capabilities. Confirm the selected package and integration instead of inferring coverage from a workforce suite name.
MCP authorization
MCP authorization controls access to a protected MCP server. Enterprise-Managed Authorization adds a central identity-provider path for approved connections. The server remains responsible for accepting only appropriate tokens and operations. Authorization for a connection should not be mistaken for permission to perform every sensitive action exposed by its tools.
Microsoft Entra Agent ID
Microsoft's identity platform for AI agents, listed as generally available to all Entra customers, with agent identities, blueprints for creating them and Conditional Access for agents. Extended security features need a Microsoft Agent 365 licence.
Microsoft Entra Connect
Microsoft's tool for synchronizing users and groups from on-premises Active Directory to Entra ID; cloud provisioning agents are the lighter alternative. Microsoft lists one or the other as a prerequisite for moving Microsoft 365 federation off Okta.
Microsoft Entra ID
Microsoft's cloud identity service, formerly Azure Active Directory. Microsoft began using the new name on 15 August 2023. It is the directory Microsoft 365 runs on.
Model Context Protocol (MCP)
An open protocol that lets AI applications call tools and data sources through MCP servers. Its authorization specification treats a protected MCP server as an OAuth 2.1 resource server and leaves token issuing to an authorization server.
Multifactor authentication (MFA)
Sign-in that requires two or more kinds of proof, such as a password and a phone prompt. Not all MFA is phishing-resistant.
OAuth 2.1
The revision of OAuth 2.0 that is still an IETF draft; the MCP specification cites draft-ietf-oauth-v2-1-13. MCP requires authorization servers to implement it for both confidential and public clients.
Okta FastPass
Okta's passwordless sign-in, using device trust and biometric checks. Okta states that it meets FedRAMP High and NIST requirements for AAL3 on properly configured devices.
Okta Integration Network (OIN)
Okta's catalog of pre-built integrations. Its opened catalog describes more than 8,000 integrations, read 2026-11-03. Catalog presence does not establish provisioning, session termination or every policy feature. Check the exact integration before treating its listing as full application lifecycle support.
OpenID Connect (OIDC)
An identity layer on top of OAuth 2.0 that lets an app receive a signed statement of who the user is. Common for modern web and mobile apps.
OpenID Connect Key Binding
An OpenID Foundation specification for binding cryptographic keys within OpenID Connect flows, so a token is tied to a key the client holds. Members approved it as an Implementer's Draft on 10 September 2026.
OpenID Federation
An OpenID Foundation specification, from the OpenID Connect Working Group, for establishing trust between parties in a federation. Members approved version 1.0 as a Final Specification in February 2026.
Pass-through authentication
An Entra ID sign-in method in which an agent checks the user's password against on-premises Active Directory, so passwords are validated on-premises. One of the options when moving Microsoft 365 off Okta.
Passkey
A FIDO2 credential that replaces a password. Device-bound passkeys stay on one device or security key; synced passkeys are backed up across a user's devices by a platform such as iCloud Keychain or Google Password Manager.
Passkey profile
An Entra ID setting in the authentication methods policy for managing synced and device-bound passkeys side by side. Microsoft lists passkey profiles as generally available in March 2026.
Password hash synchronization
An Entra Connect option that extends directory synchronization so users sign in to Entra ID and Microsoft 365 with their on-premises Active Directory password. One of the options when moving Microsoft 365 off Okta.
Password-based SSO (SWA)
Password-based SSO fills application credentials when federation is unavailable. Okta calls this Secure Web Authentication, or SWA. Microsoft's app gallery documents password-based SSO separately from federation. It is a different mechanism from accepting a signed assertion or identity token.
Per-call authorization
A policy decision made for an individual tool or API call, rather than only when a connection begins. The relevant question is whether the proposed operation is allowed now. Identity, resource, scope and context inform that decision. A valid login or reusable access token does not by itself establish approval for every operation.
Phishing-resistant MFA
MFA that cannot be relayed by a fake sign-in page, because the credential is bound to the real site or device. Microsoft lists Windows Hello for Business, macOS Platform Credential, passkeys, FIDO2 keys and certificate-based authentication.
PIV and CAC smart cards
Certificate-bearing smart cards used by US federal employees (PIV) and the US military (CAC). Okta lists support for them alongside FastPass and FIDO2 WebAuthn.
PKCE
Proof Key for Code Exchange: the client creates a secret verifier and a matching challenge, so only the client that started a sign-in can exchange the authorization code for tokens. MCP clients must use it, with the S256 method when technically capable.
Protected Resource Metadata
A document, defined in RFC 9728, that a resource server publishes to say which authorization servers issue tokens for it. MCP servers must publish one, and MCP clients use it to find where to get a token.
Resource indicator
The resource parameter from RFC 8707, which names the service a token is meant for so the token can be bound to that audience. MCP clients must send it in both authorization and token requests.
SAML 2.0
An XML-based standard for single sign-on in which the identity provider sends a signed assertion to the application. Widely used for enterprise SaaS.
SCIM
System for Cross-domain Identity Management is an API standard for account provisioning. Microsoft's documentation describes SCIM 2.0 for creating, updating and removing identities in applications. Sign-in is a separate protocol decision. Validate account lifecycle support for the exact application rather than assuming federation includes provisioning.
Secure Split Key
A split signing-authority design separates control of a signing key across distinct environments. Evaluate signing authority independently from authentication and resource authorization.
Security defaults
Microsoft's baseline Entra ID security settings, available to all customers at no additional cost. Organisations that need custom rules move to Conditional Access, which needs P1.
Short-lived credentials
Credentials or tokens that expire after a limited period, rather than remaining valid indefinitely. Okta's Agent SSO announcement describes short-lived tokens for agent connections. Expiration reduces the period of useful access, but does not prove every request is appropriate. Combine a limited lifetime with scope, audience checks and a revocation plan.
Single sign-on (SSO)
One sign-in that gives access to many applications, with the identity provider vouching for the user to each app.
Staged rollout
An Entra ID feature that moves chosen pilot groups from federated sign-in to cloud authentication before the whole domain is converted, used when moving Microsoft 365 off Okta.
Token binding
A token-protection approach that connects a token to proof held by its intended presenter. Audience restriction and key binding address different questions. The first identifies the intended resource; the second limits who can present the token. A deployment must specify the mechanism and validation behavior rather than assuming every bearer token is bound.
Token lifetime policy
A setting that controls how long an access token, ID token or SAML token stays valid. Microsoft lists configurable token lifetime policies per application as generally available in April 2026.
Token replay
Reusing a stolen but still valid token or session to act as the user without the password or MFA. Short lifetimes, key binding and continuous evaluation narrow the window; NIST IR 8587 covers protecting tokens from theft and misuse.
Universal Logout
An Okta capability in Identity Threat Protection that ends a user's sessions across supported apps when risk changes.
Windows Hello for Business
Microsoft's passwordless sign-in for Windows, using a key held on the device and released by a PIN or biometric. Microsoft lists it as phishing-resistant.
WS-Federation
An older Microsoft-originated federation protocol. Okta's Microsoft 365 integration can use it to federate Microsoft 365 sign-in.