Feed

Descope states it was recognized as the only Visionary in the 2026 Gartner Magic Quadrant for Customer Identity and Access Management (CIAM).

Descope: the Only Visionary in 2026 Gartner® Magic Quadrant™ for CIAM ↗

What happened

• Descope states it was an Honorable Mention in the 2025 Gartner Magic Quadrant for Access Management.
• Descope states Gartner listed it as a Sample Vendor for CIAM for AI Agents and Journey-Time Orchestration in two 2026 Hype Cycles.
• Descope states its Agentic Identity Hub handles authentication and access control for more than 1,000 MCP servers.

Why it matters to Signicat

• Analyst placement claim is vendor-reported; the full Gartner report is not in the source and is offered only on request.
• Descope positions CIAM as a distinct category separate from workforce access, a framing relevant to Signicat's customer identity positioning.
• Descope's agent identity content, including Agentic Identity Hub, is positioned as a core platform element; Signicat has no agent identity product in its listed product lines.

4 of 4 facts verified against the source · confidence medium · claude-haiku-5-5

Descope states the Descope Agent Gateway is currently in early access.

The Developer’s Guide to MCP Gateways ↗

What happened

• Descope states its Agent Gateway exposes one gateway URL and exchanges tokens per route.

Why it matters to Signicat

• Descope positions its identity layer for agent and MCP connections, an area adjacent to Signicat's orchestration and authentication offerings.

2 of 3 facts verified against the source · confidence high · claude-haiku-5-5

Descope launches Envoy for delegated consumer AI agent sign-in

Descope Unveils Envoy, an Identity-Aware Way For Personal AI Agents to Act on People’s Behalf ↗

What happened

• Descope announced Envoy on November 4, 2026, a set of capabilities giving personal AI agents a delegated sign-in path alongside a consumer app's existing authentication flows.
• GoFundMe, You.com, GoodRx and Composio are named as launch and design partners for Envoy.
• Envoy includes Personal Agent Protocol support using Client ID Metadata Documents with no pre-registration required and DPoP-bound session tokens.
• Envoy supports Rich Authorization Requests to define agent permissions on a customer account.
• Envoy uses Client-Initiated Backchannel Authentication (CIBA) for out-of-band approval of sensitive agent actions.
• Descope published a Poppy SDK, a zero-dependency TypeScript SDK for AI agent builders.
• Envoy builds on the Descope Agentic Identity Hub, which Descope says handles authentication and access control for 1000+ MCP servers.

Why it matters to Signicat

• Envoy targets consumer-app agent login, a direct overlap with Signicat's authentication and orchestration offerings for consumer sign-in flows.
• Descope frames agent access as a standards-based alternative to blocking agents or letting them sign in as humans; this is a vendor narrative, not independently verified.

7 of 7 facts verified against the source · confidence medium · claude-haiku-5-5

Descope announced Agentic Identity Hub 3.0, adding agent governance, runtime enforcement across Policy Enforcement Points, and expanded client authentication methods.

Introducing Descope Agentic Identity Hub 3.0: Governance and Control for AI Agents ↗

What happened

• The Agent Governance Suite is available only for the Enterprise tier; other capabilities are available to any developer, including Free Forever tier users.
• Agent SSO (Cross-App Access) issuance and validation of ID-JAGs is described as supported by Descope.
• Client authentication options now include SPIFFE workload identities, private_key_jwt, and mutual TLS with certificate-bound tokens.

Why it matters to Signicat

• Descope is extending agent identity into governance and runtime policy, an adjacent area to Signicat's authentication and trust orchestration offerings; Signicat's agentic AI posture is not supplied here.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Descope announced Agentic Identity Hub 3.0, which brings governance, policy enforcement, and auditing to AI agents and MCP servers that organizations run internally.

Descope Unveils Agentic Identity Hub 3.0 to Enhance Governance and Control for AI Agents ↗

What happened

• The release adds an Agentic Governance Suite with a self-service onboarding and approval workflow for AI agents.
• The release adds MCP gateway integrations, with native integration described for agentgateway, an open source project of the Agentic AI Foundation.
• The release adds advanced client authentication supporting private_key_jwt, mutual TLS, SPIFFE and workload identity federation.
• The release adds ID-JAG issuance for internal agents, with policies evaluated on every request.

Why it matters to Signicat

• Descope extends agent identity from external-facing to internal agents, an adjacent area to Signicat's orchestration and authentication lines, with no direct overlap in Signicat's listed products.

5 of 5 facts verified against the source · confidence medium · claude-haiku-5-5

Descope publishes B2C delegated agent access guide using Northbound demo store

