# OAuth

OAuth is an open standard for authorization on the web.

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

## CVE-2026-130728 - NocoDB before 2026.08.0 Stored XSS via OAuth Redirect URI

DevFeed: [CVE-2026-130728 - NocoDB before 2026.08.0 Stored XSS via OAuth Redirect URI](<https://devfeed.tech/articles/cve-2026-130728-nocodb-before-2026-08-0-stored-xss-via-oauth-redirect-uri-140417.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-130728>)

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-18T11:34:00Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [XSS](<https://devfeed.tech/topics/xss.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [button](<https://devfeed.tech/tags/button.md>), [clients](<https://devfeed.tech/tags/clients.md>), [consent](<https://devfeed.tech/tags/consent.md>), [cross-site-scripting](<https://devfeed.tech/tags/cross-site-scripting.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-130728](<https://devfeed.tech/tags/cve-2026-130728.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [link](<https://devfeed.tech/tags/link.md>), [nocodb](<https://devfeed.tech/tags/nocodb.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [published](<https://devfeed.tech/tags/published.md>), [redirect](<https://devfeed.tech/tags/redirect.md>), [script](<https://devfeed.tech/tags/script.md>), [session](<https://devfeed.tech/tags/session.md>), [stored](<https://devfeed.tech/tags/stored.md>), [token](<https://devfeed.tech/tags/token.md>), [user](<https://devfeed.tech/tags/user.md>), [xss](<https://devfeed.tech/tags/xss.md>)

### AI overview

NocoDB versions before 2026.08.0 are described as vulnerable to stored cross-site scripting: any authenticated user can register an OAuth client with a `javascript:` redirect URI, then send a consent link to a signed-in victim. Either consent button can execute script in the NocoDB origin, potentially exposing the session token and enabling account takeover. The excerpt gives a severity score of 8.5 (HIGH) but does not identify affected versions more precisely or provide mitigation steps.

### Source excerpt

CVE ID :CVE-2026-130728 Published : Nov. 18, 2026, 11:34 a.m. | 14 minutes ago Description :NocoDB before 2026.08.0 contains a stored cross-site scripting vulnerability that allows any authenticated user to register OAuth clients with javascript: redirect URIs. Attackers can send a consent link to a signed-in victim so either consent button runs script in the NocoDB origin, stealing the session token for account takeover. Severity: 8.5 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## One Recovery Code, Two Shells in Control Web Panel

DevFeed: [One Recovery Code, Two Shells in Control Web Panel](<https://devfeed.tech/articles/one-recovery-code-two-shells-in-control-web-panel-135996.md>)

Original publisher: [Read original article](<https://www.vulncheck.com/blog/control-web-panel-recovery-code-rce>)

Author: Valentin Lobstein (Chocapikk)

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

Content type: news

Language: en

Sources: [VulnCheck](<https://devfeed.tech/sources/vulncheck.md>)

Topics: [password reset](<https://devfeed.tech/topics/password-reset.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [code security](<https://devfeed.tech/topics/code-security.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [control-panel](<https://devfeed.tech/tags/control-panel.md>), [control-web-panel](<https://devfeed.tech/tags/control-web-panel.md>), [coordinated-vulnerability-disclosure](<https://devfeed.tech/tags/coordinated-vulnerability-disclosure.md>), [cron](<https://devfeed.tech/tags/cron.md>), [cve-2026-124020](<https://devfeed.tech/tags/cve-2026-124020.md>), [cve-2026-124021](<https://devfeed.tech/tags/cve-2026-124021.md>), [cwp](<https://devfeed.tech/tags/cwp.md>), [header](<https://devfeed.tech/tags/header.md>), [initial-access](<https://devfeed.tech/tags/initial-access.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [password](<https://devfeed.tech/tags/password.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [reset](<https://devfeed.tech/tags/reset.md>), [vulncheck](<https://devfeed.tech/tags/vulncheck.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Two Control Web Panel flaws let an attacker use an account's password-recovery code to reach code execution as that hosting account. CVE-2026-124020 trusts the unauthenticated request Host header when building reset links, enabling code capture followed by a password reset and shell access through File Manager and Crontab. CVE-2026-124021 lets the port 2304 administration API accept that code as authorization and add a cron job without resetting the password; it applies where the API is exposed, since standard CSF blocks the port by default. CWP 1.30.6 fixes both by using the configured hostname in reset links, consuming recovery codes after reset, and rejecting them as API authorization. The text advises keeping port 2304 off the public internet and restricting the user panel to known networks if an immediate update is not possible.

### Source excerpt

VulnCheck's Initial Access Intelligence team discloses two vulnerabilities in Control Web Panel that both end in code execution as the hosting account from the same primitive, an account password-recovery code. One poisons the reset link's Host header to leak the code, and the other feeds that code to the administration API, which accepts it as OAuth authorization.

## 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.

## 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.

## OAuth Token Exchange vs Agent Delegation: What Enterprises Need to Know

DevFeed: [OAuth Token Exchange vs Agent Delegation: What Enterprises Need to Know](<https://devfeed.tech/articles/oauth-token-exchange-vs-agent-delegation-what-enterprises-need-to-know-112151.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/oauth-token-exchange-vs-agent-delegation/>)

Author: Lyzr Team

Published: 2026-10-30T08:09:39Z

Content type: article

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-delegation](<https://devfeed.tech/tags/agent-delegation.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>), [complete](<https://devfeed.tech/tags/complete.md>), [consider](<https://devfeed.tech/tags/consider.md>), [delegation](<https://devfeed.tech/tags/delegation.md>), [employee](<https://devfeed.tech/tags/employee.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [know](<https://devfeed.tech/tags/know.md>), [need](<https://devfeed.tech/tags/need.md>), [needs](<https://devfeed.tech/tags/needs.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [process](<https://devfeed.tech/tags/process.md>), [token](<https://devfeed.tech/tags/token.md>), [token-exchange](<https://devfeed.tech/tags/token-exchange.md>), [vs](<https://devfeed.tech/tags/vs.md>)

### AI overview

OAuth Token Exchange and Agent Delegation address different parts of agent security: token exchange is a standardized way to obtain a token for a specific downstream resource, while delegation defines what an agent may do, for whom, and under what limits. RFC 8693 distinguishes impersonation, where a request acts as another principal, from delegation, where the acting application retains its identity while representing another principal. The text recommends separate user and agent identities, task specific least privilege, resource appropriate tokens, bounded delegation lifetimes, preserved delegation provenance, revocation, and end to end activity records. High impact actions may require human approval. Token validity alone does not establish permission or guarantee immediate revocation; broader governance is needed to track agents, policies, access, and activity across environments.

### Source excerpt

Consider an enterprise AI agent assigned to process an employee's expense reports. To complete the task, it needs to retrieve expense records from an internal...

## CVE-2026-118669 - OAuthLib: Token grants can use attacker-supplied client\_id for authorization after authenticating a different client

DevFeed: [CVE-2026-118669 - OAuthLib: Token grants can use attacker-supplied client\_id for authorization after authenticating a different client](<https://devfeed.tech/articles/cve-2026-118669-oauthlib-token-grants-can-use-attacker-supplied-client-id-for-authorization-after-authenticating-a-different-client-105595.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-118669>)

Author: CVEFEED.io; github.com

Published: 2026-10-28T22:17:12Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [client](<https://devfeed.tech/tags/client.md>), [cve-2026-118669](<https://devfeed.tech/tags/cve-2026-118669.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [python](<https://devfeed.tech/tags/python.md>), [scopes](<https://devfeed.tech/tags/scopes.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

Before OAuthLib 4.0.0, the client_credentials and Resource Owner Password Credentials handlers could authenticate one confidential client but use an attacker-supplied client_id when validating grant types and scopes. A lower-privilege authenticated client could potentially obtain tokens with unauthorized grants or scopes if the application's validators rely on the documented client_id argument; validators that authorize only from request.client may not be affected. The issue is fixed in OAuthLib 4.0.0. The excerpt lists no affected products.

### Source excerpt

CVE ID :CVE-2026-118669 Published : Oct. 28, 2026, 10:17 p.m. | 1 hour, 12 minutes ago Description :OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. Prior to 4.0.0, the client_credentials and Resource Owner Password Credentials token grant handlers can authenticate request.client as one confidential client while retaining an attacker-supplied request.client_id for validate_grant_type and validate_scopes. A lower-privilege authenticated client can therefore cause grant and scope authorization to use another client's identity when an application validator relies on the documented client_id argument, potentially issuing tokens with unauthorized grants or scopes. Validators that authorize exclusively from request.client may not be affected. This issue is fixed in version 4.0.0. Severity: 8.4 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-106013 - Jupiter X Core \<= 4.61.0 - Unauthenticated Authentication Bypass via Twitter/X Social Login oauth\_verifier Parameter

DevFeed: [CVE-2026-106013 - Jupiter X Core \<= 4.61.0 - Unauthenticated Authentication Bypass via Twitter/X Social Login oauth\_verifier Parameter](<https://devfeed.tech/articles/cve-2026-106013-jupiter-x-core-4-61-0-unauthenticated-authentication-bypass-via-twitter-x-social-login-oauth-verifier-parameter-102855.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-106013>)

Author: CVEFEED.io; wordfence.com

Published: 2026-10-28T02:17:01Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [artbees](<https://devfeed.tech/tags/artbees.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [core](<https://devfeed.tech/tags/core.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-106013](<https://devfeed.tech/tags/cve-2026-106013.md>), [jupiter-x-core](<https://devfeed.tech/tags/jupiter-x-core.md>), [login](<https://devfeed.tech/tags/login.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [social](<https://devfeed.tech/tags/social.md>), [twitter](<https://devfeed.tech/tags/twitter.md>), [x](<https://devfeed.tech/tags/x.md>)

### AI overview

Jupiter X Core versions through 4.61.0 are described as vulnerable to unauthenticated WordPress account takeover through Twitter/X social login. In verify_twitter_callback, the plugin exchanges the visitor's oauth_verifier but does not assign the returned credentials to the TwitterOAuth client. The subsequent verification request therefore uses the site operator's stored tokens, returns the X application owner's profile, and the plugin authenticates the WordPress account matching that profile's email. The source says this account is typically the site administrator.

### Source excerpt

CVE ID :CVE-2026-106013 Published : Oct. 28, 2026, 2:17 a.m. | 29 minutes ago Description :The Jupiter X Core plugin for WordPress is vulnerable to Authentication Bypass via the Twitter/X Social Login handler in all versions up to and including 4.61.0. The vulnerability exists within the verify_twitter_callback function because after exchanging the visitor's oauth_verifier for their access token, the handler never calls setOauthToken() to reassign the returned credentials to the TwitterOAuth client, causing the subsequent account/verify_credentials API call to remain signed with the site operator's stored Access Token and Access Token Secret rather than the authenticating visitor's token. This causes the X API to return the profile of the X application owner instead of the signing-in visitor, and the plugin then resolves and authenticates a WordPress account solely by matching that owner's email address via wp_set_auth_cookie(), allowing unauthenticated attackers to gain authenticated access as the WordPress user whose email corresponds to the X app owner, who is typically the site administrator. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## 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.

## GitHub CLI: Opt in to expiring, auto-refreshing OAuth tokens

DevFeed: [GitHub CLI: Opt in to expiring, auto-refreshing OAuth tokens](<https://devfeed.tech/articles/github-cli-opt-in-to-expiring-auto-refreshing-oauth-tokens-93076.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-10-21-github-cli-opt-in-to-expiring-auto-refreshing-oauth-tokens>)

Author: Allison

Published: 2026-10-21T16:43:23Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cli](<https://devfeed.tech/tags/cli.md>), [client-apps](<https://devfeed.tech/tags/client-apps.md>), [config](<https://devfeed.tech/tags/config.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [ghes](<https://devfeed.tech/tags/ghes.md>), [git](<https://devfeed.tech/tags/git.md>), [github](<https://devfeed.tech/tags/github.md>), [github-cli](<https://devfeed.tech/tags/github-cli.md>), [github-com](<https://devfeed.tech/tags/github-com.md>), [github-enterprise](<https://devfeed.tech/tags/github-enterprise.md>), [github-enterprise-server](<https://devfeed.tech/tags/github-enterprise-server.md>), [https](<https://devfeed.tech/tags/https.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-tokens](<https://devfeed.tech/tags/oauth-tokens.md>), [preview](<https://devfeed.tech/tags/preview.md>), [release](<https://devfeed.tech/tags/release.md>), [token](<https://devfeed.tech/tags/token.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

GitHub CLI v2.103.0 adds an opt-in public preview of expiring OAuth credentials: `gh auth login --expiring` enables them for a sign-in, or `gh config set expiring_credentials enabled` enables them for future sign-ins. `gh` stores a short-lived access token with a rotating refresh token and refreshes it automatically; `gh auth status` shows its expiry. For HTTPS git use, configure `gh` with `gh auth setup-git`; Git 2.46 or newer can avoid caching credentials past their lifetime. Scripts or tools that save a token obtained once may later hold an expired value, so retrieve it fresh with `gh auth token`. Servers that do not issue refreshable credentials fall back to nonexpiring tokens. Availability is stated for github.com and ghe.com, and GHES 3.23 onward; earlier GHES versions use the existing nonexpiring behavior. Opt-in is backward compatible, while workflows requiring long-lived tokens may break.

### Source excerpt

You can now use expiring, automatically refreshing OAuth credentials in GitHub CLI as part of a public preview. When you opt in, gh stores an expiring access token alongside a... The post GitHub CLI: Opt in to expiring, auto-refreshing OAuth tokens appeared first on The GitHub Blog.

## 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.

## Pipes Connection Sharing: Connect Slack once for the whole organization

DevFeed: [Pipes Connection Sharing: Connect Slack once for the whole organization](<https://devfeed.tech/articles/pipes-connection-sharing-connect-slack-once-for-the-whole-organization-92857.md>)

Original publisher: [Read original article](<https://workos.com/blog/pipes-connection-sharing>)

Author: WorkOS

Published: 2026-10-21T13:43:32Z

Content type: article

Language: en

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

Topics: [Slack](<https://devfeed.tech/topics/slack.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [bot](<https://devfeed.tech/tags/bot.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [docs](<https://devfeed.tech/tags/docs.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [organization](<https://devfeed.tech/tags/organization.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [slack](<https://devfeed.tech/tags/slack.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

WorkOS Pipes organization connections let an admin establish one provider connection for all active organization members. They fit organization-owned credentials such as a shared Slack bot, company analytics key, or server-to-server grant; person-specific identities should remain per-user. Enable organization ownership for the provider and shared connections in the admin and member widgets, then request credentials with `connection_owner: "organization"` (or select that owner in Relay). Organization scope alone does not select a shared connection, and Relay never falls back to the other owner. Calls use the connecting account's permissions, so keep its scopes narrow and log the acting member. Members cannot repair shared connections themselves. If the establishing member leaves the organization, WorkOS clears the credential and marks the connection `needs_reauthorization`; an admin must reconnect it.

### Source excerpt

Pipes Connection Sharing lets an admin connect a provider once for the whole organization. When it beats per-user OAuth, and what changes in your code.

## 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.

## 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.

## 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.

## Best Managed OAuth Providers for AI Agents

DevFeed: [Best Managed OAuth Providers for AI Agents](<https://devfeed.tech/articles/best-managed-oauth-providers-for-ai-agents-90696.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/best-managed-oauth-providers>)

Author: Swytchcode Team

Published: 2026-10-16T03:30:00Z

Content type: comparison

Language: en

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

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [oauth](<https://devfeed.tech/tags/oauth.md>)

### AI overview

The article compares managed OAuth providers for AI agents and argues that the key production test is whether each call uses the intended customer's token, fails when that customer has not connected, and avoids falling back to another account. It reviews providers including Nango, Pipedream Connect, Paragon, Merge, Apideck, Composio, Auth0 Token Vault, and Swytchcode, describing tradeoffs in token handling, integration features, and product fit.

### Source excerpt

Managed OAuth means a provider runs the OAuth client, stores the tokens, and refreshes them. For AI agents, the dividing line is whether the correct tenant's token is selected at runtime, on that call, with no fallback to a default account.

## 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.

## 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 grants pile up faster than you can review them. Here's how to keep up.

DevFeed: [OAuth grants pile up faster than you can review them. Here's how to keep up.](<https://devfeed.tech/articles/oauth-grants-pile-up-faster-than-you-can-review-them-here-s-how-to-keep-up-77094.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/oauth-grants-pile-up-faster-than-you-can-review-them-heres-how-to-keep-up/>)

Author: Sponsored by Nudge Security

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

Content type: article

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [article](<https://devfeed.tech/tags/article.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [nudge-security](<https://devfeed.tech/tags/nudge-security.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-grants](<https://devfeed.tech/tags/oauth-grants.md>), [oauth-tokens](<https://devfeed.tech/tags/oauth-tokens.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

OAuth grants let third-party apps retain access to corporate data, often beyond an employee's account credentials, making them difficult for security teams to review at scale. Sponsored by Nudge Security, the article describes its discovery, risk scoring, AI-assisted grant analysis, and human-reviewed governance workflow for assessing and revoking risky access.

### Source excerpt

OAuth grants create data highways between SaaS apps, AI agents, and other tools. And, they are multiplying faster than any security team can review them. As the recent Klue breach showed, attackers are taking notice and exploiting forgotten OAuth grants to gain access to corporate data. This article covers why OAuth risks are so hard [...]

## SSO vs OAuth vs OIDC vs SAML

DevFeed: [SSO vs OAuth vs OIDC vs SAML](<https://devfeed.tech/articles/sso-vs-oauth-vs-oidc-vs-saml-62097.md>)

Original publisher: [Read original article](<https://blog.levelupcoding.com/p/sso-vs-oauth-vs-oidc-vs-saml>)

Author: Nikki Siapno

Published: 2026-09-29T12:44:20Z

Content type: tutorial

Language: en

Sources: [Level Up Coding System Design Newsletter](<https://devfeed.tech/sources/level-up-coding-system-design-newsletter.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [saml](<https://devfeed.tech/topics/saml.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-vs-authorization](<https://devfeed.tech/tags/authentication-vs-authorization.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

The article distinguishes SSO as a sign-in experience from OAuth 2.0, OIDC, and SAML as mechanisms that address access and identity. It explains authentication versus authorization and describes how applications can trust a shared identity provider for federated sign-in.

### Source excerpt

Do you know the differences? Here's a clear breakdown to make them click.

## Descope Agentic Identity Hub Demo: Access Control, OAuth, and Audit Logs for MCP Agents

DevFeed: [Descope Agentic Identity Hub Demo: Access Control, OAuth, and Audit Logs for MCP Agents](<https://devfeed.tech/articles/the-agentic-identity-hub-61487.md>)

Original publisher: [Read original article](<https://www.developersdigest.tech/tutorials/ZAfvfUlST10>)

Author: Developers Digest

Published: 2026-09-29T01:04:18Z

Content type: tutorial

Language: en

Sources: [Developers Digest](<https://devfeed.tech/sources/developers-digest.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-identity](<https://devfeed.tech/tags/agentic-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [audit](<https://devfeed.tech/tags/audit.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

The video demonstrates Descope's Agentic Identity Hub, covering fine-grained access control, OAuth, and audit logs for MCP AI agents.

### Source excerpt

Descope Agentic Identity Hub Demo: Fine-Grained Access Control, OAuth, and Audit Logs for MCP AI Agents Check out Descope: https://descope.plug.dev/inU8swv The video demonstrates Descope's Agentic I...

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