# Auth0 Blog

Company Updates, Technology Articles from Auth0

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Securing Your Newest Customer Channel with Auth for Personal Agents

DevFeed: [Securing Your Newest Customer Channel with Auth for Personal Agents](<https://devfeed.tech/articles/securing-your-newest-customer-channel-with-auth-for-personal-agents-142027.md>)

Original publisher: [Read original article](<https://auth0.com/blog/auth-for-personal-agents-beta-release/>)

Author: Karim Tantawy

Published: 2026-11-18T00:00:00Z

Content type: release

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [agentic browsing](<https://devfeed.tech/topics/agentic-browsing.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [auth](<https://devfeed.tech/tags/auth.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [beta](<https://devfeed.tech/tags/beta.md>), [channel](<https://devfeed.tech/tags/channel.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [identity](<https://devfeed.tech/tags/identity.md>), [join](<https://devfeed.tech/tags/join.md>), [like](<https://devfeed.tech/tags/like.md>), [muse](<https://devfeed.tech/tags/muse.md>), [personal](<https://devfeed.tech/tags/personal.md>), [personal-agent](<https://devfeed.tech/tags/personal-agent.md>), [personal-agent-protocol](<https://devfeed.tech/tags/personal-agent-protocol.md>), [personal-agents](<https://devfeed.tech/tags/personal-agents.md>), [poppy](<https://devfeed.tech/tags/poppy.md>), [program](<https://devfeed.tech/tags/program.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Poppy gives personal agents a way to identify themselves and act for customers through scoped, revocable access, avoiding shared passwords and blanket account access. Auth0 says its upcoming beta will support API and web browsing: brands register allowed agents by CIMD URL, customers sign in and consent through standard OAuth, and DPoP-bound tokens plus session checks let services verify and audit the agent separately from the user. The SDK is described as handling discovery metadata and agent-driven web sessions, with CLI setup and diagnostics. A browser playground can test discovery, sign-in, browsing, and conversation against a shop. The beta is coming soon and participation is by selection.

### Source excerpt

Auth0 brings identity to Personal Agents by adding support for the Personal Agent Protocol (Poppy). Verify agents like Muse, tie actions to real customers, and join the Beta Program.

## Building a Secure MCP (Model Context Protocol) Server with Auth0

DevFeed: [Building a Secure MCP (Model Context Protocol) Server with Auth0](<https://devfeed.tech/articles/building-a-secure-mcp-model-context-protocol-server-with-auth0-136615.md>)

Original publisher: [Read original article](<https://auth0.com/blog/building-secure-mcp-server-with-auth0/>)

Author: Kevin Kimani

Published: 2026-11-16T17:06:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [context](<https://devfeed.tech/tags/context.md>), [data](<https://devfeed.tech/tags/data.md>), [go](<https://devfeed.tech/tags/go.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [learn](<https://devfeed.tech/tags/learn.md>), [learn-how-to](<https://devfeed.tech/tags/learn-how-to.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model](<https://devfeed.tech/tags/model.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [server](<https://devfeed.tech/tags/server.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The guide builds a Go MCP server that uses Auth0 Authorization Code with PKCE to issue user-linked access tokens, then validates JWT signatures, issuer, audience, and expiry against Auth0 JWKS. Auth0 RBAC supplies department permissions; the server authorizes from the token's requested-and-approved `scope` claim, mapping `read:engineering` or `read:hr` to a department. It registers only that department's resources for each session and returns "resource not found" for cross-department reads to reduce information leakage. Missing or invalid tokens receive 401 with OAuth resource metadata; valid tokens without a required scope receive 403. The walkthrough also configures OAuth Protected Resource Metadata and demonstrates requests with cURL. It distinguishes Client Credentials as suitable for automated machine-to-machine pipelines, while choosing Authorization Code for deployments governed by a real user. Production follow-ups include token refresh, client-secret rotation, richer audit logging, and finer-grained authorization for more complex access patterns.

### Source excerpt

Learn how to build an MCP server in Go and secure it with Auth0 using OAuth 2.1, PKCE, and RBAC-backed scopes, so AI agents only see the data their user is authorized to access.

## Authentication and Authorization: What's New in .NET 11

DevFeed: [Authentication and Authorization: What's New in .NET 11](<https://devfeed.tech/articles/authentication-and-authorization-what-s-new-in-net-11-125616.md>)

Original publisher: [Read original article](<https://auth0.com/blog/authentication-and-authorization-what-s-new-in-net-11/>)

Author: Andrea Chiarelli

Published: 2026-11-09T00:00:00Z

Content type: release

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [.NET](<https://devfeed.tech/topics/net.md>), [ASP.NET Core](<https://devfeed.tech/topics/asp-net-core.md>), [SignalR](<https://devfeed.tech/topics/signalr.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Passkeys](<https://devfeed.tech/topics/passkeys.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>)

Tags: [asp-net](<https://devfeed.tech/tags/asp-net.md>), [asp-net-core](<https://devfeed.tech/tags/asp-net-core.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [net-11](<https://devfeed.tech/tags/net-11.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>), [what-s-new-in-net-11](<https://devfeed.tech/tags/what-s-new-in-net-11.md>)

### AI overview

.NET 11 adds targeted authentication and authorization refinements. SignalR can refresh a connection's identity in place: the client obtains a fresh token through its access-token provider, while the server rejects changes in subject; configure proxies to allow the new `/refresh` route, and pair refresh with `CloseOnAuthenticationExpiration` to close connections that fail to refresh. Custom authorization requirement attributes now work consistently across Minimal APIs, MVC, SignalR, and Blazor, though legacy MVC without endpoint routing retains its prior behavior. ASP.NET Core Identity can name known passkeys from authenticator identifiers and lets users rename unknown ones. Other changes include `TimeProvider` support for testable Identity time behavior, file-based `dotnet user-jwts`, and automatic TLS channel binding for Negotiate. The experimental Device Bound Session Credentials package was removed before RC2 because its implementation was incomplete.

### Source excerpt

Learn what's new in .NET 11 regarding authentication and authorization.

## Consumers are Ready for AI. Are Companies?

DevFeed: [Consumers are Ready for AI. Are Companies?](<https://devfeed.tech/articles/consumers-are-ready-for-ai-are-companies-116542.md>)

Original publisher: [Read original article](<https://auth0.com/blog/consumers-are-ready-for-ai-are-companies/>)

Author: Auth0 Team

Published: 2026-11-03T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Interactive AI Systems](<https://devfeed.tech/topics/interactive-ai-systems.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-commerce](<https://devfeed.tech/tags/agentic-commerce.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [auditability](<https://devfeed.tech/tags/auditability.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-systems](<https://devfeed.tech/tags/autonomous-systems.md>), [ciam](<https://devfeed.tech/tags/ciam.md>), [customer-experience](<https://devfeed.tech/tags/customer-experience.md>), [customer-identity](<https://devfeed.tech/tags/customer-identity.md>), [customer-journeys](<https://devfeed.tech/tags/customer-journeys.md>), [customers](<https://devfeed.tech/tags/customers.md>), [engineering-capacity](<https://devfeed.tech/tags/engineering-capacity.md>), [identity](<https://devfeed.tech/tags/identity.md>), [useful](<https://devfeed.tech/tags/useful.md>)

### AI overview

The excerpt reports a gap between companies' AI ambitions and delivery: 77.1% of surveyed North American organizations are building or have production AI agents, but only 22.1% say they are moving as quickly as desired. About 20% cite engineering capacity as the main delay, and just over 10% point to identity infrastructure that cannot support agent access patterns. Consumers' willingness to let AI act rises above 50% for most uses when they can approve or reverse actions; 37% are ready without that safeguard, including 7% for final decisions and action. The report argues that customer identity systems supporting agent authentication, authorization, auditability, and scale can help teams deliver useful, trusted experiences while reducing identity maintenance burdens. These findings come from surveys commissioned for Okta's 2026 Customer Identity Trends Report.

### Source excerpt

Brands are in a high-stakes race to introduce AI-assisted experiences that are useful, convenient, and trustworthy--identity can be an enabler or a hindrance.

## Who Will Consumers Trust to Act, Shop, and Pay on Their Behalf?

DevFeed: [Who Will Consumers Trust to Act, Shop, and Pay on Their Behalf?](<https://devfeed.tech/articles/who-will-consumers-trust-to-act-shop-and-pay-on-their-behalf-116546.md>)

Original publisher: [Read original article](<https://auth0.com/blog/who-will-consumers-trust-to-act-shop-pay-on-their-behalf/>)

Author: Auth0 Team

Published: 2026-11-03T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [agentic commerce fraud](<https://devfeed.tech/topics/agentic-commerce-fraud.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [trust](<https://devfeed.tech/topics/trust.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [account](<https://devfeed.tech/tags/account.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [acquisition](<https://devfeed.tech/tags/acquisition.md>), [actions](<https://devfeed.tech/tags/actions.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [addition](<https://devfeed.tech/tags/addition.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-commerce](<https://devfeed.tech/tags/agentic-commerce.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [convenient](<https://devfeed.tech/tags/convenient.md>), [need](<https://devfeed.tech/tags/need.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Retailers can reduce purchase friction while preparing for agentic commerce by matching security checks to the action and giving consumers control over AI activity. In a survey of 5,250 consumers, account creation before showing key information, slow login or verification, and repeated identity checks were cited as reasons for abandoning a task by 74%, 72%, and 71%, respectively. Only 6% were ready for AI to handle as much as possible, but most were willing to delegate lower-consequence actions when they could approve them first or reverse them. Retailers also report existing fraud challenges, including fake accounts, loyalty abuse, and account takeovers; agents and their APIs add risks. The text recommends linking agents to individual customers and using tightly scoped, time-limited credentials. It describes modern CIAM platforms as centralizing authorization, modeling agent identities, enforcing fine-grained permissions and audit trails, and supporting verification. Survey comparisons associate external identity platforms with less reported customer-experience harm and stronger AI production and timeline outcomes, though the text does not establish causation.

### Source excerpt

As AI agents evolve from answering questions to taking action, retailers need to deliver seamless experiences that are both convenient and secure.

## AI ambitions are blocked by identity debt

DevFeed: [AI ambitions are blocked by identity debt](<https://devfeed.tech/articles/ai-ambitions-are-blocked-by-identity-debt-116540.md>)

Original publisher: [Read original article](<https://auth0.com/blog/ai-ambitions-are-blocked-by-identity-debt/>)

Author: Auth0 Team

Published: 2026-11-03T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [audit](<https://devfeed.tech/tags/audit.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-systems](<https://devfeed.tech/tags/autonomous-systems.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [ciam](<https://devfeed.tech/tags/ciam.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-infrastructure](<https://devfeed.tech/tags/identity-infrastructure.md>), [japanese](<https://devfeed.tech/tags/japanese.md>)

### AI overview

The excerpt reports that 73% of surveyed Japanese developers and senior leaders say their organization has AI or agentic features in production (29%) or is building them (44%), yet fewer than 28% of active builders are delivering at their desired speed. Among delayed organizations, 23% cite identity infrastructure that cannot support agent access patterns as the main cause; among organizations that have not started, nearly 60% identify outdated identity infrastructure as the primary cause. The report says teams spend over 15% of engineering time on CIAM and points to capabilities including authentication, token vaults, MCP authorization, asynchronous authorization, agent-as-principal, and fine-grained authorization for RAG. It frames usable consumer controls, trust, security, and auditability as requirements for expanding AI-powered journeys.

### Source excerpt

Japanese brands' identity infrastructure is stalling rollout of agentic systems

## Moving Quickly Without Breaking Things

DevFeed: [Moving Quickly Without Breaking Things](<https://devfeed.tech/articles/moving-quickly-without-breaking-things-116543.md>)

Original publisher: [Read original article](<https://auth0.com/blog/moving-quickly-without-breaking-things/>)

Author: Auth0 Team

Published: 2026-11-03T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [trust](<https://devfeed.tech/topics/trust.md>), [okta](<https://devfeed.tech/topics/okta.md>), [ai regulation](<https://devfeed.tech/topics/ai-regulation.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-commerce](<https://devfeed.tech/tags/agentic-commerce.md>), [agentic-identity](<https://devfeed.tech/tags/agentic-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [audit](<https://devfeed.tech/tags/audit.md>), [auditability](<https://devfeed.tech/tags/auditability.md>), [auth](<https://devfeed.tech/tags/auth.md>), [customer-identity](<https://devfeed.tech/tags/customer-identity.md>), [europe](<https://devfeed.tech/tags/europe.md>), [identity](<https://devfeed.tech/tags/identity.md>), [regulators](<https://devfeed.tech/tags/regulators.md>), [transparency](<https://devfeed.tech/tags/transparency.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

European organizations are moving quickly to deploy AI agents, but only 17.5% say they are delivering at their desired speed, and consumer readiness for AI to make decisions or act is limited to 40%. The excerpt links deployment delays to customer identity challenges and says organizations need identity systems that support agent authentication, authorization, and auditing. It highlights delegated access, context security, interoperability, fine-grained authorization, audit trails, and identity verification as relevant capabilities, including for GDPR and EU AI Act requirements. Consumer trust varies: 40% feel more comfortable with AI acting for them than a year ago, while the source emphasizes clear controls and transparency and says no single measure addresses most consumers' concerns. Survey figures cited are for Germany and the UK.

### Source excerpt

As AI agents evolve from answering questions to taking action, customer identity enables the trust and transparency Europe's consumers and regulators demand.

## Secure and Convenient is the Real Killer App

DevFeed: [Secure and Convenient is the Real Killer App](<https://devfeed.tech/articles/secure-and-convenient-is-the-real-killer-app-116544.md>)

Original publisher: [Read original article](<https://auth0.com/blog/secure-and-convenient-is-the-real-killer-app/>)

Author: Auth0 Team

Published: 2026-11-03T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Digital Trust](<https://devfeed.tech/topics/digital-trust.md>), [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bot](<https://devfeed.tech/tags/bot.md>), [bot-traffic](<https://devfeed.tech/tags/bot-traffic.md>), [brute-force-attacks](<https://devfeed.tech/tags/brute-force-attacks.md>), [convenient](<https://devfeed.tech/tags/convenient.md>), [customers](<https://devfeed.tech/tags/customers.md>), [identity](<https://devfeed.tech/tags/identity.md>), [media](<https://devfeed.tech/tags/media.md>), [modernize](<https://devfeed.tech/tags/modernize.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [tech](<https://devfeed.tech/tags/tech.md>), [telecom](<https://devfeed.tech/tags/telecom.md>)

### AI overview

TMT companies face frequent customer identity attacks while customers expect strong security without difficult access: 93% of surveyed consumers said this helps them trust apps and websites. The text reports phishing or social engineering (40.5%), API abuse or unauthorized access (39.5%), and fake account creation (36.8%) among common challenges. Security friction also has business costs: 19% of surveyed TMT leaders and developers say they are losing customers because of it, while 25.2% lack visibility into security-driven abandonment. Developers using an external identity provider exclusively were more likely than those using in-house, legacy, or hybrid systems to report frictionless security and less likely to report customer losses or major negative effects on retention, usage, and purchasing. The text attributes this in part to platforms enabling authentication friction to be applied at moments that manage risk while limiting inconvenience. These are survey findings commissioned for Okta's 2026 Customer Identity Trends Report.

### Source excerpt

As customers seek out experiences that are both convenient and secure, telecom, media, and tech companies must modernize their identity platforms.

## Trust Puts Customer Identity in the Spotlight

DevFeed: [Trust Puts Customer Identity in the Spotlight](<https://devfeed.tech/articles/trust-puts-customer-identity-in-the-spotlight-116545.md>)

Original publisher: [Read original article](<https://auth0.com/blog/trust-puts-customer-identity-in-the-spotlight/>)

Author: Auth0 Team

Published: 2026-11-03T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [trust](<https://devfeed.tech/topics/trust.md>), [fake account fraud](<https://devfeed.tech/topics/fake-account-fraud.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [api](<https://devfeed.tech/tags/api.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [bot-traffic](<https://devfeed.tech/tags/bot-traffic.md>), [convenient](<https://devfeed.tech/tags/convenient.md>), [credential-stuffing](<https://devfeed.tech/tags/credential-stuffing.md>), [customer-experience](<https://devfeed.tech/tags/customer-experience.md>), [customer-identity](<https://devfeed.tech/tags/customer-identity.md>), [customer-journey](<https://devfeed.tech/tags/customer-journey.md>), [external](<https://devfeed.tech/tags/external.md>), [fake-accounts](<https://devfeed.tech/tags/fake-accounts.md>), [financial-services](<https://devfeed.tech/tags/financial-services.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Financial services organizations face frequent identity attacks while customers expect security that does not make access difficult: 93% of surveyed consumers said strong security without difficult access helps them trust apps and websites. Surveyed institutions reported threats including phishing or social engineering (43.4%), API abuse or unauthorized access (42.0%), and fake account creation (39.8%). Yet 17.6% of surveyed financial-sector developers and leaders said security friction was costing them customers, and 17.1% lacked visibility into whether security was driving abandonment. The brief reports that developers relying exclusively on an external identity provider were more likely to say security was not harming the customer experience, more likely to have implemented frictionless security, and less likely to report customer losses or poor visibility than developers using other approaches. These are survey findings; the excerpt does not establish that the platform choice caused the differences.

### Source excerpt

As customers seek out experiences that are both convenient and secure, financial services organizations must adopt modern, external identity platforms.

## Build an AI Wellbeing App with Fireworks and Fitbit via Auth0 Token Vault.

DevFeed: [Build an AI Wellbeing App with Fireworks and Fitbit via Auth0 Token Vault.](<https://devfeed.tech/articles/build-an-ai-wellbeing-app-with-fireworks-and-fitbit-via-auth0-token-vault-114135.md>)

Original publisher: [Read original article](<https://auth0.com/blog/build-an-ai-wellbeing-app-with-fireworks-fitbit-via-auth0-token-vault/>)

Author: Deepu K Sasidharan

Published: 2026-11-02T19:25:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [function calling](<https://devfeed.tech/topics/function-calling.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-sdk](<https://devfeed.tech/tags/ai-sdk.md>), [app](<https://devfeed.tech/tags/app.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [build](<https://devfeed.tech/tags/build.md>), [daily](<https://devfeed.tech/tags/daily.md>), [fitbit](<https://devfeed.tech/tags/fitbit.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [sleep](<https://devfeed.tech/tags/sleep.md>), [token](<https://devfeed.tech/tags/token.md>), [vault](<https://devfeed.tech/tags/vault.md>), [wellbeing](<https://devfeed.tech/tags/wellbeing.md>)

### AI overview

Daily Wellbeing retrieves the signed-in user's Google Health readings through Auth0 Token Vault, builds a latest-completed-day report with seven-day personal averages, and streams Fireworks suggestions only after the user explicitly chooses to share the summary. The report preserves recorded local dates, distinguishes missing values from zero, counts available comparison days, and skips data streams without permission. Users can review readings without inference. Fireworks receives a normalized summary through a server-side tool; its prompt limits advice to general wellbeing and excludes diagnosis and treatment, though the source cautions that prompt rules do not guarantee suitable responses. Setup requires a personal Google account linked to a health profile, Google Cloud OAuth configuration, an Auth0 tenant with Token Vault and Connected Accounts, and a Fireworks key and compatible model. Google OAuth test-mode refresh tokens expire after seven days, requiring reconnection.

### Source excerpt

Build Daily Wellbeing, a Next.js app that connects Fitbit through Auth0 Token Vault, compares your daily activity and sleep with your averages, and uses Fireworks to suggest what to try today.

## Beyond Infrastructure: The New Era of CIAM Innovation

DevFeed: [Beyond Infrastructure: The New Era of CIAM Innovation](<https://devfeed.tech/articles/beyond-infrastructure-the-new-era-of-ciam-innovation-114136.md>)

Original publisher: [Read original article](<https://auth0.com/blog/okta-named-a-leader-in-gartner-magic-quadrant-2026/>)

Author: Auth0 Team

Published: 2026-11-02T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [okta](<https://devfeed.tech/topics/okta.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-delegation](<https://devfeed.tech/tags/agent-delegation.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-commerce](<https://devfeed.tech/tags/agentic-commerce.md>), [agentic-identity](<https://devfeed.tech/tags/agentic-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [ciam](<https://devfeed.tech/tags/ciam.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [gartner-magic-quadranttm](<https://devfeed.tech/tags/gartner-magic-quadranttm.md>), [identity](<https://devfeed.tech/tags/identity.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [leader](<https://devfeed.tech/tags/leader.md>), [okta](<https://devfeed.tech/tags/okta.md>)

### AI overview

Okta says Gartner named it a Leader in the 2026 Magic Quadrant for Customer Identity and Access Management, and frames Auth0 as a way to support growth as customer journeys expand across apps and AI experiences. The text describes developer tools and integrations, authentication options intended to reduce sign-in friction, and protections against credential attacks. For B2B services, Tenancy-as-a-Service supports tenant controls and delegated administration; B2B Connect adds partner federation and provisioning over an existing authorization server, which Okta says can avoid a full platform migration. Agent identity features include governed identities and auditable activity; Cross App Access is listed as early access, while Token Vault and human-in-the-loop authorization are described as generally available. Regional and dedicated private-cloud options address data-residency needs. These are vendor claims; the excerpt does not independently assess performance or Gartner's comparative findings.

### Source excerpt

Okta has been named a Leader in Gartner® Magic Quadrant™ for Customer Identity and Access Management.

## Auth0-Powered SaaS Providers Unlock Growth with the Okta Integration Network

DevFeed: [Auth0-Powered SaaS Providers Unlock Growth with the Okta Integration Network](<https://devfeed.tech/articles/auth0-powered-saas-providers-unlock-growth-with-the-okta-integration-network-98261.md>)

Original publisher: [Read original article](<https://auth0.com/blog/auth0-powered-saas-providers-unlock-growth-okta-integration-network/>)

Author: Alex Silk

Published: 2026-10-23T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [okta](<https://devfeed.tech/topics/okta.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Endpoint security](<https://devfeed.tech/topics/endpoint-security.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [augment-code](<https://devfeed.tech/tags/augment-code.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [code](<https://devfeed.tech/tags/code.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [devices](<https://devfeed.tech/tags/devices.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [factory](<https://devfeed.tech/tags/factory.md>), [growth](<https://devfeed.tech/tags/growth.md>), [harness](<https://devfeed.tech/tags/harness.md>), [helps](<https://devfeed.tech/tags/helps.md>), [integration](<https://devfeed.tech/tags/integration.md>), [network](<https://devfeed.tech/tags/network.md>), [okta](<https://devfeed.tech/tags/okta.md>), [providers](<https://devfeed.tech/tags/providers.md>), [published](<https://devfeed.tech/tags/published.md>), [saas](<https://devfeed.tech/tags/saas.md>), [software](<https://devfeed.tech/tags/software.md>), [software-factory](<https://devfeed.tech/tags/software-factory.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

The excerpt presents Okta Integration Network publication as a way for Auth0-powered SaaS providers to offer enterprise identity features without building onboarding and security integrations from scratch. Jamf says Express Configuration replaced days of manual OIDC setup with a few-click, self-service SSO setup; Universal Logout lets it terminate administrator sessions across its platform in response to identity threats. Augment Code says Express Configuration similarly removed customer calls and manual setup, while its published integration supports Universal Logout, including partial coverage, for product-level session revocation directed by Okta. The article says the Auth0 capabilities were already built into Augment Code's stack, so publication did not require pausing its roadmap. It describes OIN publication and Express Submission as free, and lists onboarding support for SSO, Universal Logout, and SCIM. These are provider examples and claims from the supplied excerpt, not evidence of results across all OIN integrations.

### Source excerpt

Jamf manages and secures millions of Apple devices. Augment Code (now part of Harness) helps engineering teams deploy their software factory. Both are powered by Auth0 and published to the Okta Integration Network.

## Scaling AI Agent Identity with CIMD and Application Profiles in Auth0

DevFeed: [Scaling AI Agent Identity with CIMD and Application Profiles in Auth0](<https://devfeed.tech/articles/scaling-ai-agent-identity-with-cimd-and-application-profiles-in-auth0-96181.md>)

Original publisher: [Read original article](<https://auth0.com/blog/scaling-ai-agent-identity-cimd-application-profiles/>)

Author: Eric Wu

Published: 2026-10-22T00:00:00Z

Content type: release

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [application](<https://devfeed.tech/tags/application.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [caching](<https://devfeed.tech/tags/caching.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [credential-management](<https://devfeed.tech/tags/credential-management.md>), [identity](<https://devfeed.tech/tags/identity.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [scaling-ai](<https://devfeed.tech/tags/scaling-ai.md>), [security](<https://devfeed.tech/tags/security.md>), [security-for-ai](<https://devfeed.tech/tags/security-for-ai.md>)

### AI overview

Auth0 describes two CIMD registration modes for OAuth clients in AI-agent ecosystems. With manual pre-registration, an administrator submits a metadata URL; Auth0 retrieves and validates the metadata, then creates the client after approval, supporting tighter governance. Dynamic registration (Early Access) discovers and processes metadata during authorization for just-in-time registration, reducing manual provisioning. Auth0 says shared caching and more efficient metadata and key retrieval are designed to reduce database write pressure and latency while keeping changing metadata and signing keys current. Application Profiles (Early Access) centrally applies settings for dynamically registered CIMD clients, including refresh-token policies, DPoP, and Organizations, instead of configuring each client individually. CIMD addresses identification and registration; Profiles address centralized security and authorization controls.

### Source excerpt

Auth0 expands Client ID Metadata Document (CIMD) support with manual pre-registration and dynamic registration. Pair it with Application Profiles to manage security for AI agent clients at scale.

## Introducing Terraform Auth0 Modules

DevFeed: [Introducing Terraform Auth0 Modules](<https://devfeed.tech/articles/introducing-terraform-auth0-modules-95927.md>)

Original publisher: [Read original article](<https://auth0.com/blog/terraform-auth0-modules/>)

Author: Rajat Bajaj

Published: 2026-10-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account](<https://devfeed.tech/tags/account.md>), [acme](<https://devfeed.tech/tags/acme.md>), [actions](<https://devfeed.tech/tags/actions.md>), [addition](<https://devfeed.tech/tags/addition.md>), [apis](<https://devfeed.tech/tags/apis.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [custom](<https://devfeed.tech/tags/custom.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [mfa](<https://devfeed.tech/tags/mfa.md>), [module](<https://devfeed.tech/tags/module.md>), [modules](<https://devfeed.tech/tags/modules.md>), [roles](<https://devfeed.tech/tags/roles.md>), [set](<https://devfeed.tech/tags/set.md>), [sso](<https://devfeed.tech/tags/sso.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [up](<https://devfeed.tech/tags/up.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Terraform Auth0 Modules package a reusable B2B identity setup into the `b2b-saas-starter` module, built on the Auth0 Terraform Provider. One module block can create an application and RBAC-protected API, plus tenant-wide MFA and attack protection settings. Defaults include RBAC permissions in access tokens, PKCE and rotating refresh tokens, brute-force and breached-password protections, and TOTP MFA; inputs can override them. The module also accepts roles and permissions as data, validates undeclared role references during `terraform plan`, and can configure organization-specific SAML or OIDC SSO. Custom domains require DNS verification after the DNS record is live, typically across two applies; Terraform-managed DNS can allow one apply. Use Terraform 1.3 or later, an Auth0 tenant, and a Management API-authorized M2M application. Because tenant settings, MFA, and attack protection are shared, only one module instance should manage them; additional app instances can disable those management inputs.

### Source excerpt

Set up apps, APIs, roles, MFA, enterprise SSO, and custom domains on Auth0 with a single Terraform module.

## Your Agent Can Better Drive the Auth0 CLI with Agent Mode

DevFeed: [Your Agent Can Better Drive the Auth0 CLI with Agent Mode](<https://devfeed.tech/articles/your-agent-can-better-drive-the-auth0-cli-with-agent-mode-92758.md>)

Original publisher: [Read original article](<https://auth0.com/blog/your-agent-can-better-drive-auth0-cli-with-agent-mode/>)

Author: Bharath Natarajan

Published: 2026-10-20T16:02:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [cursor](<https://devfeed.tech/topics/cursor.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-mode](<https://devfeed.tech/tags/agent-mode.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [apps](<https://devfeed.tech/tags/apps.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [ci](<https://devfeed.tech/tags/ci.md>), [claude](<https://devfeed.tech/tags/claude.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding](<https://devfeed.tech/tags/coding.md>), [error](<https://devfeed.tech/tags/error.md>), [json](<https://devfeed.tech/tags/json.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [schema](<https://devfeed.tech/tags/schema.md>), [structured](<https://devfeed.tech/tags/structured.md>)

### AI overview

Auth0 CLI agent mode reduces trial and error for coding agents by providing structured JSON output, disabling prompts and color, and returning nonzero exit codes for real failures. Agents can discover commands with `auth0 commands --flat` or `--detailed`, inspect live OpenAPI payload schemas with `--schema`, submit JSON with `--data` for local field-level validation, and filter lists using `--query`. Errors include stable codes and reasons, field details, and--when returned by the API--an HTTP status. `--json-compact` reduces whitespace, and streaming commands use compact output automatically in agent mode. Documentation search needs no login; environment-based credentials can avoid keychain and disk use for CI or sandboxes. Agent mode is available in CLI versions newer than v1.38.0.

### Source excerpt

Explore Auth0 CLI agent mode: structured JSON, schema checks, predictable error recovery, and more built specifically for AI coding agents.

## Securing AI Agents with Auth0 CIMD and Token Exchange

DevFeed: [Securing AI Agents with Auth0 CIMD and Token Exchange](<https://devfeed.tech/articles/securing-ai-agents-with-auth0-cimd-and-token-exchange-91173.md>)

Original publisher: [Read original article](<https://auth0.com/blog/securing-ai-agents-with-auth0-cimd-token-exchange/>)

Author: Andre Hochstein

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [actor](<https://devfeed.tech/tags/actor.md>), [agent-context](<https://devfeed.tech/tags/agent-context.md>), [agent-delegation](<https://devfeed.tech/tags/agent-delegation.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-security](<https://devfeed.tech/tags/agentic-security.md>), [agentic-workflow](<https://devfeed.tech/tags/agentic-workflow.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [delegation](<https://devfeed.tech/tags/delegation.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [permission](<https://devfeed.tech/tags/permission.md>), [securing-ai](<https://devfeed.tech/tags/securing-ai.md>), [securing-ai-agents](<https://devfeed.tech/tags/securing-ai-agents.md>), [static](<https://devfeed.tech/tags/static.md>), [token](<https://devfeed.tech/tags/token.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

The article describes how Auth0 can preserve a third-party agent's permission ceiling and show who it acts for across downstream calls. Strict Mode requires PKCE and an explicit Client Grant, so permissive API policies cannot bypass the grant. CIMD uses an agent's metadata at a stable HTTPS URL to establish a client identity; the text says Auth0 currently supports pre-registration through the Management API or Dashboard, with dynamic CIMD registration planned for a future release. In the described flow, default permissions set the ceiling and user consent binds access to the user. RFC 8693 Token Exchange then combines the user's subject token with the agent's credentials to issue a delegated token carrying the user as `sub` and the agent as `act`. Client Grants limit permitted scopes, but not access to particular records; the article points to Auth0 FGA for relationship-based, record-level decisions.

### Source excerpt

AI agents break static authorization. Learn how Auth0 Strict Mode, CIMD, and Token Exchange keep a permission ceiling and a verifiable user-to-agent delegation chain.

## ID-JAG, Explained: The New OAuth Grant for Cross-App Access

DevFeed: [ID-JAG, Explained: The New OAuth Grant for Cross-App Access](<https://devfeed.tech/articles/id-jag-explained-the-new-oauth-grant-for-cross-app-access-91174.md>)

Original publisher: [Read original article](<https://auth0.com/blog/what-is-id-jag/>)

Author: Carla Urrea Stabile

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [saml](<https://devfeed.tech/topics/saml.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [company](<https://devfeed.tech/tags/company.md>), [consent](<https://devfeed.tech/tags/consent.md>), [console](<https://devfeed.tech/tags/console.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [flow](<https://devfeed.tech/tags/flow.md>), [identity](<https://devfeed.tech/tags/identity.md>), [idp](<https://devfeed.tech/tags/idp.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [resource](<https://devfeed.tech/tags/resource.md>)

### AI overview

An ID-JAG (Identity Assertion JWT Authorization Grant) is a short-lived, signed token an enterprise IdP issues after checking policy to authorize one app to access another app's API on a user's behalf. In the described OIDC flow, the user signs in once; the requesting app exchanges its ID token for an ID-JAG, then presents the grant to the resource app's authorization server to obtain an access token for API calls. This requires an existing trust relationship between that server and the enterprise IdP. The grant itself cannot call the API, and the exchange does not issue a refresh token. The article describes this as a non-interactive alternative to repeated consent prompts, with enterprise policy governing access. ID-JAG builds on OAuth Token Exchange (RFC 8693) and JWT Bearer grant (RFC 7523). The IETF specification is a working draft, and Auth0 Cross App Access is described as Early Access.

### Source excerpt

Learn what an ID-JAG (Identity Assertion JWT Authorization Grant) is, the cross-app access problem it solves, and how the flow works between a requesting app, resource app, and enterprise IdP.

## Securing the Front Door of Agentic Commerce: Four Channels, One Identity Layer

DevFeed: [Securing the Front Door of Agentic Commerce: Four Channels, One Identity Layer](<https://devfeed.tech/articles/securing-the-front-door-of-agentic-commerce-four-channels-one-identity-layer-90296.md>)

Original publisher: [Read original article](<https://auth0.com/blog/securing-the-front-door-of-agentic-commerce/>)

Author: Sandrino Di Mattia

Published: 2026-10-19T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [agentic commerce fraud](<https://devfeed.tech/topics/agentic-commerce-fraud.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Shopify](<https://devfeed.tech/topics/shopify.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-commerce](<https://devfeed.tech/tags/agentic-commerce.md>), [ai](<https://devfeed.tech/tags/ai.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [identity](<https://devfeed.tech/tags/identity.md>)

### AI overview

The article describes four channels for agent-driven commerce and argues that a shared identity layer can recognize agents, link them to customers, apply scoped permissions, and require stronger verification for higher-risk actions. It discusses embedded shopping agents, MCP connectors, commerce protocols such as UCP, and personal agents, with consent, security, and conversion as central concerns.

### Source excerpt

AI agents now shop for your customers in four channels. Learn how one identity layer recognizes each agent, links it to a real customer, scopes what it can do, and turns agent traffic into sales.

## On-Behalf-Of Is a Pattern. Token Exchange Is the Standard.

DevFeed: [On-Behalf-Of Is a Pattern. Token Exchange Is the Standard.](<https://devfeed.tech/articles/on-behalf-of-is-a-pattern-token-exchange-is-the-standard-88797.md>)

Original publisher: [Read original article](<https://auth0.com/blog/on-behalf-of-is-a-pattern-token-exchange-is-the-standard/>)

Author: Andrea Chiarelli

Published: 2026-10-16T10:38:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-delegation](<https://devfeed.tech/tags/ai-agent-delegation.md>), [api-access](<https://devfeed.tech/tags/api-access.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automated-decision-making](<https://devfeed.tech/tags/automated-decision-making.md>), [confused-deputy-problem](<https://devfeed.tech/tags/confused-deputy-problem.md>), [consent](<https://devfeed.tech/tags/consent.md>), [core](<https://devfeed.tech/tags/core.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [standard](<https://devfeed.tech/tags/standard.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

The article distinguishes the On-Behalf-Of architectural pattern, OAuth 2.0 Token Exchange (RFC 8693), and Microsoft's vendor-specific implementation. It explains how token exchange lets a middle-tier API call a downstream API with the user's identity without forwarding the user's original credential. It also discusses the gap in explicit user consent and auditing when AI agents act on a user's behalf, and recommends scoped per-agent credentials and detailed logs while standards work remains unsettled.

### Source excerpt

Find out the difference between On-Behalf-Of and OAuth Token Exchange, and why the two are often confused.

## Agentic Development: Time to Shift the Focus

DevFeed: [Agentic Development: Time to Shift the Focus](<https://devfeed.tech/articles/agentic-development-time-to-shift-the-focus-88796.md>)

Original publisher: [Read original article](<https://auth0.com/blog/agentic-development-time-to-shift-focus/>)

Author: Riccardo Cocetta

Published: 2026-10-16T00:00:00Z

Content type: opinion

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [development-process](<https://devfeed.tech/topics/development-process.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [coding](<https://devfeed.tech/tags/coding.md>), [risk](<https://devfeed.tech/tags/risk.md>), [time](<https://devfeed.tech/tags/time.md>), [validating](<https://devfeed.tech/tags/validating.md>)

### AI overview

The article argues that generating pull requests with AI agents is becoming a well-understood part of software development. It says teams should focus on choosing features that serve customers and fit the product, then validating generated code before shipping. The proposed approach varies validation depth according to the risk of each software component.

### Source excerpt

Agents can turn ideas into pull requests in almost no time. The hard part now is deciding what to build and validating that generated code is safe to ship. Here is a risk-based approach to both.

## One SDK, Multiple Platforms: Introducing the Auth0 SDK for Kotlin Multiplatform

DevFeed: [One SDK, Multiple Platforms: Introducing the Auth0 SDK for Kotlin Multiplatform](<https://devfeed.tech/articles/one-sdk-multiple-platforms-introducing-the-auth0-sdk-for-kotlin-multiplatform-87154.md>)

Original publisher: [Read original article](<https://auth0.com/blog/introducing-the-auth0-sdk-for-kotlin-multiplatform/>)

Author: Prince Mathew

Published: 2026-10-14T00:00:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [auth](<https://devfeed.tech/tags/auth.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [storage](<https://devfeed.tech/tags/storage.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

The article introduces Auth0's Kotlin Multiplatform SDK for implementing authentication in Android and iOS apps. It explains shared login and API calls, native secure credential storage, setup, and features such as passkeys, SSO, DPoP, and configurable retries.

### Source excerpt

Add login, logout, and secure token storage to iOS and Android apps using the Auth0 Kotlin Multiplatform SDK. Simplify cross-platform auth.

## Introducing the Auth0 SDK for TanStack Start

DevFeed: [Introducing the Auth0 SDK for TanStack Start](<https://devfeed.tech/articles/introducing-the-auth0-sdk-for-tanstack-start-86250.md>)

Original publisher: [Read original article](<https://auth0.com/blog/introducing-the-auth0-sdk-for-tanstack-start/>)

Author: Rengarajan R

Published: 2026-10-13T00:00:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [auth0](<https://devfeed.tech/tags/auth0.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

### AI overview

The article introduces @auth0/auth0-tanstack-start-react, an SDK for adding Auth0 authentication to TanStack Start apps. It explains setup, middleware and router context configuration, login and logout, protected routes, and server-side session access. It also notes support for organizations, MFA, API scope checks, and a passkeys example.

### Source excerpt

Meet the new Auth0 SDK for TanStack Start and learn how to use it to add authentication to your apps.

## Multi-Tenant SaaS Apps with Auth0 Organizations -- Part One

DevFeed: [Multi-Tenant SaaS Apps with Auth0 Organizations -- Part One](<https://devfeed.tech/articles/multi-tenant-saas-apps-with-auth0-organizations-part-one-84282.md>)

Original publisher: [Read original article](<https://auth0.com/blog/multi-tenant-saas-apps-with-auth0-organizations-part-one/>)

Author: Felix Colaci

Published: 2026-10-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [Duo](<https://devfeed.tech/topics/duo.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [b2b-saas](<https://devfeed.tech/tags/b2b-saas.md>), [database](<https://devfeed.tech/tags/database.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [saas](<https://devfeed.tech/tags/saas.md>)

### AI overview

This introductory installment explains how Auth0 Organizations support B2B SaaS identity across self-service and enterprise users. It covers organization-scoped login, enterprise identity provider discovery, tenant context switching, mapping organizations to application data, and authorization using organization roles and token claims.

### Source excerpt

If you are building a B2B SaaS product multi-tenancy is a foundational requirement. Your customers are companies, and each company expects its own isolated space. Getting this right early saves enormous pain later.

## Why Login Becomes an Identity System

DevFeed: [Why Login Becomes an Identity System](<https://devfeed.tech/articles/everybody-thinks-login-is-easy-until-it-is-not-66879.md>)

Original publisher: [Read original article](<https://auth0.com/blog/everybody-thinks-login-is-easy/>)

Author: Juan Cruz Martinez

Published: 2026-10-07T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [API](<https://devfeed.tech/topics/api.md>), [password spraying](<https://devfeed.tech/topics/password-spraying.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [credential-stuffing](<https://devfeed.tech/tags/credential-stuffing.md>), [has](<https://devfeed.tech/tags/has.md>), [identity](<https://devfeed.tech/tags/identity.md>), [it](<https://devfeed.tech/tags/it.md>), [login](<https://devfeed.tech/tags/login.md>)

### AI overview

A basic login form can work for a narrowly scoped application, but authentication grows into a broader identity system as users, organizations, recovery needs, sessions, and non-human actors add requirements. The article explains how account linking, recovery, session management, operational resilience, enterprise SSO, and delegated AI agent access create product and security decisions that a login screen alone cannot resolve. It recommends defining the limits of an initial implementation and using managed identity services or frameworks for protocol machinery while retaining ownership of application policy.

### Source excerpt

A login form can be small. The identity system behind it rarely stays that way.

[Next page](<https://devfeed.tech/sources/auth0-blog.md?cursor=WyIyMDI2LTEwLTA3VDAwOjAwOjAwKzAwOjAwIiwgImMzZGVlZTBjLTU5MjAtNDFmMS04YzRhLTYzMDBmNTE4YjVhNCJd>)