The B2C Developer’s Guide to Delegated Agent Access ↗

What happened

• Descope published a developer guide on delegated agent access for B2C sites, using a sample store, Northbound, that it says runs with Descope as its OAuth authorization server.
• The guide describes approval of agents via device code or CIBA, with step-up approval for purchases.

Why it matters to Signicat

• Overlaps Signicat's authentication and orchestration positioning for agent-facing sign-in, but describes a demo implementation rather than a shipped Descope product line.

2 of 2 facts verified against the source · confidence high · claude-haiku-5-5

Descope announced Family Accounts, a feature for modeling parent-child, guardian-dependent and multi-family relationships in its authentication layer.

Introducing Descope Family Accounts: Relational Identity for Consumer Apps ↗

What happened

• Descope states Family Accounts is now available in the Descope console.
• Dependent profiles hold identity records without credentials and are accessed through a guardian's session.
• Independent guardianship lets multiple unrelated adults act as co-guardians for one dependent profile, each under their own identity.
• Every guardian action is written to a dedicated audit log in Descope.
• Family Accounts is supported via Descope Management SDKs and APIs.
• Step-up or dual approval for guardian-gated dependent actions is on the roadmap, not released.

Why it matters to Signicat

• Family Accounts targets consumer CIAM use cases (health, family banking, streaming) where Signicat's authentication and eID offerings are not positioned around household relationships; overlap with Signicat's core markets is limited by the source's lack of geographic or regulatory detail.
• The guardian-dependent model could matter for regulated banking or health buyers in Signicat's markets, but the post makes no compliance claims beyond audit logging.

7 of 7 facts verified against the source · confidence medium · claude-haiku-5-5

Descope states that projects can now be created in three additional regions: Singapore, Brazil, and the United Kingdom.

Descope Data Residency Is Now Available in Seven Regions ↗

What happened

• Descope states its residency regions now total seven across four continents, including US, EU, Canada and Australia.
• Descope states that user data and project configuration are stored and maintained only within the selected region, and cannot be moved between regions once selected.
• Descope states its multi-region data residency coverage is included in its Growth and Enterprise licenses.

Why it matters to Signicat

• Residency coverage in the UK and Brazil and Singapore extends a competitor identity layer into Signicat's UK core market; Signicat's listed core markets do not include Singapore or Brazil.
• Descope frames the identity store as the densest personal-data store and residency gap, a point relevant to buyer security questionnaires that Signicat's data-sovereignty messaging also addresses.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Descope makes Cross-App Access generally available in Agentic Identity Hub

SSO For Your Agents: Cross-App Access Support in Agentic Identity Hub ↗

What happened

• Descope announced that Cross-App Access (XAA) support is generally available as part of the Agentic Identity Hub.
• Descope supports both validating and issuing ID-JAG tokens.

Why it matters to Signicat

• Descope moves enterprise agent access toward the customer's own IdP, a direct overlap with Signicat's authentication and orchestration positioning for B2B identity.

2 of 3 facts verified against the source · confidence high · claude-haiku-5-5

Descope published a blog post comparing its AI agent and MCP authentication capabilities with Auth0.

Descope vs Auth0 for AI Agent and MCP Authentication ↗

What happened

• The post states that Auth0's Agent as Principal capability is available by invitation only.

Why it matters to Signicat

• Descope's comparison targets an agent identity and MCP authentication positioning that Signicat does not currently address in its listed product lines.
• The piece is a vendor-authored comparison; its Auth0 characterizations are unverified and attributable to Descope.

2 of 2 facts verified against the source · confidence high · claude-haiku-5-5

Descope MCP Server now listed as Claude Connector and ChatGPT Plugin

The Descope MCP Server Is Available On Claude and ChatGPT ↗

What happened

• Descope states the Descope MCP Server is now available as a Claude Connector and a ChatGPT Plugin.
• The MCP server exposes 23 tools, each named for the identity object or function it operates on.
• By default, access through the server is read-only, with users able to elevate permissions when needed.
• Connecting with OpenAI requires a valid Plus, Pro, or Team ChatGPT plan.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Descope published a blog post comparing its B2B auth and SSO capabilities with WorkOS across multi-tenancy, SSO provisioning, user journeys and risk-based MFA.

Descope vs WorkOS for B2B Auth and SSO ↗

Why it matters to Signicat

• The post is a named competitive comparison targeting a rival identity vendor, and is not a direct attack on Signicat.
• Low relevance to Signicat's core European eID, wallet and verification lines, since the post addresses enterprise SaaS SSO rather than eID brokering or identity verification.

1 of 1 facts verified against the source · confidence high · claude-haiku-5-5

