# OAuth 2.0

OAuth 2.0 is an industry-standard authorization protocol for web, desktop, mobile, and living-room-device applications.

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

## Ory Hydra: Open-source OAuth 2.0 server and OpenID Connect provider

DevFeed: [Ory Hydra: Open-source OAuth 2.0 server and OpenID Connect provider](<https://devfeed.tech/articles/ory-hydra-open-source-oauth-2-0-server-and-openid-connect-provider-134761.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/16/ory-hydra-oauth-server-open-source/>)

Author: Mirko Zorz

Published: 2026-11-16T06:00:29Z

Content type: article

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [applications](<https://devfeed.tech/tags/applications.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [client-apps](<https://devfeed.tech/tags/client-apps.md>), [cockroachdb](<https://devfeed.tech/tags/cockroachdb.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [docker](<https://devfeed.tech/tags/docker.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [github](<https://devfeed.tech/tags/github.md>), [hydra](<https://devfeed.tech/tags/hydra.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [keys](<https://devfeed.tech/tags/keys.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [news](<https://devfeed.tech/tags/news.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [ory](<https://devfeed.tech/tags/ory.md>), [passwords](<https://devfeed.tech/tags/passwords.md>), [server](<https://devfeed.tech/tags/server.md>), [software](<https://devfeed.tech/tags/software.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Ory Hydra issues and validates OAuth 2.0 and OpenID Connect tokens, registers clients, and manages signing keys while leaving usernames and passwords with an organization's existing identity system. At sign-in, it redirects users to a separate login and consent app, which verifies credentials and reports identity and consent to Hydra. Supported capabilities include authorization code with PKCE, client credentials, refresh tokens, device authorization, opaque access tokens with immediate revocation, introspection, and dynamic client registration. It runs on Linux, macOS, Windows, Docker, and Kubernetes; production databases include PostgreSQL 12+, MySQL 8+, and CockroachDB, while SQLite is limited to local development. The excerpt says Hydra sends summarized, anonymized telemetry that administrators can disable, and reports OpenID Foundation certification for v1.0.0 across five profiles.

### Source excerpt

Ory Hydra is an open-source OAuth 2.0 server and OpenID Connect provider. Ory built it to issue and validate tokens, register client applications, and manage the keys that sign those tokens. Hydra stores no usernames or passwords, so logins stay with whatever identity system an organization already runs. The OAuth specifications run to more than 400 pages, and a team building its own server has to get every one of them right. Hydra does that ... More -> The post Ory Hydra: Open-source OAuth 2.0 server and OpenID Connect provider appeared first on Help Net Security.

## Amazon WorkSpaces for AI Agents Adds Linux, Windows 11, and OAuth Support

DevFeed: [Amazon WorkSpaces for AI Agents Adds Linux, Windows 11, and OAuth Support](<https://devfeed.tech/articles/amazon-workspaces-for-ai-agents-adds-linux-windows-11-and-oauth-support-133421.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/desktop-and-application-streaming/amazon-workspaces-for-ai-agents-adds-linux-windows-11-and-oauth-support/>)

Author: Dave Jaskie

Published: 2026-11-13T22:06:17Z

Content type: release

Language: en

Sources: [Desktop and Application Streaming](<https://devfeed.tech/sources/desktop-and-application-streaming.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [gui-agents](<https://devfeed.tech/topics/gui-agents.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [agent-integration](<https://devfeed.tech/tags/agent-integration.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-end-user-computing](<https://devfeed.tech/tags/amazon-end-user-computing.md>), [amazon-workspaces](<https://devfeed.tech/tags/amazon-workspaces.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [end-user-computing](<https://devfeed.tech/tags/end-user-computing.md>), [linux](<https://devfeed.tech/tags/linux.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>), [windows-11](<https://devfeed.tech/tags/windows-11.md>)

### AI overview

Amazon WorkSpaces for AI agents adds Linux and Windows 11 fleets (Windows 11 requires BYOL), plus OAuth sign-in for MCP clients such as Kiro and Claude Code. The Agent Toolkit for AWS now includes a skill that explains session connections, connection modes, desktop tools, batching, forwarded MCP tools, and common errors. OAuth uses browser sign-in with an AWS identity; short-lived tokens renew automatically, while per-tool IAM permissions and CloudTrail logging remain in place. Existing SigV4 connections continue to work. Setup requires a configured WorkSpaces Applications stack and running fleet, suitable IAM permissions, Node.js, and a supported client. Features are available in Regions offering the WorkSpaces Applications MCP endpoint.

### Source excerpt

In June, we announced the general availability of Amazon WorkSpaces for AI agents. That launch gave your agents a managed way to operate the desktop applications your business runs on, including ERP clients, claims systems, engineering tools, and internal apps that were never built with an API. Since then, many of you have put agents [...]

## Crafty Microsoft Teams Booking Flow Disguises Device Code Phishing

DevFeed: [Crafty Microsoft Teams Booking Flow Disguises Device Code Phishing](<https://devfeed.tech/articles/crafty-microsoft-teams-booking-flow-disguises-device-code-phishing-133544.md>)

Original publisher: [Read original article](<https://www.huntress.com/blog/crafty-microsoft-teams-booking-flow-disguises-device-code-phishing>)

Author: Andrea Hatcher; Matt Poto; Lindsey O'Donnell-Welch

Published: 2026-11-12T14:00:00Z

Content type: article

Language: en

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

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Microsoft Teams](<https://devfeed.tech/topics/microsoft-teams.md>), [microsoft 365](<https://devfeed.tech/topics/microsoft-365.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account](<https://devfeed.tech/tags/account.md>), [actor](<https://devfeed.tech/tags/actor.md>), [adapting](<https://devfeed.tech/tags/adapting.md>), [booking](<https://devfeed.tech/tags/booking.md>), [code](<https://devfeed.tech/tags/code.md>), [device](<https://devfeed.tech/tags/device.md>), [device-code](<https://devfeed.tech/tags/device-code.md>), [device-code-phishing](<https://devfeed.tech/tags/device-code-phishing.md>), [flow](<https://devfeed.tech/tags/flow.md>), [lure](<https://devfeed.tech/tags/lure.md>), [meeting](<https://devfeed.tech/tags/meeting.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-teams](<https://devfeed.tech/tags/microsoft-teams.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [teams](<https://devfeed.tech/tags/teams.md>), [used](<https://devfeed.tech/tags/used.md>)

### AI overview

A spear-phishing email impersonating a construction-company executive led a victim through a realistic Teams meeting-booking flow that concealed device-code phishing. After the victim clicked Continue, the backend initiated a Microsoft device sign-in and displayed its code as a booking reference. Copying or confirming the reference copied the code and opened Microsoft's legitimate device-login page; entering it and completing any requested MFA authorized the attacker's session. The page then redirected to a Calendly booking page to preserve the appearance of a normal interaction. The phishing kit could restart the device-code flow if MFA was required and display a Microsoft-like popup for further action. Huntress contained the observed incident. The excerpt recommends verifying unexpected code prompts through known contacts, restricting or monitoring device-code authentication where unnecessary, using phishing-resistant MFA and identity-focused controls, and checking for unauthorized account changes after compromise.

### Source excerpt

Threat actors used a convincing Microsoft Teams meeting-booking lure to conceal device code phishing and trick victims into authorizing attacker access.

## Never Share Your Password Again -- The OAuth 2.0 Solution

DevFeed: [Never Share Your Password Again -- The OAuth 2.0 Solution](<https://devfeed.tech/articles/never-share-your-password-again-the-oauth-2-0-solution-124079.md>)

Original publisher: [Read original article](<https://stackoverflow.blog/2026/11/09/never-share-your-password-again-the-oauth-2-0-solution/>)

Author: Srikanth Srinivas

Published: 2026-11-09T20:50:38Z

Content type: article

Language: en

Sources: [Stack Overflow](<https://devfeed.tech/sources/stack-overflow-blog.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [pkce](<https://devfeed.tech/topics/pkce.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [passwords](<https://devfeed.tech/topics/passwords.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [X (Twitter)](<https://devfeed.tech/topics/twitter.md>)

Tags: [auth](<https://devfeed.tech/tags/auth.md>), [cc-by-sa](<https://devfeed.tech/tags/cc-by-sa.md>), [contributed](<https://devfeed.tech/tags/contributed.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [password](<https://devfeed.tech/tags/password.md>), [running-software](<https://devfeed.tech/tags/running-software.md>)

### AI overview

OAuth 2.0 lets a user grant a third-party app limited, revocable access without sharing their password. In the described Authorization Code with PKCE flow, the app redirects the user to the authorization server, which authenticates them and returns a short-lived, single-use code. The app exchanges that code server-to-server for a token, then uses the token to call the API. The text explains that state helps prevent CSRF, PKCE makes an intercepted code useless without the verifier, and a pre-registered exact redirect URI limits code redirection. Scopes bound access to approved permissions; tokens expire and can be revoked. The excerpt says PKCE is required for mobile apps and SPAs and strongly recommended elsewhere.

### Source excerpt

Founded in 2008, Stack Overflow's public platform is used by nearly everyone who codes to learn, share their knowledge, collaborate, and build their careers.

## Grok Bot has a Tailscale integration--and now you can, too

DevFeed: [Grok Bot has a Tailscale integration--and now you can, too](<https://devfeed.tech/articles/grok-bot-has-a-tailscale-integration-and-now-you-can-too-125768.md>)

Original publisher: [Read original article](<https://tailscale.com/blog/oauth-apps-ga>)

Author: Sam Linville

Published: 2026-11-09T20:30:00Z

Content type: release

Language: en

Sources: [Tailscale](<https://devfeed.tech/sources/blog-on-tailscale.md>)

Topics: [tailscale](<https://devfeed.tech/topics/tailscale.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Bot](<https://devfeed.tech/topics/bot.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [grok-bot](<https://devfeed.tech/tags/grok-bot.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-servers](<https://devfeed.tech/tags/mcp-servers.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [tailscale](<https://devfeed.tech/tags/tailscale.md>)

### AI overview

Tailscale OAuth apps let agents join a user's tailnet through OAuth 2.0 without exposing private services publicly or sharing keys. Unlike existing OAuth clients that create tag-owned devices under a shared identity, OAuth app devices carry the authorizing user's identity and remain subject to tailnet policies, audit logs, and device quotas. The excerpt describes Grok Bot accessing private MCP servers: Premium and Enterprise plans can use a custom device posture attribute to restrict it to designated resources, while other plans can apply a device tag after authentication and use tag-based rules. An example policy allows engineers' regular devices to reach production databases while their Grok Bot devices reach only MCP servers.

### Source excerpt

Agent access without exposing your network -- Tailscale OAuth apps are now GA.

## Let each customer bring their own OAuth app with WorkOS Pipes

DevFeed: [Let each customer bring their own OAuth app with WorkOS Pipes](<https://devfeed.tech/articles/let-each-customer-bring-their-own-oauth-app-with-workos-pipes-121081.md>)

Original publisher: [Read original article](<https://workos.com/blog/pipes-bring-your-own-oauth-app>)

Author: WorkOS

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

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [backend](<https://devfeed.tech/tags/backend.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [custom](<https://devfeed.tech/tags/custom.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [data-integration](<https://devfeed.tech/tags/data-integration.md>), [docs](<https://devfeed.tech/tags/docs.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [secret](<https://devfeed.tech/tags/secret.md>), [widget](<https://devfeed.tech/tags/widget.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS Pipes organization credentials let each customer register and control its own OAuth app. This is configured per provider for the whole environment: once enabled, every organization must supply a client ID and secret before its members can connect. Admins can configure credentials through the permission-gated PipesAdmin widget or API; members use the standard Pipes widget, and each member still authorizes a personal connection scoped to their organization. Setup requires creating the OAuth app, registering Pipes' redirect URI, saving the credential pair, choosing scopes, and enabling the provider. Rotation replaces the stored secret; retirement happens in the provider's console, while disabling a provider only hides it from that organization's members. The excerpt notes there is no documented remove-credentials control and no Node SDK method for the configuration API.

### Source excerpt

When a provider needs each customer's own OAuth app, the Pipes Admin widget lets their admin register it, rotate the secret and retire it without your help.

## Managed Better Auth is now an OAuth provider, with MCP support

DevFeed: [Managed Better Auth is now an OAuth provider, with MCP support](<https://devfeed.tech/articles/managed-better-auth-is-now-an-oauth-provider-with-mcp-support-113443.md>)

Original publisher: [Read original article](<https://neon.com/blog/managed-better-auth-oauth-provider-mcp>)

Author: Shridhar Deshmukh

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

Content type: release

Language: en

Sources: [Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [pkce](<https://devfeed.tech/topics/pkce.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [clients](<https://devfeed.tech/tags/clients.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [product](<https://devfeed.tech/tags/product.md>), [server](<https://devfeed.tech/tags/server.md>)

### AI overview

Managed Better Auth's OAuth Provider plugin makes an auth instance an OAuth 2.1 authorization server for companion apps and MCP clients. In Managed Better Auth, the OAuth provider and MCP support are configured together: add login and consent page URLs and an MCP server URL. Neon runs discovery, keys, token issuance and refresh, and client onboarding; developers run the login and consent pages and the API or MCP server. The `@neon/oauth` SDK verifies MCP tokens' signature, issuer and audience, and provides adapters for Hono, Next.js and `node:http`. MCP clients can onboard with Client ID Metadata Documents by default, while older clients may use optional dynamic registration. OAuth configuration is per database branch; branches share signing keys but have distinct issuers, which issuer-pinning verifiers use to reject preview tokens in production. The feature is available now and included in all Neon plans; the Free plan covers up to 60,000 monthly active users.

### Source excerpt

Managed Better Auth now supports the OAuth Provider plugin. It turns your auth instance into an OAuth 2.1 authorization server, so other apps and MCP clients can sign users in with your app.

## Google Adopts DPoP to Strengthen OAuth 2.0 Against Token Theft and Replay Attacks

DevFeed: [Google Adopts DPoP to Strengthen OAuth 2.0 Against Token Theft and Replay Attacks](<https://devfeed.tech/articles/google-adopts-dpop-to-strengthen-oauth-2-0-against-token-theft-and-replay-attacks-106786.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/google-dpop-oauth2/>)

Author: Sergio De Simone

Published: 2026-10-29T19:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>)

Tags: [adversary](<https://devfeed.tech/tags/adversary.md>), [adversary-in-the-middle-aitm](<https://devfeed.tech/tags/adversary-in-the-middle-aitm.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-workflows](<https://devfeed.tech/tags/agent-workflows.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [browser](<https://devfeed.tech/tags/browser.md>), [client](<https://devfeed.tech/tags/client.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [credential-theft](<https://devfeed.tech/tags/credential-theft.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [development](<https://devfeed.tech/tags/development.md>), [google](<https://devfeed.tech/tags/google.md>), [google-dpop-oauth2](<https://devfeed.tech/tags/google-dpop-oauth2.md>), [news](<https://devfeed.tech/tags/news.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [proof-of-possession](<https://devfeed.tech/tags/proof-of-possession.md>), [security](<https://devfeed.tech/tags/security.md>), [theft](<https://devfeed.tech/tags/theft.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

Google OAuth supports DPoP for refresh tokens, binding them to a client-generated asymmetric key so a stolen token cannot be replayed without the private key. Access tokens remain bearer tokens; the text says applying DPoP to each request would add cryptographic verification overhead. Clients must manage keys, timestamps, nonces, HTTP headers and DPoP proof JWTs. DPoP does not protect web session cookies; Google and WICG are developing DBSC to bind browser cookies to device hardware. For multi-agent delegation, the text points to Google Cloud STS to exchange an upstream token for a short-lived federated token bound to the next agent's key. Because browser-held keys remain exposed to client-side misuse, the cited IETF guidance recommends a Backend-for-Frontend pattern; a zero-persistence approach is also proposed where server infrastructure is unavailable.

### Source excerpt

Google's OAuth Platform has recently introduces support for Demonstrating Proof-of-Possession (DPoP), an OAuth 2.0 security mechanism designed to mitigate token theft and replay attacks. By Sergio De Simone

## Apache Polaris with Spark 4: REST Catalog, OAuth, and Credential Vending

DevFeed: [Apache Polaris with Spark 4: REST Catalog, OAuth, and Credential Vending](<https://devfeed.tech/articles/apache-polaris-with-spark-4-rest-catalog-oauth-and-credential-vending-102845.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/apache-polaris-with-spark-4-rest-catalog-oauth-and-credential-vending/>)

Author: Alex Merced

Published: 2026-10-27T18:56:45Z

Content type: tutorial

Language: en

Sources: [Dremio](<https://devfeed.tech/sources/dremio.md>)

Topics: [Apache Spark](<https://devfeed.tech/topics/spark.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [connect](<https://devfeed.tech/tags/connect.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [dremio-blog-open-data-insights](<https://devfeed.tech/tags/dremio-blog-open-data-insights.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [rest](<https://devfeed.tech/tags/rest.md>), [scopes](<https://devfeed.tech/tags/scopes.md>), [spark](<https://devfeed.tech/tags/spark.md>), [storage](<https://devfeed.tech/tags/storage.md>), [verify](<https://devfeed.tech/tags/verify.md>)

### AI overview

The excerpt gives a versioned recipe for connecting Spark 4 to Apache Polaris 1.8 as an Iceberg REST catalog: align Polaris client JARs with the documented compatibility matrix, configure OAuth client credentials and scope, set the warehouse and vended-credential header, and map temporary credentials into the storage FileIO. A namespace and managed-table write/read smoke test checks catalog and object-store access; metadata success with S3 AccessDenied points to credentials not reaching or being applied by the FileIO. Polaris vends credentials only for physical tables managed under its storage rules, not generic Iceberg tables. The excerpt also recommends checking driver, executor, and monitoring logs for exposed OAuth secrets or temporary credentials, and validating networking and IAM permissions before a staged rollout. Exact property names and non-AWS behavior depend on the documented client and cloud configuration.

### Source excerpt

Connect Spark 4 to Apache Polaris with the Iceberg REST catalog, OAuth credentials, catalog scopes, and storage credential vending, then verify writes. The post Apache Polaris with Spark 4: REST Catalog, OAuth, and Credential Vending appeared first on Dremio.

## Stop Trusting the OAuth Email: How One Missing Check Enables Account Takeover in 2026

DevFeed: [Stop Trusting the OAuth Email: How One Missing Check Enables Account Takeover in 2026](<https://devfeed.tech/articles/stop-trusting-the-oauth-email-how-one-missing-check-enables-account-takeover-in-2026-99230.md>)

Original publisher: [Read original article](<https://hackernoon.com/stop-trusting-the-oauth-email-how-one-missing-check-enables-account-takeover-in-2026?source=rss>)

Author: viodex

Published: 2026-10-25T13:00:02Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [trust](<https://devfeed.tech/topics/trust.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [MFA](<https://devfeed.tech/topics/mfa.md>), [password reset](<https://devfeed.tech/topics/password-reset.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [cves](<https://devfeed.tech/tags/cves.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [email](<https://devfeed.tech/tags/email.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-authentication](<https://devfeed.tech/tags/oauth-authentication.md>), [oauth-vulnerabilities](<https://devfeed.tech/tags/oauth-vulnerabilities.md>), [security](<https://devfeed.tech/tags/security.md>), [trust](<https://devfeed.tech/tags/trust.md>), [verification](<https://devfeed.tech/tags/verification.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

OAuth login can bypass an application's email verification or enable account takeover when the application treats a provider's email claim as proof of ownership without checking its verification status and enforcing its own linking rules. The article describes varied outcomes with Discord OAuth: some clients reject unverified identities, some preserve their unverified state, and others accept them as verified. It cites Nhost's use of a nonempty email field instead of Discord's `verified` value, and a Better Auth flaw that checked the provider's verified-email claim but not the existing local account's verification state. Risks described include blind linking, unauthorized access, pre-account takeover, and privilege escalation, depending on the application's flows. The recommended safeguards are to understand each provider's guarantees, check its reliable verification status, keep provider and local verification states distinct, and require proof of account ownership before linking identities.

### Source excerpt

Explore OAuth Verification Trust Mismatch, a security issue caused by mismatch between OAuth providers and client applications

## The Current Landscape of OAuth Attacks

DevFeed: [The Current Landscape of OAuth Attacks](<https://devfeed.tech/articles/the-current-landscape-of-oauth-attacks-96031.md>)

Original publisher: [Read original article](<https://unit42.paloaltonetworks.com/current-landscape-oauth-attacks/>)

Author: Ria Bhatia

Published: 2026-10-22T17:00:25Z

Content type: article

Language: en

Sources: [Unit 42](<https://devfeed.tech/sources/unit-42.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [ai-assisted attacks](<https://devfeed.tech/topics/ai-assisted-attacks.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [ai](<https://devfeed.tech/tags/ai.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [credential-based-attacks](<https://devfeed.tech/tags/credential-based-attacks.md>), [general](<https://devfeed.tech/tags/general.md>), [insights](<https://devfeed.tech/tags/insights.md>), [mfa](<https://devfeed.tech/tags/mfa.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [threats](<https://devfeed.tech/tags/threats.md>)

### AI overview

OAuth phishing targets the authorization step after users authenticate, so stolen access or refresh tokens can bypass MFA and persist through password resets. The article groups attacks into account hijacking, permission hijacking, and malicious redirects, describing device-code and authorization-code abuse, deceptive consent screens, and unsafe redirect handling. It also reports attackers using evasive browser scripts, phishing-as-a-service templates, and LLM-assisted brand impersonation. Recommended controls include routing third-party consent through administrators, blocking vague or impersonating apps and excessive scopes, monitoring authorization-code clipboard activity, and continuously auditing redirect URIs. Token lifetimes, IdP safeguards, and OAuth implementations vary; the article notes that protections are decentralized and some smaller providers may have weaker validation.

### Source excerpt

Unit 42 explores modern OAuth threats and actionable steps organizations can take to protect their environments. The post The Current Landscape of OAuth Attacks appeared first on Unit 42.

## OAuth for AI agents: What four extensions cover, and the gaps they leave

DevFeed: [OAuth for AI agents: What four extensions cover, and the gaps they leave](<https://devfeed.tech/articles/oauth-for-ai-agents-what-four-extensions-cover-and-the-gaps-they-leave-92961.md>)

Original publisher: [Read original article](<https://workos.com/blog/oauth-for-ai-agents-rar-dpop-cimd-transaction-tokens>)

Author: WorkOS

Published: 2026-10-21T14:24:43Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>)

Tags: [2013](<https://devfeed.tech/tags/2013.md>), [2023](<https://devfeed.tech/tags/2023.md>), [2026](<https://devfeed.tech/tags/2026.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [actions](<https://devfeed.tech/tags/actions.md>), [administrator](<https://devfeed.tech/tags/administrator.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>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [problems](<https://devfeed.tech/tags/problems.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [transaction](<https://devfeed.tech/tags/transaction.md>)

### AI overview

RAR can express structured permissions, DPoP binds a token to a key, and CIMD identifies a client through a metadata URL; Transaction Tokens carry identity and authorization context within one trust domain. These extensions address parts of authorization at grant time, but the cited gap analysis says none standardizes binding consent to an agent's original intent, verifying delegation lineage across hops, or revoking all of a principal's grants at once. The draft suggests application-level task records and consent evidence, per-hop token exchange and narrower grants, and a per-principal/client revocation epoch checked by resource servers, with short token lifetimes as backup. These measures require application enforcement; the draft's proposed extensions remain future work.

### Source excerpt

RAR, DPoP, CIMD and Transaction Tokens get cited as the answer for AI agents. What each one actually binds, and three problems none of them solves yet.

## Bring Your Own IdP to Harness MCP | OAuth Proxy Mode

DevFeed: [Bring Your Own IdP to Harness MCP | OAuth Proxy Mode](<https://devfeed.tech/articles/bring-your-own-idp-to-harness-mcp-oauth-proxy-mode-92574.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/bring-your-own-identity-provider-to-harness-mcp>)

Author: Piyush Patel

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

Content type: article

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [pkce](<https://devfeed.tech/topics/pkce.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>)

Tags: [aes](<https://devfeed.tech/tags/aes.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>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-developer](<https://devfeed.tech/tags/ai-developer.md>), [blog](<https://devfeed.tech/tags/blog.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [harness](<https://devfeed.tech/tags/harness.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [idp](<https://devfeed.tech/tags/idp.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-oauth](<https://devfeed.tech/tags/mcp-oauth.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [static](<https://devfeed.tech/tags/static.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

OAuth proxy mode lets a self-hosted Harness MCP server accept a developer's company identity-provider token while calling Harness with that developer's linked HarnessID token. At sign-in, the broker redirects through the company IdP and HarnessID; the server stores HarnessID tokens encrypted, while the IDE receives the company token and a broker-issued refresh token. For each request, the server checks the company token's signature, issuer, audience, and expiry, then uses or refreshes the user's HarnessID token. A failed link or revoked refresh token returns 401 and requires sign-in again; the server does not fall back to shared credentials. The excerpt describes per-leg S256 PKCE, server-held client secrets, AES-256-GCM encrypted token storage, restricted callback URLs, and optional TLS-protected Redis storage across pods. Harness RBAC and audit logs apply to the individual user. Enabling the mode requires contacting Harness support.

### Source excerpt

Learn how Harness MCP OAuth proxy mode enables enterprise developers to use their own identity provider without static tokens or shared credentials. | Blog

## Multi-Tenant OAuth for AI Agents: How to Store a Credential for Every Customer

DevFeed: [Multi-Tenant OAuth for AI Agents: How to Store a Credential for Every Customer](<https://devfeed.tech/articles/multi-tenant-oauth-for-ai-agents-how-to-store-a-credential-for-every-customer-90757.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/multi-tenant-oauth-for-ai-agents>)

Author: Swytchcode Team

Published: 2026-10-20T15:07:31.919507Z

Content type: article

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>)

Tags: [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>), [apis](<https://devfeed.tech/tags/apis.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [github](<https://devfeed.tech/tags/github.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [slack](<https://devfeed.tech/tags/slack.md>)

### AI overview

The article explains how to implement customer-specific OAuth credentials for AI agents that connect to services such as Slack and GitHub. It recommends a hosted consent flow, storing each grant against the customer ID, passing that tenant ID with every call, and limiting scopes. It compares Nango, Composio, Arcade, and Pipedream Connect, and describes Swytchcode's role in executing calls with existing grants. It also discusses cross-tenant access risks, policy controls, retries, and audit logging.

### Source excerpt

Multi-tenant OAuth means one stored grant per customer, not one token in a .env file. If every customer connects their own Slack or GitHub, you need a hosted connect flow, a credential stored against their ID, and every call tagged with whose account it used. Here is who does what.

## What is Enterprise-Managed Authorization (EMA)?

DevFeed: [What is Enterprise-Managed Authorization (EMA)?](<https://devfeed.tech/articles/what-is-enterprise-managed-authorization-ema-91181.md>)

Original publisher: [Read original article](<https://workos.com/blog/what-is-enterprise-managed-authorization>)

Author: WorkOS

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

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [can](<https://devfeed.tech/tags/can.md>), [consent](<https://devfeed.tech/tags/consent.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [managed](<https://devfeed.tech/tags/managed.md>), [screen](<https://devfeed.tech/tags/screen.md>), [what-is](<https://devfeed.tech/tags/what-is.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Enterprise-Managed Authorization (EMA) lets an identity provider (IdP) approve an AI agent's access to an app on an employee's behalf, replacing repeated per-user consent screens for configured connections. The agent signs in through SSO, requests a short-lived ID-JAG from the IdP, and presents it to the app's authorization server, which verifies it and issues a normal OAuth access token. IT can govern access through existing groups and roles; removing a user stops new ID-JAGs, while already-issued access tokens remain valid until expiry. EMA requires the IdP, agent, and app to support the flow and trust one another. The article says support is still narrow, the ID-JAG specification is a draft, and many internal APIs, databases, and CLIs remain outside its coverage. EMA governs app access and scopes, not approval of individual actions.

### Source excerpt

How your identity provider can grant AI agents access to work apps, without a consent screen for every app and every agent.

## Google OAuth DPoP for refresh tokens: What it protects and how to adopt

DevFeed: [Google OAuth DPoP for refresh tokens: What it protects and how to adopt](<https://devfeed.tech/articles/google-oauth-dpop-for-refresh-tokens-what-it-protects-and-how-to-adopt-91179.md>)

Original publisher: [Read original article](<https://workos.com/blog/google-oauth-dpop-refresh-tokens>)

Author: WorkOS

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

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Server-side vs Client-side OAuth2 Flows](<https://devfeed.tech/topics/server-side-vs-client-side-oauth2-flows.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [adopting](<https://devfeed.tech/tags/adopting.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [adversary](<https://devfeed.tech/tags/adversary.md>), [agent](<https://devfeed.tech/tags/agent.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [build](<https://devfeed.tech/tags/build.md>), [can](<https://devfeed.tech/tags/can.md>), [client](<https://devfeed.tech/tags/client.md>), [google](<https://devfeed.tech/tags/google.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [key](<https://devfeed.tech/tags/key.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [refresh](<https://devfeed.tech/tags/refresh.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Google's DPoP support binds refresh tokens to a client key, making a stolen refresh token unusable without the private key; access tokens remain ordinary Bearer tokens, typically valid for an hour or less. Adoption requires a key pair, per-request proofs, nonce tracking, and a retry on HTTP 400 nonce challenges. Google recommends DPoP across three browser-app architectures, but its token exchange example requires a client secret, so a browser-only SPA needs a confidential backend. Binding adds defense in depth for server-held tokens. It does not stop an attacker running script in the browser from using the key or stealing an access token. Multi-agent chains need separate keys and tokens per hop; Google's consumer OAuth endpoint lacks RFC 8693 token exchange, while its Cloud STS is recommended for federated workloads. The article says native and mobile support is not addressed in Google's materials.

### Source excerpt

Google now binds OAuth refresh tokens to a client key with DPoP; access tokens stay Bearer. What that protects, what to build, and who can use it.

## Announcing DPoP Support for Google OAuth: Securing Refresh Tokens

DevFeed: [Announcing DPoP Support for Google OAuth: Securing Refresh Tokens](<https://devfeed.tech/articles/announcing-dpop-support-for-google-oauth-securing-refresh-tokens-88204.md>)

Original publisher: [Read original article](<https://developers.googleblog.com/announcing-dpop-support-for-google-oauth-securing-refresh-tokens/>)

Author: Sergei Akulich; Brian Daugherty

Published: 2026-10-16T02:29:55.043485Z

Content type: article

Language: en

Sources: [Google Developers Blog](<https://devfeed.tech/sources/google-developers-blog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [adversary-in-the-middle-aitm](<https://devfeed.tech/tags/adversary-in-the-middle-aitm.md>), [agent-identities](<https://devfeed.tech/tags/agent-identities.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [infostealer](<https://devfeed.tech/tags/infostealer.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [refresh](<https://devfeed.tech/tags/refresh.md>), [security](<https://devfeed.tech/tags/security.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Google's OAuth platform supports DPoP binding for refresh tokens, cryptographically tying them to a client key pair to reduce theft and replay risks. Short-lived access tokens remain standard bearer tokens to avoid per-request verification overhead. For delegation in multi-agent or MCP workloads, the article recommends Google Cloud STS to issue short-lived federated tokens bound to each agent's key.

### Source excerpt

Google OAuth Platform now supports DPoP (Demonstrating Proof-of-Possession) to sender-constrain refresh tokens, neutralizing Infostealer malware and adversary-in-the-middle attacks. By cryptographically binding long-lived refresh tokens while maintaining short-lived access tokens as standard Bearer tokens, developers achieve robust credential security without incurring high-QPS API performance overhead. Additionally, developers integrating multi-agent or Model Context Protocol (MCP) workloads can use Google Cloud Secure Token Service (STS) to handle secure token delegation across agent chains.

## Vercel Connect adds Enterprise-Managed Authorization

DevFeed: [Vercel Connect adds Enterprise-Managed Authorization](<https://devfeed.tech/articles/vercel-connect-adds-enterprise-managed-authorization-88230.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-connect-adds-enterprise-managed-authorization>)

Author: Hedi Zandi

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

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [consent](<https://devfeed.tech/tags/consent.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [scopes](<https://devfeed.tech/tags/scopes.md>), [slack](<https://devfeed.tech/tags/slack.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Connect has added public beta support for Enterprise-Managed Authorization. It lets apps and agents access supported services on behalf of signed-in users, with administrators managing access through an identity provider and apps requesting scoped tokens. The release also supports Cross-App Access for MCP authorization through EMA.

### Source excerpt

Vercel Connect now supports Enterprise-Managed Authorization (EMA) in public beta. Your apps and agents can access supported services on behalf of signed-in users without separate consent prompts for each service. Here's how access works: Admin-managed access: Administrators can grant or revoke access to supported services through the identity provider. Corporate sign-in: Users sign into your app with their corporate account through a compatible identity provider such as Okta. Scoped tokens: Your app requests the scopes it needs, and Connect handles token exchange, caching, and renewal. Access is limited to approved scopes and the user's existing service permissions. If your app uses Vercel Passport, you can request a token for Slack's Model Context Protocol (MCP) server with the signed-in user's identity: type: embedded-entry-inline id: 1T9cFkjaRDDmRFQ5bWVmD6 Connect supports Cross-App Access (XAA), including its use for MCP authorization through EMA. Follow the Vercel Connect EMA setup guide to configure your identity provider and services and enable EMA on their Connect connectors. Read more

## Three OAuth account takeovers, one bug: Auto-linking by email

DevFeed: [Three OAuth account takeovers, one bug: Auto-linking by email](<https://devfeed.tech/articles/three-oauth-account-takeovers-one-bug-auto-linking-by-email-85480.md>)

Original publisher: [Read original article](<https://workos.com/blog/oauth-auto-link-email-account-takeover>)

Author: WorkOS

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

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [password reset](<https://devfeed.tech/topics/password-reset.md>)

Tags: [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>)

### AI overview

The article examines three account-takeover vulnerabilities in OAuth account linking: Pingvin Share X accepted unverified provider email, Better Auth failed to verify the local account's email, and AshAuthentication did not compare the provider email with the matched account. It recommends checking identities by issuer and subject, verifying email claims on both sides, requiring the user to prove access to an existing account when needed, preserving account recovery data, and making authentication callback checks fail closed.

### Source excerpt

Pingvin Share X, Better Auth and AshAuthentication each attached a stranger's OAuth sign-in to someone else's account. Here's how each check failed and what a safe linking decision looks like.

## OAuth 2.0 vs OpenID Connect: What's the Difference and Which Do You Need?

DevFeed: [OAuth 2.0 vs OpenID Connect: What's the Difference and Which Do You Need?](<https://devfeed.tech/articles/oauth-2-0-vs-openid-connect-what-s-the-difference-and-which-do-you-need-85536.md>)

Original publisher: [Read original article](<https://deanhume.com/oauth-2-0-vs-openid-connect/>)

Author: Dean Hume

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

Content type: article

Language: en

Sources: [Dean Hume](<https://devfeed.tech/sources/dean-hume.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [pkce](<https://devfeed.tech/topics/pkce.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.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>), [backend](<https://devfeed.tech/tags/backend.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [callback](<https://devfeed.tech/tags/callback.md>), [code-challenge](<https://devfeed.tech/tags/code-challenge.md>), [database](<https://devfeed.tech/tags/database.md>), [google](<https://devfeed.tech/tags/google.md>), [google-photos](<https://devfeed.tech/tags/google-photos.md>), [has](<https://devfeed.tech/tags/has.md>), [net](<https://devfeed.tech/tags/net.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

OAuth 2.0 provides authorization for API access, while OpenID Connect adds authentication through an ID token. The article explains how the protocols and tokens differ, when an app needs either or both, and common implementation mistakes such as using an access token as proof of login or failing to validate an ID token.

### Source excerpt

OAuth 2.0 handles authorization, OpenID Connect handles authentication. Learn the difference, how the tokens compare, and which one your app needs.

## A Modern Guide to Using OAuth 2.0 with Node.js

DevFeed: [A Modern Guide to Using OAuth 2.0 with Node.js](<https://devfeed.tech/articles/a-modern-guide-to-using-oauth-2-0-with-node-js-77422.md>)

Original publisher: [Read original article](<https://deanhume.com/a-modern-guide-to-using-oauth-2-0-with-node-js/>)

Author: Dean Hume

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

Content type: tutorial

Language: en

Sources: [Dean Hume](<https://devfeed.tech/sources/dean-hume.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Deno](<https://devfeed.tech/topics/deno.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [azure](<https://devfeed.tech/tags/azure.md>), [microsoft-graph](<https://devfeed.tech/tags/microsoft-graph.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [oauth](<https://devfeed.tech/tags/oauth.md>)

### AI overview

A practical tutorial demonstrates obtaining an OAuth 2.0 access token in Node.js with MSAL and using built-in fetch to call Microsoft Graph. It covers client credentials, loading credentials from an environment file, and common permission-related 403 errors.

### Source excerpt

Get an OAuth 2.0 access token in Node.js with MSAL, then call Microsoft Graph using built-in fetch and credentials loaded from an environment file.

## Add secure Web Search to Claude Desktop with Amazon Bedrock AgentCore

DevFeed: [Add secure Web Search to Claude Desktop with Amazon Bedrock AgentCore](<https://devfeed.tech/articles/add-secure-web-search-to-claude-desktop-with-amazon-bedrock-agentcore-64224.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/add-secure-web-search-to-claude-desktop-with-amazon-bedrock-agentcore/>)

Author: Jishnu Dasgupta

Published: 2026-10-02T15:46:05Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-iam-identity-center](<https://devfeed.tech/tags/aws-iam-identity-center.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [identity](<https://devfeed.tech/tags/identity.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This walkthrough explains how to connect Claude Desktop to Web Search through Amazon Bedrock AgentCore Gateway. It uses Amazon Cognito to federate AWS IAM Identity Center authentication and secure gateway requests with JWTs, keeping search traffic within AWS infrastructure.

### Source excerpt

Claude Desktop on Amazon Bedrock is limited to the model's knowledge cutoff without web search. In this post, we walk through connecting Claude Desktop to Web Search using Amazon Bedrock AgentCore Gateway, with JWT-based inbound authentication through AWS IAM Identity Center and Amazon Cognito.

## Device code phishing: How EvilTokens worked and how to stop it

DevFeed: [Device code phishing: How EvilTokens worked and how to stop it](<https://devfeed.tech/articles/device-code-phishing-how-eviltokens-worked-and-how-to-stop-it-63463.md>)

Original publisher: [Read original article](<https://workos.com/blog/device-code-phishing-eviltokens>)

Author: WorkOS

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

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [device-code-phishing](<https://devfeed.tech/tags/device-code-phishing.md>), [eviltokens](<https://devfeed.tech/tags/eviltokens.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [password](<https://devfeed.tech/tags/password.md>), [phishing](<https://devfeed.tech/tags/phishing.md>)

### AI overview

The article explains how EvilTokens used OAuth 2.0 device authorization to trick users into approving attackers' sign-ins, compromising more than 12,000 inboxes. It describes safeguards for products that offer device-code sign-in, including clearer approval screens, shorter flow windows, organization-level controls, separate monitoring, and planning for token revocation delays.

### Source excerpt

Microsoft took down a phishing service that used the OAuth device flow to get into 12,000 inboxes without stealing a single password. Here's what the attack means for teams that offer device-code sign-in.

## Keycloak 26.7.5 released

DevFeed: [Keycloak 26.7.5 released](<https://devfeed.tech/articles/keycloak-26-7-5-released-62908.md>)

Original publisher: [Read original article](<https://www.keycloak.org/2026/09/keycloak-2675-released>)

Author: Keycloak Team

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

Content type: release

Language: en

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

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Security](<https://devfeed.tech/topics/security.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [saml](<https://devfeed.tech/topics/saml.md>)

Tags: [dependencies](<https://devfeed.tech/tags/dependencies.md>), [idm](<https://devfeed.tech/tags/idm.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [keycloak-release](<https://devfeed.tech/tags/keycloak-release.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [owasp](<https://devfeed.tech/tags/owasp.md>), [saml](<https://devfeed.tech/tags/saml.md>), [security](<https://devfeed.tech/tags/security.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

Keycloak 26.7.5 is a release listing security fixes, resolved issues, and an upgrade migration guide. The fixes include authorization and identity protocol issues affecting OIDC and SAML, along with dependency vulnerabilities and other bugs.

### Source excerpt

To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Security fixes #50996 [CVE-2026-16103] Incomplete fix for CVE-2026-9798 (Keycloak CIBA brute-force lockout bypass at token redemption) oidc #51278 [CVE-2026-18206] Client policy source-host wildcard domains match non-subdomain suffixes oidc #51280 [CVE-2026-18203] Group policy child-extension matches sibling group path prefixes authorization-services #51281 [CVE-2026-18207] Source-group condition matches duplicate group names and can skip negative-logic enforcement oidc #51284 [CVE-2026-18208] Inactive out-of-audience introspection responses can include a signed JWT claim oidc #51285 [CVE-2026-18211] Secure-client-uris localhost exception accepts localhost-prefixed attacker domains oidc #51781 [CVE-2026-18217] SAML Redirect Binding Parameter Pollution saml #52531 CVE-2025-66021 com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer dependencies #52692 [CVE-2026-89298] Confidential client secret disclosed to view-clients role via Client Registration GET oidc #52783 [CVE-2026-88770] Device Authorization Grant issues tokens to brute-force-locked accounts (sibling of CVE-2026-9798) oidc #52888 CVE-2026-84939 org.freemarker:freemarker #52972 CVE-2026-8798 org.bouncycastle:bc-fips dependencies #52974 CVE-2026-13505 org.bouncycastle:bc-fips dependencies #53074 [CVE-2026-93999] Keycloak 26.7.2: token-exchange refresh continues issuing tokens for a disabled audience client token-exchange Weaknesses #51340 DCR: Registration access token allows protocol switch from OIDC to SAML oidc #53024 check-licenses.sh: shell injection via source of dependency pom.properties Enhancements #52357 Upgrade to Quarkus 3.33.4 dist/quarkus Bugs #50739 keycloak 26.7.0 sha1 file is missing dist/quarkus #50903 Missing input length validation on username field causes outsized log generation in /login-actions/authenticate authenticat

[Next page](<https://devfeed.tech/topics/oauth2.md?cursor=WyIyMDI2LTA5LTMwVDAwOjAwOjAwKzAwOjAwIiwgImFiYjkyNDZkLWM5YTMtNDAyOS1iNDNkLWM2YjY2NWE1MTNkNSJd>)