# OpenID connect (OIDC)

OpenID Connect (OIDC) is an identity layer built on OAuth 2.0 that enables clients to verify end-user identity and obtain profile information.

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

## S3 audit log streaming with OpenID Connect expands to GHE.com

DevFeed: [S3 audit log streaming with OpenID Connect expands to GHE.com](<https://devfeed.tech/articles/s3-audit-log-streaming-with-openid-connect-expands-to-ghe-com-142929.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-19-s3-audit-log-streaming-with-openid-connect-expands-to-ghe-com>)

Author: Allison

Published: 2026-11-19T08:27:16Z

Content type: news

Language: en

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

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [audit](<https://devfeed.tech/topics/audit.md>)

Tags: [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-log](<https://devfeed.tech/tags/audit-log.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [data](<https://devfeed.tech/tags/data.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-cloud](<https://devfeed.tech/tags/enterprise-cloud.md>), [enterprise-management-tools](<https://devfeed.tech/tags/enterprise-management-tools.md>), [github](<https://devfeed.tech/tags/github.md>), [github-enterprise-cloud](<https://devfeed.tech/tags/github-enterprise-cloud.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [openid](<https://devfeed.tech/tags/openid.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [platform-governance](<https://devfeed.tech/tags/platform-governance.md>), [s3](<https://devfeed.tech/tags/s3.md>), [streaming](<https://devfeed.tech/tags/streaming.md>)

### AI overview

GitHub Enterprise Cloud with data residency (GHE.com) now supports streaming enterprise audit logs to Amazon S3 using OpenID Connect (OIDC), extending the existing github.com capability. This enables authentication without storing long-lived AWS credentials on GitHub. The excerpt does not describe setup steps or other requirements.

### Source excerpt

You can now stream enterprise audit logs to Amazon S3 using OpenID Connect (OIDC) on GitHub Enterprise Cloud with data residency (GHE.com). This extends the existing github.com capability, letting you... The post S3 audit log streaming with OpenID Connect expands to GHE.com appeared first on The GitHub Blog.

## Step-up authentication: how to right-size authentication to risk

DevFeed: [Step-up authentication: how to right-size authentication to risk](<https://devfeed.tech/articles/step-up-authentication-how-to-right-size-authentication-to-risk-142070.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/step-up-authentication-how-to-right-size-authentication-to-risk/>)

Author: Abrom Douglas

Published: 2026-11-18T23:49:07Z

Content type: article

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [MFA](<https://devfeed.tech/topics/mfa.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [account-balance](<https://devfeed.tech/tags/account-balance.md>), [acr](<https://devfeed.tech/tags/acr.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [amr](<https://devfeed.tech/tags/amr.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [balance](<https://devfeed.tech/tags/balance.md>), [banking](<https://devfeed.tech/tags/banking.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [identity](<https://devfeed.tech/tags/identity.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [risk](<https://devfeed.tech/tags/risk.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [step-up-authentication](<https://devfeed.tech/tags/step-up-authentication.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [user](<https://devfeed.tech/tags/user.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Amazon Cognito step-up authentication lets applications match authentication strength and freshness to the risk of an action. The app requests a target level with OIDC `acr_values` and optional `max_age`, or `TARGET_ACR_VALUES` and `MAX_AGE` in the `USER_AUTH` API flow. Cognito reports the achieved level and factors in `acr` and `amr`; `auth_time` tracks interactive authentication, while token refresh preserves assurance and does not reset freshness. The application remains responsible for choosing required levels, validating returned claims, and enforcing access. Four patterns cover transaction-level checks, differing requirements across apps sharing SSO, API or SDK sign-in, and federated OIDC providers that map external assurance values. Step-up requires the Essentials or Plus plan; on lower tiers, API requests raise `FeatureUnavailableInTierException`, while managed login ignores `acr_values` and proceeds with normal authentication.

### Source excerpt

Not every action a user takes in an application carries the same risk. Viewing an account balance in a banking application isn't the same as wiring several thousand dollars to a new payee. In practice, though, many applications ask users to prove their identity once at sign-in and then treat every action the same from [...]

## Private certificate authority support in Amazon Bedrock AgentCore Identity

DevFeed: [Private certificate authority support in Amazon Bedrock AgentCore Identity](<https://devfeed.tech/articles/private-certificate-authority-support-in-amazon-bedrock-agentcore-identity-141213.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/private-certificate-authority-support-in-amazon-bedrock-agentcore-identity/>)

Author: Aastha Paul

Published: 2026-11-18T20:53:41Z

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>), [certificates](<https://devfeed.tech/topics/certificates.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agents](<https://devfeed.tech/tags/agents.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [application-load-balancer](<https://devfeed.tech/tags/application-load-balancer.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [aws](<https://devfeed.tech/tags/aws.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificate-authorities](<https://devfeed.tech/tags/certificate-authorities.md>), [certificate-authority](<https://devfeed.tech/tags/certificate-authority.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-providers](<https://devfeed.tech/tags/identity-providers.md>), [idp](<https://devfeed.tech/tags/idp.md>), [private](<https://devfeed.tech/tags/private.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [support](<https://devfeed.tech/tags/support.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Amazon Bedrock AgentCore Identity can validate self-hosted private IdPs using a PEM root or intermediate CA certificate stored in Secrets Manager or S3 and referenced by a credential provider. The provider must use a private endpoint and VPC Lattice; the certificate must be valid, PEM encoded, no larger than 16 KB, and stored in the same Region. Secrets Manager also requires the same account, while cross-account S3 requires a bucket owner account ID and access policy. AgentCore reads the certificate at provider creation or update, so changes to the stored file require an update call that includes certificateConfigurations. To rotate with less downtime, trust both old and new CAs, update the IdP server certificate, then remove the old CA and update again. CloudWatch exposes EarliestCertificateDaysToExpiry. AgentCore does not check CRLs or OCSP, so trust persists until the server certificate expires or its CA is removed. Protect write access to the trust store; the certificate itself contains no private key.

### Source excerpt

Amazon Bedrock AgentCore Identity now supports private certificate authorities (CAs), so your agents can connect to self-hosted identity providers that use a private CA. This post shows how to issue an IdP certificate with AWS Private CA, configure a credential provider to trust it, rotate the CA, and protect the certificate.

## CVE-2026-109857 - Authentication Bypass in CAST Imaging

DevFeed: [CVE-2026-109857 - Authentication Bypass in CAST Imaging](<https://devfeed.tech/articles/cve-2026-109857-authentication-bypass-in-cast-imaging-140658.md>)

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

Author: cvefeed.io

Published: 2026-11-18T13:17:23Z

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>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>)

Tags: [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [cast](<https://devfeed.tech/tags/cast.md>), [cast-software](<https://devfeed.tech/tags/cast-software.md>), [cve-2026-109857](<https://devfeed.tech/tags/cve-2026-109857.md>), [imaging](<https://devfeed.tech/tags/imaging.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>)

### AI overview

CAST Imaging has a critical authentication bypass (CVSS 9.2): its TenantFilter dynamically registers an OpenID Connect issuer from the X-ISSUER-LOCATION HTTP header. An unauthenticated remote attacker can register a malicious identity provider, create accounts matching existing administrator usernames, and obtain JWTs the application accepts, gaining administrative access. The issue is confirmed in version 3.6.2 and may affect other versions; the vendor says it is fixed in newer versions but provides no affected version range.

### Source excerpt

CVE ID :CVE-2026-109857 Published : Nov. 18, 2026, 1:17 p.m. | 1 hour, 9 minutes ago Description :CAST Imaging is vulnerable to authentication bypass in the TenantFilter class. The TenantFilter processes the X-ISSUER-LOCATION HTTP header and dynamically registers an OpenID Connect issuer based on its value. An unauthenticated remote attacker can register a malicious identity provider, create users matching existing administrative usernames, and obtain valid JWTs which will be accepted by the application. This results in complete authentication bypass and privilege escalation to administrative access. The vulnerability has only been confirmed in version 3.6.2 but may also affect other versions. The vendor did not provide the affected version range, but assured that the vulnerability is fixed "in newer versions". Severity: 9.2 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Securing REST APIs with JWT authorizers in Amazon API Gateway

DevFeed: [Securing REST APIs with JWT authorizers in Amazon API Gateway](<https://devfeed.tech/articles/securing-rest-apis-with-jwt-authorizers-in-amazon-api-gateway-139433.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/securing-rest-apis-with-jwt-authorizers-in-amazon-api-gateway/>)

Author: Giedrius Praspaliauskas

Published: 2026-11-17T18:39:16Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [authorizer](<https://devfeed.tech/tags/authorizer.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [scopes](<https://devfeed.tech/tags/scopes.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Amazon API Gateway REST API JWT authorizers validate OIDC tokens in the request path without a Lambda invocation. Configure trusted issuers, audiences, signing algorithms and optional claim rules; API Gateway checks signatures, expiry, not-before time and method scopes, then passes validated claims to the integration. The walkthrough applies separate `orders:read` and `orders:write` scopes to GET and POST methods and adds a Cognito user pool as a second issuer. Missing, malformed, expired or untrusted tokens receive 401; valid tokens failing scope or claim checks receive 403. Lambda authorizers remain useful for custom logic, token introspection or non-JWT credentials. Limits include 1-10 issuers, cached signing keys, no revocation checks, and public issuer URLs. Scope checks use `scope` or `scp`; the article notes Entra ID client-credentials permissions in `roles` require a dedicated audience per caller or a Lambda authorizer for role checks.

### Source excerpt

Amazon API Gateway REST APIs now support JWT authorizers, which validate tokens from any OIDC-compatible identity provider in API Gateway itself, with no Lambda authorizer required. Learn how JWT authorizers work, then build a REST API that accepts machine-to-machine tokens with per-method scopes and adds an Amazon Cognito user pool as a second issuer.

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

## Customize the OpenID Connect 1.0 UserInfo Response in Spring Authorization Server

DevFeed: [Customize the OpenID Connect 1.0 UserInfo Response in Spring Authorization Server](<https://devfeed.tech/articles/customize-the-openid-connect-1-0-userinfo-response-in-spring-authorization-server-129941.md>)

Original publisher: [Read original article](<https://www.baeldung.com/spring-authorization-server-openid-connect-userinfo-response-customize>)

Author: Philippe Sevestre

Published: 2026-11-11T13:16:37Z

Content type: tutorial

Language: en

Sources: [Baeldung](<https://devfeed.tech/sources/baeldung.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Spring Framework](<https://devfeed.tech/topics/spring-framework.md>), [Spring Boot](<https://devfeed.tech/topics/spring-boot.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [customization](<https://devfeed.tech/tags/customization.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [spring](<https://devfeed.tech/tags/spring.md>), [spring-mvc](<https://devfeed.tech/tags/spring-mvc.md>), [spring-mvc-spring-security-authorization](<https://devfeed.tech/tags/spring-mvc-spring-security-authorization.md>), [spring-security](<https://devfeed.tech/tags/spring-security.md>)

### AI overview

Spring Authorization Server's UserInfo endpoint can return claims from an application service, filtered by the scopes authorized for the client. The article's example maps the authenticated username to a UserInfo record, then uses a custom OidcUserInfoAuthenticationContext-to-OidcUserInfo function registered through the OIDC DSL. It adds email claims for the email scope, profile claims for profile, and account-specific claims for account; with no matching user or no relevant scopes, it returns only sub. The example uses a static map, while a real implementation could retrieve records from a database, LDAP, or REST service. The article also notes that updated_at needs a generic claim call to produce a JSON number in the described Spring version, and lists other endpoint customization hooks for request conversion, authentication providers, and response or error handling.

### Source excerpt

Learn how to customize the Spring Authorization Server UserInfo endpoint handling. The post Customize the OpenID Connect 1.0 UserInfo Response in Spring Authorization Server first appeared on Baeldung.

## Release Apache APISIX 3.20.0

DevFeed: [Release Apache APISIX 3.20.0](<https://devfeed.tech/articles/release-apache-apisix-3-20-0-130861.md>)

Original publisher: [Read original article](<https://apisix.apache.org/blog/2026/11/11/release-apache-apisix-3.20.0/>)

Author: Abhishek Choudhary

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

Content type: release

Language: en

Sources: [Apache APISIX Blog](<https://devfeed.tech/sources/apache-apisix-blog.md>)

Topics: [Release notes](<https://devfeed.tech/topics/release-notes.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Process](<https://devfeed.tech/topics/process.md>), [cache-invalidation](<https://devfeed.tech/topics/cache-invalidation.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [release](<https://devfeed.tech/tags/release.md>), [request](<https://devfeed.tech/tags/request.md>), [security](<https://devfeed.tech/tags/security.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

Apache APISIX 3.20.0 adds request decompression, multi-cluster Kubernetes discovery, HTTPS Consul discovery, verified OIDC claim forwarding, richer rate-limit diagnostics, and per-process Prometheus metrics. Request decompression supports gzip and deflate, defaults to a 1 MiB body limit, and sends decompressed content upstream unless configured to preserve compression. Multi-cluster upstreams select explicit cluster IDs and combine deduplicated endpoints; Consul HTTPS verifies certificates by default. The release also changes important compatibility and security behavior: `mcp-bridge` is removed, OIDC introspection now distinguishes invalid tokens (401) from service failures (503), `oas-validator` verifies HTTPS certificates by default, and upstreams receive normalized paths in relevant cases. Other changes tighten Keycloak permission checks, authentication header handling, and `openapi-to-mcp` trust and size limits. Operators should review the documented upgrade plans, especially for encrypted plugin values, metrics label changes, custom gRPC trust configuration, and containers that rely on `apisix start` staying in the foreground. APISIX Runtime is upgraded to 1.4.2.

### Source excerpt

Apache APISIX 3.20.0 was released on Nov 11, 2026. This release adds request decompression, multi-cluster Kubernetes discovery, OIDC claim forwarding, new process metrics, and important security and upgrade changes.

## Authenticate external gRPC clients with Amazon VPC Lattice

DevFeed: [Authenticate external gRPC clients with Amazon VPC Lattice](<https://devfeed.tech/articles/authenticate-external-grpc-clients-with-amazon-vpc-lattice-127235.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/authenticate-external-grpc-clients-with-amazon-vpc-lattice/>)

Author: Alin Scurtu

Published: 2026-11-10T01:16:39Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [gRPC](<https://devfeed.tech/topics/grpc.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [application-load-balancer](<https://devfeed.tech/tags/application-load-balancer.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [identity](<https://devfeed.tech/tags/identity.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The pattern bridges external JWT identity and VPC Lattice's SigV4 trust: an ALB validates RS256 access tokens, then an ECS proxy extracts selected claims into headers and signs requests with its task role. Lattice authorizes that workload identity through service network and per-service IAM auth policies; the translated identity headers are covered by SigV4. The native AWS SDK approach supports unary RPCs and requires application code to handle credentials, signing, and gRPC framing. Envoy moves signing into a filter pipeline and supports gRPC streaming when the Lattice target group uses protocol version GRPC; Lua claim translation must run before signing. The sample is for non-production use. The ALB needs a publicly accessible JWKS endpoint and cannot check token revocation, while the proxy must only accept ALB traffic because it does not revalidate JWTs.

### Source excerpt

External gRPC clients carry JWTs, but Amazon VPC Lattice trusts SigV4 signatures. This post shows how to build an ingress layer where an Application Load Balancer validates JWTs and an Amazon ECS proxy translates that identity into SigV4, enforcing per-service authorization with VPC Lattice auth policies while preserving gRPC over HTTP/2 end-to-end.

## Simplify cross-partition access with AWS IAM outbound identity federation

DevFeed: [Simplify cross-partition access with AWS IAM outbound identity federation](<https://devfeed.tech/articles/simplify-cross-partition-access-with-aws-iam-outbound-identity-federation-126474.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/simplify-cross-partition-access-with-aws-iam-outbound-identity-federation/>)

Author: Bill Wells

Published: 2026-11-09T16:08:30Z

Content type: release

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [china](<https://devfeed.tech/tags/china.md>), [cross](<https://devfeed.tech/tags/cross.md>), [govcloud](<https://devfeed.tech/tags/govcloud.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [partition](<https://devfeed.tech/tags/partition.md>), [partitions](<https://devfeed.tech/tags/partitions.md>), [resources](<https://devfeed.tech/tags/resources.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [services](<https://devfeed.tech/tags/services.md>), [sovereign-cloud](<https://devfeed.tech/tags/sovereign-cloud.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

IAM outbound identity federation enables cross-partition AWS access by having a workload request a short-lived, AWS-signed JWT in its source partition and exchange it through `sts:AssumeRoleWithWebIdentity` for temporary credentials in the destination partition. The destination role's trust policy can restrict access using token audience, subject, source Region, account, organization, or principal context. CloudTrail records a shared token ID across issuance and exchange for correlation, and destination policies can revoke sessions. Setup requires enabling federation in the source account, registering its issuer as an OIDC provider in the destination account, and configuring role trust and permissions. The feature is available across Commercial, China, GovCloud (US), and European Sovereign Cloud partitions at no additional cost; it does not support same-partition federation. AWS advises least privilege, short token lifetimes, audit monitoring, and compliance review. Organizations with existing PKI can alternatively use IAM Roles Anywhere.

### Source excerpt

You can now use tokens from AWS Identity and Access Management (IAM) outbound federation to assume roles in other Amazon Web Services (AWS) partitions. When your workloads run across AWS partitions such as Commercial, China, GovCloud (US), and European Sovereign Cloud, a workload in one partition might need to access resources or communicate with AWS [...]

## What is Cross App Access (XAA) for MCP?

DevFeed: [What is Cross App Access (XAA) for MCP?](<https://devfeed.tech/articles/what-is-cross-app-access-xaa-for-mcp-122604.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/09/what-is-cross-app-access-xaa-for-mcp/>)

Author: Ritesh Patel

Published: 2026-11-08T20:12:46.132051Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.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-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-code](<https://devfeed.tech/tags/ai-code.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [security](<https://devfeed.tech/tags/security.md>), [servers](<https://devfeed.tech/tags/servers.md>), [sso](<https://devfeed.tech/tags/sso.md>), [token](<https://devfeed.tech/tags/token.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

MCP's optional Enterprise-Managed Authorization extension lets an enterprise identity provider (IdP) decide whether a user may use a particular MCP client with a server and scopes, avoiding per-server authorization when both client and server support enterprise SSO. The client exchanges an ID token (or, in the described SAML case, a refresh token) at the IdP for an ID-JAG; it presents that grant to the server's authorization server, which validates it and returns a server-audience-restricted access token. The IdP may require client authentication, MFA, and client registration. Clients discover support through authorization server metadata listing the ID-JAG grant profile. The IdP sees token issuance, not tool traffic, so its policy cannot prevent misuse of tools the agent is authorized to call. The extension is optional; the article's unauthenticated exchange example was not tested against an IdP.

### Source excerpt

Cross App Access (XAA) lets your identity provider decide which MCP clients reach which MCP servers, via a signed ID-JAG exchanged for an access token.

## Releasing Ruby Gems with OIDC and GitHub Actions

DevFeed: [Releasing Ruby Gems with OIDC and GitHub Actions](<https://devfeed.tech/articles/releasing-ruby-gems-with-oidc-and-github-actions-122503.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/11/07/releasing-ruby-gems-with-oidc-and-github-actions.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

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

Content type: tutorial

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [project release](<https://devfeed.tech/topics/project-release.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [rubygems](<https://devfeed.tech/topics/rubygems.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [github-actions](<https://devfeed.tech/tags/github-actions.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [ruby](<https://devfeed.tech/tags/ruby.md>)

### AI overview

ruby-gem-release automates Ruby gem release bookkeeping through Ruby tasks and a reusable GitHub Actions workflow. RubyGems Trusted Publishing provides short-lived credentials, avoiding a stored RubyGems API key; after setup, collaborators with write access can dispatch releases. The example reads the version from a Ruby constant, dates the changelog before publishing, then increments the version and adds a "Next" section. It supports Intridea and Keep a Changelog formats. First publication requires configuring a trusted publisher and passing the numeric RubyGems account ID; later releases omit that input. For customization, Ruby callbacks expose steps such as changelog preparation, building and publishing the gem, Git tagging, and GitHub release creation as ordinary methods that can be tested.

### Source excerpt

The traditional approach for automating Ruby gem releases is to use release-gem. It's super simple. You can also build upon it when you need something beyond the plain rake release, such as updating a CHANGELOG.md, by rolling miles of brittle GitHub Actions YAML and shell script AI slop. Instead, I've been asking AI to follow a hand-crafted RELEASING.md. It can run tests, date CHANGELOG.md, ask me for a RubyGems OTP, make the release, increment the version of the next developer iteration. This works well. Still, AI is a very blunt tool for something that should be mechanized. Therefore, I built ruby-gem-release to automate all release bookkeeping in Ruby in an extensible workflow. The release runs in GitHub Actions. RubyGems Trusted Publishing supplies short-lived credentials, so there is no RubyGems API key to store in GitHub secrets or share with other maintainers. After setup, collaborators with write access can dispatch releases too. As an example, I added it to ruby-link-checker. Here's the Rakefile addition: require 'ruby-gem-release/workflow/ruby_gem' require 'ruby-gem-release/changelog' RubyGemRelease::Workflow::RubyGem.new( version: RubyGemRelease::Version::RubyConstant.new(path: 'lib/ruby-link-checker/version.rb', constant: 'VERSION'), changelog: RubyGemRelease::Changelog::Intridea.new(placeholder: '* Your contribution here.') ).install_tasks The version strategy reads a constant from lib/ruby-link-checker/version.rb: module LinkChecker VERSION = '0.5.0'.freeze end The CHANGELOG.md in this project is in the Intridea style. The gem also supports Keep a Changelog. Before publishing 0.5.0 the CHANGELOG.md is updated with a date. After publishing, the VERSION constant is incremented to 0.5.1, and CHANGELOG.md is updated with a Next section. Add .github/workflows/release.yml to call the reusable release workflow. The optional rubygems-owner input accepts your numeric RubyGems account ID when publishing a new gem for the first time: name: Release on: workflow_di

## How we built Render OIDC

DevFeed: [How we built Render OIDC](<https://devfeed.tech/articles/how-we-built-render-oidc-122096.md>)

Original publisher: [Read original article](<https://render.com/blog/how-we-built-render-oidc>)

Published: 2026-11-06T22:34:00Z

Content type: article

Language: en

Sources: [Render](<https://devfeed.tech/sources/render.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>)

Tags: [anthropic](<https://devfeed.tech/tags/anthropic.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [application](<https://devfeed.tech/tags/application.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [aws-sdk](<https://devfeed.tech/tags/aws-sdk.md>), [complex](<https://devfeed.tech/tags/complex.md>), [configure](<https://devfeed.tech/tags/configure.md>), [connect](<https://devfeed.tech/tags/connect.md>), [container](<https://devfeed.tech/tags/container.md>), [containerized](<https://devfeed.tech/tags/containerized.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [custom](<https://devfeed.tech/tags/custom.md>), [easy](<https://devfeed.tech/tags/easy.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [render](<https://devfeed.tech/tags/render.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Render OIDC lets services authenticate to providers such as AWS and GCP with signed, short-lived tokens instead of long-lived API keys. Tokens expire after 60 minutes; subject claims can scope access by service, environment, or workspace, while workspace-specific issuer URLs limit cross-workspace acceptance even if a provider's subject checks are misconfigured. Audience claims bind each token to its intended provider. Since common SDKs generally read tokens from files and do not offer a consistent refresh endpoint, Render runs an OIDC Daemon outside each container. A read-only bind mount exposes a shared in-memory directory to the service; the daemon writes token files before startup and refreshes them periodically. Provider setup differs: AWS uses an environment variable pointing to its token file, while GCP needs a credential configuration file. The workspace-specific issuer safeguard means customers with multiple workspaces must configure each one separately.

### Source excerpt

Learn how Render built OIDC authentication using short-lived tokens, workspace-specific issuers, and a daemon that keeps credentials fresh.

## Query Databricks Lakeflow Pipeline Tables from Snowflake, Without Copying Data

DevFeed: [Query Databricks Lakeflow Pipeline Tables from Snowflake, Without Copying Data](<https://devfeed.tech/articles/query-databricks-lakeflow-pipeline-tables-from-snowflake-without-copying-data-121423.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/query-databricks-lakeflow-pipeline-tables-from-snowflake-without-copying-data-dde301ede202?source=rss----34b6daafc07---4>)

Author: Vikneshwara Balakrishnan

Published: 2026-11-06T15:01:02Z

Content type: tutorial

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [aws](<https://devfeed.tech/tags/aws.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [lakeflow](<https://devfeed.tech/tags/lakeflow.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>)

### AI overview

The excerpt reports that all 13 selected Lakeflow pipeline tables were read in place from Snowflake on AWS after enabling `pipelines.externalMetadata.enabled`, Iceberg v3 compatibility, and Unity Catalog external access. Individual Iceberg tables served raw and curated data: they allow a precise table list and refresh only when the pipeline event log indicates changes, but require explicit refreshes. A catalog-linked database served the gold schema with automatic discovery and refresh; it is read-only here, exposes whole namespaces, and can propagate drops to Databricks if writes are allowed. The setup requires OAuth catalog integrations, vended credentials, and grants for the Snowflake service principal. Reported pitfalls include disabled metastore external access, missing pipeline metadata opt-in, and Iceberg UUID mismatches after full refreshes; the author handled the latter by recreating affected Snowflake Iceberg objects. The author describes pipeline-table external access as Public Preview and reports limitations including unsupported external writes, row-level security, and masking. Results come from one environment, and some explanations and fixes are explicitly unverified.

### Source excerpt

Streaming tables and materialized views, read in place as Iceberg: the settings that matter, what the logs show, and the Snowflake errors I hit Most guides to reading Databricks from Snowflake start with a plain Delta table. Mine are different: every table here is built by Lakeflow Declarative Pipelines (formerly Delta Live Tables), so they are streaming tables and materialized views, which an outside engine cannot read out of the box. I got Snowflake to read all 13 of them in place, as Apache Iceberg, with no copy: three layers on AWS, each in its own Unity Catalog catalog. I tried two Snowflake features on them: Iceberg tables over Unity Catalog's REST endpoint, and a catalog-linked database. This article covers how each works on Lakeflow tables, the Snowflake checks that confirm it, and the four Snowflake errors that cost me time. In short: Lakeflow tables need one opt-in (pipelines.externalMetadata.enabled) to be readable from Snowflake; with it, both Iceberg tables over the REST endpoint (raw, curated) and a catalog-linked database (gold) read all 13 in place. Disclaimer: This is my own work, not affiliated with or endorsed by Snowflake, Databricks or AWS. Parts were established by trial and error in one environment, so verify against the official documentation.Why Lakeflow tables are different A Lakeflow pipeline publishes streaming tables (incremental) and materialized views (recomputed queries). Both are Unity Catalog managed tables, but neither is a plain Delta table you can point another engine at. Three things follow, and they shaped everything below. They need an opt-in. Per Databricks' documentation, they appear externally "as managed tables" with the same name, but only with pipelines.externalMetadata.enabled = 'true', UniForm for Iceberg and Iceberg v3 (Databricks Runtime 17.3 or later). Skip the property and Snowflake rejects the views (Error 2). The pipeline owns them. Its run-as identity owns every table, so everyone else, including Snowflake's ser

## How to map AI agents and humans to one identity model with OIDC

DevFeed: [How to map AI agents and humans to one identity model with OIDC](<https://devfeed.tech/articles/how-to-map-ai-agents-and-humans-to-one-identity-model-with-oidc-121569.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/05/how-to-map-ai-agents-and-humans-to-one-identity-model-with-oidc/>)

Author: Ritesh Patel

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

Content type: tutorial

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Unified Access](<https://devfeed.tech/topics/unified-access.md>)

Tags: [2](<https://devfeed.tech/tags/2.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>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [client](<https://devfeed.tech/tags/client.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [identity](<https://devfeed.tech/tags/identity.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [map](<https://devfeed.tech/tags/map.md>), [model](<https://devfeed.tech/tags/model.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [one](<https://devfeed.tech/tags/one.md>), [people](<https://devfeed.tech/tags/people.md>), [records](<https://devfeed.tech/tags/records.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [sso](<https://devfeed.tech/tags/sso.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

One OIDC issuer can serve people and delegated AI agents; Kubernetes trusts the issuer and maps token claims to usernames and groups. The guide's Entra example registers each agent as a separate client, pins the audience to its client ID, checks the tenant claim, and maps a stable claim such as `sub` or `oid` to the Kubernetes username. In delegated sessions, `sub` identifies the person per application, so record the agent client separately and include the delegating person in the audit trail only if the provider supplies a suitable claim. Key limits: Entra omits the groups claim above 200 groups, unattended app-only agents are outside the guide's scope, and Kubernetes authentication configuration cannot be combined with `--oidc-*` flags. Kubernetes accepts OIDC tokens but does not issue OIDC tokens for agents.

### Source excerpt

Put AI agents and people behind one OIDC issuer, register each agent as its own client, and map claims to the username your Kubernetes API server records for delegated sessions.

## Keycloak 26.8.2 released

DevFeed: [Keycloak 26.8.2 released](<https://devfeed.tech/articles/keycloak-26-8-2-released-121092.md>)

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

Author: Keycloak Team

Published: 2026-11-05T00: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>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [saml](<https://devfeed.tech/topics/saml.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [brotli-decoder](<https://devfeed.tech/tags/brotli-decoder.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [dos](<https://devfeed.tech/tags/dos.md>), [idm](<https://devfeed.tech/tags/idm.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>), [organization](<https://devfeed.tech/tags/organization.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [out-of-bounds-write](<https://devfeed.tech/tags/out-of-bounds-write.md>), [pool](<https://devfeed.tech/tags/pool.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release](<https://devfeed.tech/tags/release.md>), [resource](<https://devfeed.tech/tags/resource.md>), [saml](<https://devfeed.tech/tags/saml.md>), [security](<https://devfeed.tech/tags/security.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

Keycloak 26.8.2, released November 5, 2026, lists fixes for numerous security issues, including account and session takeovers, token and authorization flaws, stored XSS, and unauthenticated denial of service affecting SAML endpoints and parsers. The excerpt also lists other weaknesses and bugs, plus an upgrade to Quarkus 3.40.1.1. Before upgrading, Keycloak directs users to consult the migration guide for the complete list of changes. The supplied text is an excerpt of the release notes, so it does not establish full coverage of all changes.

### 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 #53061 [CVE-2026-92358] Cross-browser fallback proof survives successful account linking and self-service unlink organizations #53618 [CVE-2026-105305] Device Authorization Grant bypasses per-client minimum.acr.value enforcement authentication #53749 CVE-2026-107623: OIDC DCR read-modify-write silently disables offline token revocation on backchannel logout oidc #53813 [CVE-2026-107889] Stored XSS on the login page via kcSanitize bypass authentication #54333 [CVE-2026-111497] Out-of-bounds write in bundled Brotli decoder dist/quarkus #54687 [CVE-2026-112201] Login-failure upsert trusts MySQL/MariaDB affected-row count #54688 [CVE-2026-112208] Account takeover via stale SSO_AUTH note in Organization identity-first login (reproduced on 26.8.1) #54689 [CVE-2026-110932] Keycloak <= 26.8.0 : Unauthenticated persistent disk exhaustion (theme gzip cache) #54690 [CVE-2026-107123] Unauthenticated DoS in Keycloak SAML endpoint #54691 [CVE-2026-107124] Session takeover by victim logout with injected id_token_hint #54692 [CVE-2026-107602] Unauthenticated CPU and worker-pool exhaustion (restart required) via SAML 1.1 KeyInfo parser loop on a legal ds:KeyName #54693 [CVE-2026-110931] Unauthenticated single-request JVM termination (OutOfMemoryError) via SAML 1.1 AuthorityBinding parser loop, incomplete fix of CVE-2026-7307 #54694 [CVE-2026-97367] DCR azp+sid claim substitution via User Property mappers allows Account REST victim session takeover -- #YWH-PGM40475-313 #54695 [CVE-2026-97174] CIBA sub parameter injection causes attacker authentication to issue victim tokens -- #YWH-PGM40475-289 #54696 [CVE-2026-114232] UMA user-managed permission resourceType field not validated -- cross-owner resource access -- #YWH-PGM40475-306 #54697 [CVE-2026-97847] Client manager can replace a sessionless token principal and take

## CVE-2026-115770 - Pocket ID: Email verification token remains valid after address change, enabling arbitrary verified-email spoofing

DevFeed: [CVE-2026-115770 - Pocket ID: Email verification token remains valid after address change, enabling arbitrary verified-email spoofing](<https://devfeed.tech/articles/cve-2026-115770-pocket-id-email-verification-token-remains-valid-after-address-change-enabling-arbitrary-verified-email-spoofing-117871.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-04T23:17:18Z

Content type: news

Language: en

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

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Passkeys](<https://devfeed.tech/topics/passkeys.md>)

Tags: [2-2](<https://devfeed.tech/tags/2-2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-115770](<https://devfeed.tech/tags/cve-2026-115770.md>), [email](<https://devfeed.tech/tags/email.md>), [email-verification](<https://devfeed.tech/tags/email-verification.md>), [impact](<https://devfeed.tech/tags/impact.md>), [link](<https://devfeed.tech/tags/link.md>), [matching](<https://devfeed.tech/tags/matching.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [passkeys](<https://devfeed.tech/tags/passkeys.md>), [pocket-id](<https://devfeed.tech/tags/pocket-id.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>), [spoofing](<https://devfeed.tech/tags/spoofing.md>), [token](<https://devfeed.tech/tags/token.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Pocket ID versions 2.2.0 through before 2.12.0 can mark an unintended email address as verified: verification tokens are bound to a user ID, and changing the account email does not invalidate an outstanding token. An ordinary user can request a token for an address they control, change the account to an unused address, then redeem the token to have that current address published with `email_verified=true`. The described default affected configuration has `emailsVerified=false` and `allowOwnAccountEdit=true`. A relying application that matches or provisions accounts based on verified email may link the attacker's identity to another user; this downstream consequence does not apply to applications relying exclusively on the stable OIDC `sub` claim. The issue is fixed in version 2.12.0.

### Source excerpt

CVE ID :CVE-2026-115770 Published : Nov. 4, 2026, 11:17 p.m. | 1 hour, 20 minutes ago Description :Pocket ID is an OIDC provider that allows users to authenticate with their passkeys to services. From 2.2.0 until 2.12.0, SendEmailVerification uses the token model in backend/internal/model/email_verification_token.go to bind an email-verification token only to the user's identifier, while UpdateUser can change the account email without invalidating the outstanding token and VerifyEmail marks the current address as verified. An ordinary user can request a token for an address they control, change the account to an arbitrary unused address, and redeem the old token so Pocket ID publishes the new address with email_verified set to true. The default affected configuration uses emailsVerified=false and allowOwnAccountEdit=true; the target address must not already belong to another Pocket ID user. A relying application that trusts a verified email for automatic account matching or provisioning can link the attacker's identity to another user's account, while applications that rely exclusively on the stable OIDC sub claim are not affected by that downstream consequence. This issue is fixed in version 2.12.0. Severity: 9.6 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## SSO just-in-time provisioning: How to match a login to an existing user safely

DevFeed: [SSO just-in-time provisioning: How to match a login to an existing user safely](<https://devfeed.tech/articles/sso-just-in-time-provisioning-how-to-match-a-login-to-an-existing-user-safely-117626.md>)

Original publisher: [Read original article](<https://workos.com/blog/sso-jit-provisioning-account-matching>)

Author: WorkOS

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

Content type: article

Language: en

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

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [attack](<https://devfeed.tech/tags/attack.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [branch](<https://devfeed.tech/tags/branch.md>), [callback](<https://devfeed.tech/tags/callback.md>), [condition](<https://devfeed.tech/tags/condition.md>), [email](<https://devfeed.tech/tags/email.md>), [just](<https://devfeed.tech/tags/just.md>), [login](<https://devfeed.tech/tags/login.md>), [order](<https://devfeed.tech/tags/order.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>), [safely](<https://devfeed.tech/tags/safely.md>), [sso](<https://devfeed.tech/tags/sso.md>), [store](<https://devfeed.tech/tags/store.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

For a custom SSO callback, resolve an existing identity first using the persistent `idp_id` scoped to its connection; if none exists, link by email only when the connection's organization has verified the email domain or an authoritative identity provider asserts a verified address. Otherwise create a separate user or require inbox proof before linking. Store the identity separately from the user, key it by the `idp_id` and connection pair, and refresh mutable profile attributes on returning sign-ins. Scope email lookups deliberately because a global match may belong to another customer. WorkOS's domain check blocks nonmatching profiles by default, but the callback should still enforce its own linking condition. The excerpt says AuthKit follows a similar link-first, verified-email, then create order, with verification and guest-invitation behavior handled in its flow.

### Source excerpt

Just-in-time provisioning is a resolution order in your SSO callback. Here is the order, the condition that makes the email match safe, and what to store.

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

## How to add enterprise SSO and SCIM to a Better Auth app

DevFeed: [How to add enterprise SSO and SCIM to a Better Auth app](<https://devfeed.tech/articles/how-to-add-enterprise-sso-and-scim-to-a-better-auth-app-109547.md>)

Original publisher: [Read original article](<https://workos.com/blog/add-enterprise-sso-scim-better-auth-app>)

Author: WorkOS

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

Content type: tutorial

Language: en

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

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [saml](<https://devfeed.tech/topics/saml.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [auth](<https://devfeed.tech/tags/auth.md>), [better](<https://devfeed.tech/tags/better.md>), [customers](<https://devfeed.tech/tags/customers.md>), [directory](<https://devfeed.tech/tags/directory.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

The guide keeps Better Auth in charge of users, sessions, and existing sign-in methods while WorkOS handles enterprise SAML/OIDC SSO, directory sync, and IT setup. It outlines a flow that routes verified enterprise email domains to SSO, validates state, organization, and domain in the callback, and links identities by organization plus IdP user ID rather than email. Existing users connect SSO while signed in; per-customer enforcement can be enabled after that transition. Directory Sync deactivation events revoke sessions, with idempotent background handling and periodic reconciliation recommended. WorkOS's Admin Portal gives customer admins a self-serve setup path. The approach suits apps where most users remain self-serve, but creates two systems to keep aligned as enterprise needs expand; the guide suggests considering AuthKit if that overhead grows. Examples assume Node.js 20+, Better Auth 1.7.x, TypeScript, and Next.js App Router for webhooks.

### Source excerpt

Keep Better Auth for sign-in and sessions, and let WorkOS handle SAML, OIDC and directory sync for the customers who need them.

## We've built the fastest way to create a one-click remote MCP server by mistake

DevFeed: [We've built the fastest way to create a one-click remote MCP server by mistake](<https://devfeed.tech/articles/we-ve-built-the-fastest-way-to-create-a-one-click-remote-mcp-server-by-mistake-109522.md>)

Original publisher: [Read original article](<https://appwrite.io/blog/post/one-click-remote-mcp-server-by-mistake>)

Author: Eldad Fux

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

Content type: article

Language: en

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

Topics: [Back end](<https://devfeed.tech/topics/backend.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [client](<https://devfeed.tech/topics/client.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Server-side rendering](<https://devfeed.tech/topics/server-side-rendering.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.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>), [ai-tool](<https://devfeed.tech/tags/ai-tool.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [email](<https://devfeed.tech/tags/email.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [production](<https://devfeed.tech/tags/production.md>), [remote-mcp-server](<https://devfeed.tech/tags/remote-mcp-server.md>)

### AI overview

An Appwrite project can host a remote MCP server with OAuth 2.1 authorization, consent, and user-scoped data access already integrated. The example server uses protected resource metadata and a 401 challenge for discovery, then verifies signed access tokens offline against the project's JWKS, checking issuer, the server-specific audience, token type, and scopes. Its tools are exposed only when the user's approved scopes permit them, with scope checks repeated on each call. The server can run as a Function on its own domain or as an SSR Site route; the example uses a Function and returns plain JSON per request, so streaming tools need a different design. The approach is fast because hosting, identity, and data share a project, though that consolidates those services on one platform. The OAuth2 server is currently an Appwrite Cloud feature, not available in self-hosted Appwrite. Revoking consent prevents new tokens, while already issued offline-verified tokens remain usable until expiry, one hour by default for public clients.

### Source excerpt

We built an email client on Appwrite to test a new feature, then asked an agent for a remote MCP server with OAuth 2.1. It was in production in under a minute.

## CVE-2026-116672 - Authlib RFC 7592 examples omit registration-access-token client binding

DevFeed: [CVE-2026-116672 - Authlib RFC 7592 examples omit registration-access-token client binding](<https://devfeed.tech/articles/cve-2026-116672-authlib-rfc-7592-examples-omit-registration-access-token-client-binding-102358.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-10-27T16:31:48Z

Content type: news

Language: en

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

Topics: [Authorization](<https://devfeed.tech/topics/authorization.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [interception](<https://devfeed.tech/topics/interception.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [authlib](<https://devfeed.tech/tags/authlib.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cve-2026-116672](<https://devfeed.tech/tags/cve-2026-116672.md>), [examples](<https://devfeed.tech/tags/examples.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [interception](<https://devfeed.tech/tags/interception.md>), [library](<https://devfeed.tech/tags/library.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [openid](<https://devfeed.tech/tags/openid.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [python](<https://devfeed.tech/tags/python.md>), [redirect](<https://devfeed.tech/tags/redirect.md>), [reference](<https://devfeed.tech/tags/reference.md>), [request](<https://devfeed.tech/tags/request.md>), [rfc](<https://devfeed.tech/tags/rfc.md>), [servers](<https://devfeed.tech/tags/servers.md>), [target](<https://devfeed.tech/tags/target.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

Authlib's documented RFC 7592 reference implementations, from version 0.15 until 1.9.1, can let a client with any valid registration access token read, modify, or delete another client's registration. They use the request's client_id to select the target and check whether it is editable, but do not verify that request.credential belongs to that client. Changing redirect_uris may enable authorization code or token interception; deleting registrations may deny service. The issue is fixed in version 1.9.1.

### Source excerpt

CVE ID :CVE-2026-116672 Published : Oct. 27, 2026, 4:31 p.m. | 54 minutes ago Description :Authlib is a Python library which builds OAuth and OpenID Connect servers. From 0.15 until 1.9.1, the documented ClientConfigurationEndpoint.authenticate_client and ClientConfigurationEndpoint.check_permission reference implementations look up a target client from request-controlled client_id data and check only whether that target is editable, without verifying that request.credential belongs to the target client. Deployments following both examples can allow a client holding any valid registration access token to read, modify, or delete another client's registration. Changing redirect_uris can enable authorization code or token interception, while deleting registrations can deny service to affected clients. This issue is fixed in version 1.9.1. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Identity and Access Management Architecture

DevFeed: [Identity and Access Management Architecture](<https://devfeed.tech/articles/identity-and-access-management-architecture-103394.md>)

Original publisher: [Read original article](<https://blog.devops.dev/identity-and-access-management-architecture-ad5dde7e7765?source=rss----33f8b2d9a328---4>)

Author: Scaibu

Published: 2026-10-27T10:20:02Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [saml](<https://devfeed.tech/topics/saml.md>), [WebAuthn](<https://devfeed.tech/topics/webauthn.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [passwords](<https://devfeed.tech/topics/passwords.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [ami](<https://devfeed.tech/tags/ami.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [broker](<https://devfeed.tech/tags/broker.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-and-access](<https://devfeed.tech/tags/identity-and-access.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [login](<https://devfeed.tech/tags/login.md>), [lts](<https://devfeed.tech/tags/lts.md>), [minors](<https://devfeed.tech/tags/minors.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [password](<https://devfeed.tech/tags/password.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [system-design-interview](<https://devfeed.tech/tags/system-design-interview.md>)

### AI overview

Keycloak centralizes login, federation and token issuance, while applications validate signed JWTs locally and retain fine-grained authorization such as tenant roles, API keys and resource permissions. The excerpt recommends coarse roles and identity claims in short-lived tokens, with per-request tenant membership checks and ReBAC in the application. It describes an integration that gets PKCE and five-minute access tokens right but has critical gaps: its JWT verifier decodes tokens without checking signatures, and sign-in and administration still use the legacy password grant. The target design uses Authorization Code with PKCE for people, client credentials for services, device authorization for CLIs, and cached JWKS validation checking signature, issuer, audience and expiry. Keycloak is presented as feature-rich for self-hosted federation and security controls, but requires operating a stateful Java service and keeping pace with quarterly upgrades; it does not replace application-level authorization.

### Source excerpt

A Practical Guide to Authentication, Authorization, Single Sign-On, and Identity FederationWhat Keycloak is? Keycloak is an open-source identity broker and authorization server: it logs users in, issues standards-based tokens, and federates identities from other systems so your services never handle passwords. The current release is 26.8.1, shipped 13 October 2026 (versio.io). It solves three problems at once. Applications delegate login to one place (SSO). Users can come from local accounts, LDAP/AD, or upstream IdPs such as Google or a corporate SAML IdP (brokering and federation). Services verify a signed JWT locally instead of calling a session store on every request. Key facts that shape how you operate it: Lineage. Red Hat has stewarded it since 2018 and ships it commercially as Red Hat build of Keycloak; it is a CNCF incubating project. Runtime. Since version 17 it runs on Quarkus, not WildFly. Old guides using standalone.xml, /auth context paths or jboss-cli are obsolete. No LTS. The community project patches only the latest minor; older lines stop getting security fixes when a new one ships (Skycloak). Minors land roughly quarterly (26.5 Jan, 26.6 Apr, 26.7 Jul, 26.8 Oct 2026), so plan an upgrade cadence, not an install. Admin bootstrap changed. KEYCLOAK_ADMIN / KEYCLOAK_ADMIN_PASSWORD were replaced by KC_BOOTSTRAP_ADMIN_USERNAME / KC_BOOTSTRAP_ADMIN_PASSWORD, which seed a temporary first admin only Core domain model Everything in Keycloak lives inside a realm, a fully isolated namespace with its own users, clients, keys and login policies. The master realm is for administering Keycloak only; never put application users there. Realm. Isolation boundary for users, keys, sessions and flows. Use one realm per trust domain, not per customer; hundreds of realms degrade startup and the admin UX. Client. An application that asks Keycloak to authenticate users or itself. Public clients (SPA, mobile) hold no secret; confidential clients (backends) hold a secret or k

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