The post is a comparison guide listing six ForgeRock alternatives, with Descope placed first in the table.

The Top 6 ForgeRock Alternatives for Access Management ↗

What happened

• Descope describes Descope Flows as its core differentiator, a visual no-code and low-code orchestration layer.
• The post states that ForgeRock products were rebranded under the Ping portfolio after the Ping Identity merger, with ForgeRock Access Management becoming PingAM.

Why it matters to Signicat

• Competitor content targets ForgeRock/Ping migration accounts, a segment overlapping Signicat's enterprise identity and orchestration offering.
• Descope positions itself on agentic identity for AI agents and MCP ecosystems, a theme Signicat does not claim in its context.

3 of 3 facts verified against the source · confidence high · claude-haiku-5-5

Descope adds a cloud-neutral agent directory, issuance-time policy, a credential vault and an authorization server to Azure AI Foundry deployments.

Build Identity-Aware Agents With Azure AI Foundry and Descope ↗

What happened

• The post outlines a procedure that includes creating an Agentic Client.
• The post states Descope MCP Auth implements the MCP authorization spec with OAuth 2.1, including DCR and Client ID Metadata Documents (CIMD).

Why it matters to Signicat

• Content frames Entra Agent ID as a gap-filled partner stack rather than a competitor, so Signicat's agent identity claims would compete for the same Foundry buyers.
• Post makes comparative claims about Entra External ID gaps (no CIBA, no DCR) without independent verification; treat as vendor-stated.

3 of 3 facts verified against the source · confidence medium · claude-haiku-5-5

Descope publishes a blog post with a step-by-step guide for integrating its Agentic Identity Hub with Google Vertex AI Agent Engine and ADK.

Build Identity-Aware Agents With Google Vertex AI, ADK & Descope ↗

What happened

• The post states Google's Agent Identity gives each agent a SPIFFE-based cryptographic identity.
• The post states Google Identity Platform is not an authorization server for customer resources and lacks DCR and CIBA.

Why it matters to Signicat

• Descope targets the agent-identity and MCP authorization layer, an adjacent area where Signicat's orchestration and authentication offerings could be compared.
• The post contrasts a cloud-neutral layer with hyperscaler-native identity; the claims are Descope's own and uncorroborated by independent testing.

3 of 3 facts verified against the source · confidence medium · claude-haiku-5-5

Descope expands Policies to govern non-agentic clients and agents

Descope Policies: Granular Access Rules for Agents (and More) ↗

What happened

• Descope announces significant enhancements to Descope Policies that expand use cases and bring non-agentic clients into scope.
• Policies are enforced at the token boundary and execute whenever a token is issued or exchanged.
• Policy conditions combine with logical AND to narrow matching.
• For OAuth Connections, policies can include scopes so a rule grants only part of a Connection.
• Policies targeting Resources can specify grant type, such as allowing client_credentials but not token exchange.

Why it matters to Signicat

• Policy-based token-boundary authorization for agents and MCP servers overlaps with Signicat's orchestration and trust positioning in agentic access, though Signicat's public pages reviewed here do not describe an equivalent product.

5 of 5 facts verified against the source · confidence medium · claude-haiku-5-5

Descope adds identity support for autonomous agents in Agentic Identity Hub

Identity for Autonomous Agents With Descope ↗

What happened

• Descope announced identity support for autonomous agents in its Agentic Identity Hub.
• Descope lists registration of agents as OAuth Clients with client credentials and JWT bearer grant types.
• Descope states it stores and brokers credentials for agents to access downstream services such as Slack and Gmail.
• Descope states the agent-facing lifecycle includes granular access policies evaluated at token issuance and exchange.
• The post includes a worked n8n and BigQuery MCP example with tool-level scopes and credentials fetched at call time.

Why it matters to Signicat

• Feature addition extends Descope's agentic identity coverage to non-interactive machine clients, an area Signicat does not cover in its listed product lines.
• The feature overlaps with agentic identity themes but is a developer-facing machine identity capability, so direct overlap with Signicat's verification and wallet products appears limited.

5 of 5 facts verified against the source · confidence high · claude-haiku-5-5

Descope adds Cross-App Access (XAA) support for AI agent access

Descope Unveils Cross-App Access (XAA) Support, Letting Enterprises Manage AI Agent Access With Their Existing Identity Providers ↗

What happened

• Descope announced Cross-App Access (XAA) support in its Agentic Identity Hub.
• Descope's XAA support includes ID-JAG token validation and ID-JAG token issuance.
• Descope's ID-JAG validation lets organizations register a trusted issuer per tenant and accept assertions from Okta, Ping, and other standards-compliant providers.
• Descope adds Cross-App Access to its SSO Setup Suite alongside SSO, SCIM, and JIT provisioning.
• Descope states that Cross-App Access is an open protocol adopted as the Enterprise-Managed Authorization extension to the Model Context Protocol.
• Descope cites a 2026 Gravitee finding that 22% of teams treat agents as independent identities.

Why it matters to Signicat

• XAA support lets enterprise IdPs govern agent access to MCP servers, overlapping Signicat's authentication and orchestration positioning for agentic identity; the overlap is with Signicat's product lines, not a confirmed Signicat agentic offering.
• The release is vendor-stated and uncorroborated by independent testing; Descope's 'first' and Frost Radar claims should be attributed to Descope.

6 of 6 facts verified against the source · confidence medium · claude-haiku-5-5

Descope named on UK GCA G-Cloud 15 framework, Lot 2b SaaS

Descope Named as a Supplier on Government Commercial Agency’s G-Cloud 15 Framework ↗

What happened

• Descope announced its UK entity was named as a supplier on GCA's RM1557.15 G-Cloud 15 framework under Lot 2b: Software as a Service.
• The UK Department for Work and Pensions is described as already using Descope.
• Descope states that G-Cloud listing lets eligible public buyers procure through pre-agreed commercial terms rather than a full procurement.
• Descope cites a survey of 400+ identity decision-makers: 88% using or planning AI agents, 37% past pilots.

Why it matters to Signicat

• The listing opens a UK public-sector procurement route that Signicat's UK presence could contest in government identity deals.
• Descope's pitch centers on customer and agentic identity, a narrower overlap with Signicat's core eID and verification lines.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Descope partners with IDMWORKS on customer and agentic identity

Descope Partners With IDMWORKS To Accelerate Enterprise Adoption of Modern Customer and Agentic Identity ↗

What happened

• Descope announced a partnership with IDMWORKS, which the release describes as a Top 10 IAM consultancy.
• Under the partnership, IDMWORKS will provide strategic guidance, implementation, integration, and managed services for Descope's platform.

Why it matters to Signicat

• Partnership with an implementation consultancy adds a channel competing for CIAM deals in North America.
• Descope's CIAM and agentic identity focus overlaps with Signicat's authentication and orchestration lines.

2 of 2 facts verified against the source · confidence high · claude-haiku-5-5

Descope announced Family Accounts, the first release in its relational identity framework, with first-class identity primitives for parent-child, guardian-dependent, and multi-family relationships.

Descope Launches Family Accounts to Power Guardian, Dependent, and Household Experiences ↗

What happened

• Family Accounts includes dependent profiles that are reached through a guardian's session and have no credentials or login flow.
• Family Accounts allows multiple unrelated adults to serve as co-guardians for the same dependent profile, each with their own identity and equal permissions.
• Family Accounts lets a user hold different roles and attribute values in each family and belong to several households.

Why it matters to Signicat

• Family-scoped delegation is a consumer identity feature area adjacent to Signicat's authentication and eID offerings; overlap with Signicat's regulated bank and public-sector flows is not established by this source.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Descope describes a project-level 'Tenant User Isolation' setting, 'Isolate users per tenant', that changes its identity model from shared across tenants to fully isolated per tenant.

Descope Per-Tenant Identity Isolation for B2B Platforms ↗

What happened

• With the setting enabled, the same login ID becomes a separate user in each tenant, with independent credentials, MFA state, profile, and history.
• Descope states tenant-level users are available now.

Why it matters to Signicat

• Signicat's B2B and white-label customers needing separate identity stores per client would face a competing option; impact is likely limited to that segment (assessment).

3 of 3 facts verified against the source · confidence high · claude-haiku-5-5

Descope published a blog post summarizing the FIDO Alliance's 2026 State of Passkeys report, including consumer awareness at 90%.

2026 FIDO Report: Passkeys at Global Scale ↗

What happened

• The post reports that 33% of consumers experienced a confirmed account compromise or breach notification in the past year.
• The post reports that 68% of organizations are deploying, piloting, or rolling out passkeys for employee authentication.
• The post cites a Descope customer, Branch Insurance, reporting a 50% reduction in auth-related support tickets after adding passkeys.

Why it matters to Signicat

• Content is thought-leadership framing passkeys as a low-friction add-on to existing auth, competing for the same authentication budgets as Signicat's authentication line.
• The post's use of a FIDO survey plus a single vendor-reported customer result is a marketing vehicle; the 50% figure is Descope's claim, not independently verified.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Descope launches hosted Admin Portal for tenant self-service identity administration

Introducing the Descope Admin Portal ↗

What happened

• Descope is launching the Admin Portal, a hosted, tenant-aware solution that uses Descope Widgets to give organizations a central, branded self-service portal.
• Teams can select which widgets appear in the Admin Portal, including user management, role management, access key management, application access, tenant profile management, and user profile features.
• Organizations can select which Descope Flow handles user authentication in the portal.
• The portal inherits project styling and branding, and can be activated or deactivated from the Descope Console.
• Users must belong to a tenant to access the Admin Portal, and access is set by tenant membership and permissions.

Why it matters to Signicat

• The launch extends Descope's B2B identity offering into tenant admin and delegated administration, an area where Signicat's orchestration and eID Hub customers could be targeted; impact is limited to the admin layer of B2B SaaS apps rather than regulated eID or identity verification markets.

5 of 5 facts verified against the source · confidence high · claude-haiku-5-5

The article is a guide on managing credentials held by AI agents, covering what goes wrong, how to manage them, and real-world implementations.

AI Agent Credential Management Best Practices ↗

What happened

• The article attributes a figure that only 13% of MCP servers that begin development reach deployment to Descope's data.

Why it matters to Signicat

• Content is thought leadership on agentic AI identity that competes for developer mindshare on agent authentication.

2 of 2 facts verified against the source · confidence high · claude-haiku-5-5

Descope publishes Flows guide for MCP authorization orchestration

The Power of Descope Flows: MCP Identity Orchestration ↗

What happened

• Descope published a blog post describing how Descope Flows can orchestrate MCP authorization steps.
• The post describes scope-aware step-up MFA, tenant routing, consent customization and claim enrichment as Flow patterns.

Why it matters to Signicat

• Descope positions Flows as a no-code orchestration layer for MCP authorization, overlapping Signicat's trust orchestration messaging on agent identity.

2 of 2 facts verified against the source · confidence high · claude-haiku-5-5

Descope introduces MAC, MATK and M2M Exchange pricing units

Descope M2M & Agentic Identity Pricing Update ↗

What happened

• Descope says the update is its first major pricing update since introducing the Growth tier over a year ago.
• Descope defines Monthly Active Consents (MACs) as counted when a unique user consents to any scope for a specific resource at least once in a month.
• Descope defines Monthly Active Tokens (MATKs) as tokens retrieved and used to perform an action, counted for downstream connections where Descope is the credential vault.
• Descope states that M2M exchanges are billable and include token exchanges using machine-to-machine flows and Descope Policies enforced for MCP servers or AI agents.
• Descope states that M2M and agentic identity essentials should be available to all developers on all plans, including the Free Forever tier.

Why it matters to Signicat

• Usage-metered units (MAC, MATK, M2M exchange) for agent and M2M auth may be compared against Signicat's per-check or contract pricing in competitive pricing narratives.

5 of 5 facts verified against the source · confidence medium · claude-haiku-5-5

Descope published a blog post comparing its B2B authentication and SSO capabilities with Auth0.

Descope vs Auth0 for B2B Auth and SSO ↗

What happened

• The post states Descope's multi-tenancy is part of its core architecture.

Why it matters to Signicat

• Comparison content naming a competitor's product line; relevant to Signicat's orchestration and enterprise-onboarding positioning. Content is vendor-authored and uncorroborated.

2 of 2 facts verified against the source · confidence medium · claude-haiku-5-5

Descope published a blog guide listing eight MCP server security best practices.

MCP Server Security Best Practices to Prevent Risk ↗

What happened

• The guide states that Descope's survey of more than 400 identity decision-makers found 94% admit identity-related concerns about agents.

Why it matters to Signicat

• Descope is positioning itself as an MCP and agentic identity authority, a segment adjacent to Signicat's authentication and orchestration lines.

2 of 2 facts verified against the source · confidence medium · claude-haiku-5-5

The article is a tutorial by a named developer, Manish Hatwalne, comparing OAuth 2.0 with API keys for agentic AI.

OAuth vs. API Keys for Agentic AI ↗

What happened

• The article states that API keys have no built-in expiration mechanism and remain valid until explicitly revoked.
• The article describes OAuth Token Exchange (RFC 8693) as a standardized mechanism for exchanging tokens with different scopes, audiences and lifetimes.

Why it matters to Signicat

• Content is educational; it names no Signicat product and no competitor product. Its link to Descope's Agentic Identity Hub 3.0 is not stated in the excerpt.
• Agentic identity is a rising buyer concern; OAuth-based agent delegation is a standards-based framing that Signicat's authentication and orchestration offerings could be compared against.

3 of 3 facts verified against the source · confidence medium · claude-haiku-5-5