# Keycloak

Keycloak is an open-source identity and access management technology that provides authentication, user federation, user management, and fine-grained authorization for applications and services.

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

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

## Java4Shell Vulnerability Puts Many Enterprise Applications at Risk of Takeover

DevFeed: [Java4Shell Vulnerability Puts Many Enterprise Applications at Risk of Takeover](<https://devfeed.tech/articles/java4shell-vulnerability-puts-many-enterprise-applications-at-risk-of-takeover-140181.md>)

Original publisher: [Read original article](<https://www.securityweek.com/java4shell-vulnerability-puts-many-enterprise-applications-at-risk-of-takeover/>)

Author: Eduard Kovacs

Published: 2026-11-18T07:43:34Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [Exploit](<https://devfeed.tech/topics/exploit.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Spring Framework](<https://devfeed.tech/topics/spring-framework.md>), [redhat](<https://devfeed.tech/topics/redhat.md>)

Tags: [code-execution](<https://devfeed.tech/tags/code-execution.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-applications](<https://devfeed.tech/tags/enterprise-applications.md>), [featured](<https://devfeed.tech/tags/featured.md>), [java](<https://devfeed.tech/tags/java.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>), [jira](<https://devfeed.tech/tags/jira.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Java4Shell (CVE-2026-114938) is a patched OpenJDK memory safety flaw in Base64 decoding on x86-64 CPUs with AVX-512 VBMI. Malformed input can overrun the output buffer, exposing heap data or potentially enabling code execution. Calif demonstrated pre-authentication RCE in default-configured Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate; authenticated RCE in several other products; and a client-side TLS attack path. VulnCheck says crashing a reachable vulnerable JVM is straightforward, but RCE requires target-specific heap manipulation, address leaks and ASLR bypasses. Calif's published PoC shows corruption, not RCE, and says individual product chains remain private. OpenJDK versions from 17.0.6 and listed Java distributions are affected; ARM64 is not. Oracle issued fixes in its November 2026 Critical Security Patch Update, while other distributions depend on vendor updates. CISA advises immediate patching, prioritizing internet-exposed systems, and checking Java embedded in third-party software, containers and appliances. As of November 17, public OpenJDK update repositories lacked the fix; Cisco Talos had not observed exploitation in the wild.

### Source excerpt

Calif demonstrated remote code execution in Jira, Jenkins and Keycloak, while VulnCheck says real-world RCE requires per-target work The post Java4Shell Vulnerability Puts Many Enterprise Applications at Risk of Takeover appeared first on SecurityWeek.

## Java4Shell (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak on Java 17+ AVX-512 VBMI Servers

DevFeed: [Java4Shell (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak on Java 17+ AVX-512 VBMI Servers](<https://devfeed.tech/articles/java4shell-cve-2026-114938-enables-pre-auth-rce-in-jira-jenkins-keycloak-on-java-17-avx-512-vbmi-servers-140565.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/11/java4shell-cve-2026-114938-enables-pre.html>)

Author: The Hacker News

Published: 2026-11-18T04:27:41Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Jenkins](<https://devfeed.tech/topics/jenkins.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [avx-512-vbmi](<https://devfeed.tech/tags/avx-512-vbmi.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [java](<https://devfeed.tech/tags/java.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>), [jira](<https://devfeed.tech/tags/jira.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [software-security](<https://devfeed.tech/tags/software-security.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Java4Shell (CVE-2026-114938) is an out-of-bounds write in Java's AVX-512 VBMI Base64 decoder. It affects specified Java 17+ builds on x86-64 Intel and AMD systems with the required CPU features when malformed Base64 reaches the decoder; some applications are reportedly exploitable without login by default, while others require authentication. Researchers describe a memory-layout technique for turning the fixed-byte overflow into controlled writes and reads, but their application-specific exploits are unpublished, and independent tests cited here reproduced crashes or memory reads rather than remote code execution. Oracle, OpenJDK, Corretto and Azul list fixes; Red Hat was still preparing updates, and several vendors had not listed fixed builds when checked. Update the Java runtime, restart services, and rebuild and redeploy containers. Until then, the excerpt recommends disabling Base64 intrinsics or, on x86-64 only, AVX-512. ARM64 is not affected by this decoder path. The excerpt says no exploitation was known to Canada's Cyber Centre and the flaw was not in CISA's KEV catalog at the time checked.

### Source excerpt

Java4Shell (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak on Java 17+ AVX-512 VBMI Servers A Java flaw called Java4Shell can let attackers without an account run their own code on Jira, Jenkins, Keycloak, and three other widely used applications, says Calif, the security research firm that ... Read more Published Date: Nov 18, 2026 (8 hours, 38 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-114938 CVE-2026-118383

## Java4Shell: What Keycloak admins need to do (CVE-2026-114938)

DevFeed: [Java4Shell: What Keycloak admins need to do (CVE-2026-114938)](<https://devfeed.tech/articles/java4shell-what-keycloak-admins-need-to-do-cve-2026-114938-141089.md>)

Original publisher: [Read original article](<https://www.keycloak.org/2026/11/java4shell-vulnerability-cve-2026-114938>)

Author: The Keycloak team

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

Content type: tutorial

Language: en

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

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [avx](<https://devfeed.tech/tags/avx.md>), [avx-512-vbmi](<https://devfeed.tech/tags/avx-512-vbmi.md>), [base64](<https://devfeed.tech/tags/base64.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [container](<https://devfeed.tech/tags/container.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [decoder](<https://devfeed.tech/tags/decoder.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [idm](<https://devfeed.tech/tags/idm.md>), [java](<https://devfeed.tech/tags/java.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [machine](<https://devfeed.tech/tags/machine.md>), [memory](<https://devfeed.tech/tags/memory.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

CVE-2026-114938 ("Java4Shell") affects Keycloak when it uses an unpatched OpenJDK build from 17.0.6 onward, the x86-64 host exposes AVX-512 VBMI, and the live JVM has Base64 intrinsics enabled. The flaw can corrupt memory through pre-authentication requests; researchers report demonstrating remote code execution. Check the Java runtime, CPU feature, and effective flags on every Keycloak node, including failover and rollout nodes. Red Hat's preferred interim mitigation is `-XX:-UseBASE64Intrinsics`, followed by restarting and verifying each JVM with `jcmd`; limiting AVX to AVX2 is another relevant condition, but the post favors disabling the intrinsic. The Operator is a separate JVM and needs its own mitigation; configuring it does not configure managed Keycloak pods. The cited 26.8.2-1 and 26.8.2-2 x86-64 images bundle affected OpenJDK 21.0.13, but image tags alone do not establish exploitability. Use a vendor-confirmed fixed runtime when available; the post says no specific fixed Keycloak image could yet be recommended.

### Source excerpt

Last updated: 18 November 2026, 09:29 UTC If your organization uses Keycloak, please pass this post to the team that operates it, even if you do not run Keycloak yourself. They need to check the Java runtime and the CPU type used by every Keycloak instance. The issue is CVE-2026-114938, known as Java4Shell. The flaw is in OpenJDK's accelerated Base64 decoder, which Keycloak uses to process some requests. On affected systems, a malformed value that Keycloak decodes before authentication can corrupt the Java process's memory. The researchers report that they demonstrated pre-authentication remote code execution against Keycloak. Am I affected? Treat a Keycloak instance as at risk when all of these apply: It runs an unpatched OpenJDK build from 17.0.6 onward, including unpatched OpenJDK 21 and 25 builds. Its x86-64 host or virtual machine exposes the avx512vbmi CPU feature to Java. The running JVM has Base64 intrinsics enabled and has not been limited to AVX2 with -XX:UseAVX=2. As checked on 18 November 2026, the x86-64 Keycloak container images tagged 26.8.2-1 and 26.8.2-2 bundle an affected OpenJDK 21.0.13 build. These image tags alone do not establish whether your deployment is exploitable: check the CPU feature and effective JVM flags as described below. A Keycloak ZIP or TAR.GZ distribution started directly on a host can also be affected; the conditions depend on its Java runtime and CPU, not on whether it runs in a container. Keycloak processes Base64 data on requests that arrive before authentication, so administrators should not assume that a login requirement protects an affected instance. Check every node or virtual machine that can run Keycloak, including failover nodes and nodes used during rolling updates. A check on your workstation does not establish the status of a production deployment. On the Keycloak host or virtual machine, check the CPU feature: grep -m1 '^flags' /proc/cpuinfo | grep -qw avx512vbmi && echo 'AVX-512 VBMI available' If this prints no

## Critical Java4Shell flaw allows RCE attacks on major Java applications

DevFeed: [Critical Java4Shell flaw allows RCE attacks on major Java applications](<https://devfeed.tech/articles/critical-java4shell-flaw-allows-rce-attacks-on-major-java-applications-138608.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/critical-java4shell-flaw-allows-rce-attacks-on-major-java-applications/>)

Author: Lawrence Abrams

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

Content type: news

Language: en

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

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [Java](<https://devfeed.tech/topics/java.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Spring Framework](<https://devfeed.tech/topics/spring-framework.md>)

Tags: [amazon-corretto](<https://devfeed.tech/tags/amazon-corretto.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [apache-solr](<https://devfeed.tech/tags/apache-solr.md>), [artifactory](<https://devfeed.tech/tags/artifactory.md>), [atlassian-jira](<https://devfeed.tech/tags/atlassian-jira.md>), [avx](<https://devfeed.tech/tags/avx.md>), [avx-512-vbmi](<https://devfeed.tech/tags/avx-512-vbmi.md>), [base64](<https://devfeed.tech/tags/base64.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>), [confluence](<https://devfeed.tech/tags/confluence.md>), [critical](<https://devfeed.tech/tags/critical.md>), [critical-vulnerability](<https://devfeed.tech/tags/critical-vulnerability.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [enterprise-applications](<https://devfeed.tech/tags/enterprise-applications.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [java](<https://devfeed.tech/tags/java.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>), [keycloak](<https://devfeed.tech/tags/keycloak.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>), [open-source](<https://devfeed.tech/tags/open-source.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.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>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Java4Shell (CVE-2026-114938) is a memory-corruption flaw in OpenJDK's hardware-accelerated Base64 decoder that can expose memory or enable remote code execution. The excerpt says it affects OpenJDK 17.0.6 and later and derived distributions, but only when the AVX-512 VBMI decoding path runs on supported x86-64 hardware. Researchers demonstrated unauthenticated RCE in Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate, and authenticated RCE in Kafka Broker, Solr, Elasticsearch, Gerrit, and Spinnaker. Exploitation is application-dependent: there is no universal exploit, and attackers need a way to deliver crafted Base64 data to the decoder. Oracle issued patches on November 17; the recommended action is to update. Temporary mitigations are `-XX:-UseBASE64Intrinsics` or, on x86-64, `-XX:UseAVX=2`. The excerpt reports different severity scores: Calif rated it 9.2 on CVSS 4.0, while Oracle rated it 8.1 (High) on CVSS 3.1.

### Source excerpt

A critical vulnerability dubbed Java4Shell in OpenJDK, the open-source implementation of Java, can allow unauthenticated attackers to remotely execute code on popular enterprise applications, including Jenkins, Atlassian Jira, Confluence, and Keycloak. [...]

## Keycloak Client Libraries 26.0.13 released

DevFeed: [Keycloak Client Libraries 26.0.13 released](<https://devfeed.tech/articles/keycloak-client-libraries-26-0-13-released-130798.md>)

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

Author: Keycloak Team

Published: 2026-11-12T00: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>), [client library](<https://devfeed.tech/topics/client-library.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [client](<https://devfeed.tech/tags/client.md>), [error](<https://devfeed.tech/tags/error.md>), [http](<https://devfeed.tech/tags/http.md>), [idm](<https://devfeed.tech/tags/idm.md>), [jackson-3](<https://devfeed.tech/tags/jackson-3.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [keycloak-client-libraries-release](<https://devfeed.tech/tags/keycloak-client-libraries-release.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>), [upstream](<https://devfeed.tech/tags/upstream.md>)

### AI overview

Keycloak Client Libraries 26.0.13 adds OpenJDK 25 support and makes it the default for automated tests. The release also updates the workflow that syncs and submits pull requests for Jackson 3 modules, adapts the client to a renamed upstream internal client, and lists fixes for a failing PolicyEvaluationCompositeRoleTest.testCreate and an AdminClientTest HTTP 401 Unauthorized error. The release advises consulting the migration guide before upgrading; the supplied excerpt does not detail migration changes.

### Source excerpt

Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #235 Support for OpenJDK 25 and update automated tests to use it by default client #239 Include Jackson 3 modules in the workflow which synces and sends PR client #247 Keycloak client needs to be adapted to renamed upstream internal client client Bugs #241 PolicyEvaluationCompositeRoleTest.testCreate is failing client #260 AdminClientTest test error: NotAuthorized HTTP 401 Unauthorized client

## Building a Kubernetes Operator for Workload Identity Federation Across AWS and GCP

DevFeed: [Building a Kubernetes Operator for Workload Identity Federation Across AWS and GCP](<https://devfeed.tech/articles/building-a-kubernetes-operator-for-workload-identity-federation-across-aws-and-gcp-123545.md>)

Original publisher: [Read original article](<https://hackernoon.com/building-a-kubernetes-operator-for-workload-identity-federation-across-aws-and-gcp?source=rss>)

Author: Shankar

Published: 2026-11-09T05:00:03Z

Content type: article

Language: en

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

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [azure](<https://devfeed.tech/tags/azure.md>), [building](<https://devfeed.tech/tags/building.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [gcp](<https://devfeed.tech/tags/gcp.md>), [gcp-workload-identity](<https://devfeed.tech/tags/gcp-workload-identity.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [identity](<https://devfeed.tech/tags/identity.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-operator](<https://devfeed.tech/tags/kubernetes-operator.md>), [kubernetes-operators](<https://devfeed.tech/tags/kubernetes-operators.md>), [myceliam](<https://devfeed.tech/tags/myceliam.md>), [namespaces](<https://devfeed.tech/tags/namespaces.md>), [oauth2-client-credentials](<https://devfeed.tech/tags/oauth2-client-credentials.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [operator](<https://devfeed.tech/tags/operator.md>), [providers](<https://devfeed.tech/tags/providers.md>), [resources](<https://devfeed.tech/tags/resources.md>), [workload-identity](<https://devfeed.tech/tags/workload-identity.md>), [workload-identity-federation](<https://devfeed.tech/tags/workload-identity-federation.md>)

### AI overview

Myceliam is a Kubernetes operator that watches namespaces and ServiceAccounts, then creates and continually reconciles federated trust in supported identity providers (SPIFFE, Keycloak, Auth0) and AWS or GCP. Labels and access-profile CRDs specify identity and target roles or service accounts; an optional namespace allowlist limits provisioning. The operator manages trust, not permissions, and workloads obtain short-lived credentials directly from the IdP and cloud. Keycloak uses per-namespace realms and predictable client IDs; Auth0 uses a shared tenant with per-application grants and injected claims; SPIFFE needs no IdP resources. AWS trust conditions must account for whether tokens carry `azp`, while GCP maps identity to `google.subject` and binds that subject to a service account. Finalizers clean up resources, and periodic reconciliation corrects external drift. Limits include no pruning of stale AWS trust statements, no expiry-based rotation of generated signed-JWT keys, single-instance operation, and a requirement that SPIRE already be installed.

### Source excerpt

myceliam turns Kubernetes Namespaces and ServiceAccounts into the source of truth for identity, create counterpart resources in IDPs and cloud providers.

## CVE-2026-112208 - Keycloak-services: keycloak-services: account takeover via stale sso\_auth note in organization identity-first login

DevFeed: [CVE-2026-112208 - Keycloak-services: keycloak-services: account takeover via stale sso\_auth note in organization identity-first login](<https://devfeed.tech/articles/cve-2026-112208-keycloak-services-keycloak-services-account-takeover-via-stale-sso-auth-note-in-organization-identity-first-login-119255.md>)

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

Author: CVEFEED.io; redhat.com

Published: 2026-11-05T16:05:05Z

Content type: news

Language: en

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

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [password reset](<https://devfeed.tech/topics/password-reset.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [applications](<https://devfeed.tech/tags/applications.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [build-of-keycloak](<https://devfeed.tech/tags/build-of-keycloak.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [cve-2026-112208](<https://devfeed.tech/tags/cve-2026-112208.md>), [identity](<https://devfeed.tech/tags/identity.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [login](<https://devfeed.tech/tags/login.md>), [organization](<https://devfeed.tech/tags/organization.md>), [redhat](<https://devfeed.tech/tags/redhat.md>), [single-sign-on](<https://devfeed.tech/tags/single-sign-on.md>)

### AI overview

In Keycloak's Organization identity-first login flow, an attacker who belongs to multiple organizations can start a login, switch to registration or password reset, and exploit a stale successful-login flag that was not cleared when a user left the session. By supplying a victim's username, the attacker may have the flag treated as proof of the victim's identity, bypassing authentication and gaining access to the victim's account and connected applications. The source rates the issue 8.1 (High), but provides no affected versions or remediation details.

### Source excerpt

CVE ID :CVE-2026-112208 Published : Nov. 5, 2026, 4:05 p.m. | 56 minutes ago Description :A flaw was found in the Organization identity-first login flow of the Keycloak authentication server. Keycloak is an open-source identity and access management solution used to secure modern applications and services. The issue occurs when an attacker who belongs to multiple organizations initiates a login and then switches to a registration or password reset path. During this process, a flag indicating a successful login is not properly cleared when the user is removed from the session. An attacker can then provide a victim's username, and the system incorrectly treats the stale flag as proof of the victim's identity. This allows the attacker to bypass authentication and gain full access to the victim's account and connected applications. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

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

## Keycloak's observability journey: a guide for project maintainers

DevFeed: [Keycloak's observability journey: a guide for project maintainers](<https://devfeed.tech/articles/keycloak-s-observability-journey-a-guide-for-project-maintainers-113142.md>)

Original publisher: [Read original article](<https://opentelemetry.io/blog/2026/devex-keycloak/>)

Author: OpenTelemetry Authors; Docs CC BY

Published: 2026-11-02T15:39:10Z

Content type: article

Language: en

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

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [guide](<https://devfeed.tech/tags/guide.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [interviews](<https://devfeed.tech/tags/interviews.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [observability](<https://devfeed.tech/tags/observability.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [saml](<https://devfeed.tech/tags/saml.md>)

### AI overview

Keycloak's maintainers found that the OpenTelemetry Java agent enabled quick experimentation but added dozens of seconds to startup, so they moved to native Quarkus integration to preserve fast startup. Metrics gave immediate value; tracing helped locate database and LDAP bottlenecks, and exemplars linked metric spikes to representative traces for investigating high-percentile latency. OpenTelemetry support is on by default, but users must enable a component such as tracing to export data. The source also flags operational tradeoffs: unlike pull-based Prometheus, push-based telemetry over an open TCP socket lacks built-in backpressure and raises questions about signal origin and overload. Keycloak uses custom identity-provider attribute prefixes because conventions are not standardized, and its maintainers call for clearer guides and validation tools such as Weaver.

### Source excerpt

As part of an ongoing series, the Developer Experience SIG interviews organizations about their real-world OpenTelemetry deployments to share practical lessons with the broader community. This post features Keycloak, a CNCF project, and looks at the journey from the perspective of project maintainers who add native OpenTelemetry support to the software they ship. If you have ever needed an Identity and Access Management (IAM) solution, there is a good chance Keycloak was on your radar: a widely used, community-driven open source IAM system that secures applications by authenticating both human and non-human users through industry-standard protocols such as OpenID Connect (OIDC), OAuth 2.0, and SAML.

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

## Temporal JWT token authentication

DevFeed: [Temporal JWT token authentication](<https://devfeed.tech/articles/temporal-jwt-token-authentication-102710.md>)

Original publisher: [Read original article](<https://temporal.io/blog/temporal-jwt-token-authentication>)

Author: Adam Quan

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

Content type: article

Language: en

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

Topics: [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [client library](<https://devfeed.tech/topics/client-library.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [configure](<https://devfeed.tech/tags/configure.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [mapping](<https://devfeed.tech/tags/mapping.md>), [refresh](<https://devfeed.tech/tags/refresh.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [sso](<https://devfeed.tech/tags/sso.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [temporal-voices](<https://devfeed.tech/tags/temporal-voices.md>), [token](<https://devfeed.tech/tags/token.md>), [token-authentication](<https://devfeed.tech/tags/token-authentication.md>), [worker](<https://devfeed.tech/tags/worker.md>)

### AI overview

The article outlines JWT authentication for self-hosted Temporal using Keycloak. It assigns machine clients such as Workers a client-credentials flow and human UI or CLI users an interactive login, with Keycloak roles mapped to Temporal's `permissions` claim (for example, `temporal-system:admin`). Temporal's default ClaimMapper reads those claims and its Authorizer checks permissions; the frontend needs JWT verification keys, while the internal frontend remains available for internal cluster traffic. The UI is configured with Keycloak discovery, client credentials, callback URL, and scopes. CLI requests pass a bearer token through `TEMPORAL_GRPC_META_AUTHORIZATION`; SDK clients pass it in `rpc_metadata`. Since tokens expire, the Python example refreshes them in the background by updating client metadata before expiry, avoiding a token request on every API call. The demonstration omits TLS, so tokens sent over the network are vulnerable to interception.

### Source excerpt

Learn how to configure JWT authentication for self-hosted Temporal with Keycloak, including SSO, Worker access, role mapping, and token refresh.

## Advanced authentication for Data Grid in Red Hat OpenShift 4: Keycloak and SSO

DevFeed: [Advanced authentication for Data Grid in Red Hat OpenShift 4: Keycloak and SSO](<https://devfeed.tech/articles/advanced-authentication-for-data-grid-in-red-hat-openshift-4-keycloak-and-sso-97548.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/10/23/advanced-authentication-data-grid-red-hat-openshift-4-keycloak-and-sso>)

Author: Francisco De Melo Junior, Alexander Barbosa Ayala , Suparna Nag

Published: 2026-10-23T13:16:33Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [data-grid](<https://devfeed.tech/tags/data-grid.md>), [integration](<https://devfeed.tech/tags/integration.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [operators](<https://devfeed.tech/tags/operators.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [security](<https://devfeed.tech/tags/security.md>), [single-sign-on](<https://devfeed.tech/tags/single-sign-on.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

The article shows how to delegate Red Hat Data Grid 8 authentication in OpenShift 4 to Red Hat build of Keycloak. Data Grid's console uses the public `datagrid-console` client for OIDC authorization-code login; the server uses the confidential `datagrid-client` to introspect access tokens with Keycloak. The example deploys Keycloak with its operator, PostgreSQL, and a `KeycloakRealmImport` defining clients, roles, and users, while Data Grid is configured through Helm values with its security realm and endpoint. The article also includes a deprecated `KeycloakClient` path for migration from Red Hat SSO and notes that operator subscriptions differ. Its scope excludes LDAP/LDAPS (covered in part 2), Keycloak-to-Data Grid remote cache use, and cross-site integrations, which may be unsupported.

### Source excerpt

This article explains how to configure authentication for Red Hat Data Grid in Red Hat OpenShift 4 by delegating console access control to single sign-on (SSO) using Red Hat build of Keycloak. (Note: Direct directory integration using LDAP/LDAPS follows in part 2 of this series.) What this article covers: The post Advanced authentication for Data Grid in Red Hat OpenShift 4: Keycloak and SSO appeared first on Red Hat Developer.

## Agent Security & Identity (Part 2): Who Are You, Who's Your Agent, And What Should They Be Allowed?

DevFeed: [Agent Security & Identity (Part 2): Who Are You, Who's Your Agent, And What Should They Be Allowed?](<https://devfeed.tech/articles/agent-security-identity-part-2-who-are-you-who-s-your-agent-and-what-should-they-be-allowed-97763.md>)

Original publisher: [Read original article](<https://hackernoon.com/agent-security-and-identity-part-2-who-are-you-whos-your-agent-and-what-should-they-be-allowed?source=rss>)

Author: Alejandro Saucedo

Published: 2026-10-23T11:00:02Z

Content type: article

Language: en

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

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Security](<https://devfeed.tech/topics/security.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2-2](<https://devfeed.tech/tags/2-2.md>), [3](<https://devfeed.tech/tags/3.md>), [3-questions](<https://devfeed.tech/tags/3-questions.md>), [about](<https://devfeed.tech/tags/about.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [account](<https://devfeed.tech/tags/account.md>), [actor](<https://devfeed.tech/tags/actor.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-auth](<https://devfeed.tech/tags/agent-auth.md>), [agent-delegation](<https://devfeed.tech/tags/agent-delegation.md>), [agent-gateway](<https://devfeed.tech/tags/agent-gateway.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agent-orchestration](<https://devfeed.tech/tags/agent-orchestration.md>), [agent-security](<https://devfeed.tech/tags/agent-security.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-security](<https://devfeed.tech/tags/agentic-security.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [ai-agent-identity](<https://devfeed.tech/tags/ai-agent-identity.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-ethics](<https://devfeed.tech/tags/ai-ethics.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [identity](<https://devfeed.tech/tags/identity.md>), [security](<https://devfeed.tech/tags/security.md>), [series](<https://devfeed.tech/tags/series.md>)

### AI overview

The walkthrough demonstrates KAOS enforcing identity and authorization at a gateway on a local KIND cluster. Alice, in the `researchers` group, can invoke `researcher`; Bob, in `support`, is denied. The agent's declared tool and model dependencies supply its permissions, while autonomous `autobot` acts under its own identity and a user-facing agent without a user is denied. Authorization fails closed if the service is unavailable, a choice the article says carries an availability cost and motivates running it with multiple replicas. For GitHub, the Agent Identity Broker stores consented user credentials and exchanges them on a specific outbound route, so the agent does not handle the long-lived token; users can revoke consent independently. The demo uses mock GitHub, so it demonstrates the delegation path, not GitHub's behavior.

### Source excerpt

Part 2 of a 2-part series on agent identity and security

## Agent Security & Identity (Part 1): Who Are You, Who's Your Agent, And What Should They Be Allowed?

DevFeed: [Agent Security & Identity (Part 1): Who Are You, Who's Your Agent, And What Should They Be Allowed?](<https://devfeed.tech/articles/agent-security-identity-part-1-who-are-you-who-s-your-agent-and-what-should-they-be-allowed-93920.md>)

Original publisher: [Read original article](<https://hackernoon.com/agent-security-and-identity-part-1-who-are-you-whos-your-agent-and-what-should-they-be-allowed?source=rss>)

Author: Alejandro Saucedo

Published: 2026-10-21T20:24:35Z

Content type: article

Language: en

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

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Security](<https://devfeed.tech/topics/security.md>), [Open Policy Agent](<https://devfeed.tech/topics/open-policy-agent.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [actor](<https://devfeed.tech/tags/actor.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-identities](<https://devfeed.tech/tags/agent-identities.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agent-orchestration](<https://devfeed.tech/tags/agent-orchestration.md>), [agentgateway](<https://devfeed.tech/tags/agentgateway.md>), [agentic-identity](<https://devfeed.tech/tags/agentic-identity.md>), [agentic-identity-broker](<https://devfeed.tech/tags/agentic-identity-broker.md>), [agentic-security](<https://devfeed.tech/tags/agentic-security.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agntcon](<https://devfeed.tech/tags/agntcon.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-ethics](<https://devfeed.tech/tags/ai-ethics.md>), [ai-identity](<https://devfeed.tech/tags/ai-identity.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [api](<https://devfeed.tech/tags/api.md>), [arcade](<https://devfeed.tech/tags/arcade.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [identity](<https://devfeed.tech/tags/identity.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The article argues that agent security needs distinct user (subject) and agent (actor) identities, plus separate controls for in-cluster access and user-delegated third-party access. A shared bot token obscures attribution, requires broad permissions, and makes individual revocation difficult. Zalando's open-source Agentic Identity Broker addresses delegated access by storing users' encrypted provider tokens, recording scoped, revocable grants, and exchanging credentials through a trusted gateway; it does not provide human login, agent identity, or gateway enforcement. In the described KAOS design, Keycloak supplies user and agent identity, a gateway and Open Policy Agent enforce resource access, and a network policy blocks routes that bypass the gateway. The author emphasizes fail-closed decisions, the availability cost of a required policy service, and that authorization does not prevent poisoned tool output or prompt injection. Agent-specific identity standards remain unsettled, and the broker's documented production use is limited to Zalando's internal platform.

### Source excerpt

Part 1 of a 2-part series on agent identity and security

## High availability for everyone with multi-site Red Hat build of Keycloak on Red Hat OpenShift

DevFeed: [High availability for everyone with multi-site Red Hat build of Keycloak on Red Hat OpenShift](<https://devfeed.tech/articles/high-availability-for-everyone-with-multi-site-red-hat-build-of-keycloak-on-red-hat-openshift-92817.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/10/21/high-availability-for-everyone-with-multi-site-red-hat-build-of-keycloak-on-red-hat-openshift>)

Author: Jerczey Godoy

Published: 2026-10-21T13:02:19Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [redhat](<https://devfeed.tech/topics/redhat.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [availability](<https://devfeed.tech/tags/availability.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Starting with Red Hat build of Keycloak 26.4, stateless multi-site HA supports fallback deployments across independent OpenShift clusters using supported databases and load balancers. It stores cross-site session data in a shared, consistent database while keeping Infinispan caches local, and uses one public OIDC issuer plus `/lb-check` probes so an external load balancer can route around a degraded site. A local two-site proof of concept used synchronous PostgreSQL replication and HAProxy; when Site A's Keycloak instances were stopped, traffic moved to Site B and the tested SPA session and token refresh continued without interruption. The excerpt also reports successful authorization-code-with-PKCE and RFC 8693 token-exchange failover tests. Setup findings include matching the public hostname and issuer across sites, specifying custom ports in the hostname configuration, and disabling OpenShift router stickiness. The demonstration was a LAN lab; it does not establish production performance or requirements.

### Source excerpt

Identity and access management (IAM) is at the very core of your enterprise's runtime infrastructure. When authentication services fail, otherwise healthy application workloads instantly lock up, blocking users and disconnecting platform services. But high-availability setups for these services have historically been operationally complex, rigid, and restricted to heavy cloud architectures. The post High availability for everyone with multi-site Red Hat build of Keycloak on Red Hat OpenShift appeared first on Red Hat Developer.

## \[webapps\] Keycloak 26.7.2 - Unauthenticated Account Takeover

DevFeed: [\[webapps\] Keycloak 26.7.2 - Unauthenticated Account Takeover](<https://devfeed.tech/articles/webapps-keycloak-26-7-2-unauthenticated-account-takeover-93101.md>)

Original publisher: [Read original article](<https://www.exploit-db.com/exploits/52699>)

Author: Abel Maldonado

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

Content type: tutorial

Language: en

Sources: [Exploit-DB.com RSS Feed](<https://devfeed.tech/sources/exploit-db-com-rss-feed.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [password reset](<https://devfeed.tech/topics/password-reset.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>)

Tags: [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [cve-2026-18963](<https://devfeed.tech/tags/cve-2026-18963.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [webapps](<https://devfeed.tech/tags/webapps.md>)

### AI overview

The excerpt describes CVE-2026-18963, a Keycloak password-reset flow bypass that can let an unauthenticated caller reach the password-change form without an emailed link. An unscoped authentication-selector note reopens the email execution; on affected builds, its handler marks the email verified and succeeds without validating the action token. Affected ranges are 26.0.0-26.4.14, 26.5.0-26.6.5, and 26.7.0-26.7.1. Fixes are listed in 26.4.15, 26.6.6, 26.7.2, and the 26.8.0 line. The PoC offers a check using a random nonexistent identifier, which sends no mail or account changes; checking supplied identifiers can set emailVerified for a resolving account. Its password-setting mode completes the takeover and locks out the account holder. It reads endpoints and form fields dynamically to support custom themes, paths, and field names; browser support is optional and imports Playwright only when requested.

### Source excerpt

Keycloak 26.7.2 - Unauthenticated Account Takeover

## Securing AI agent identity with X.509 PKI on AWS

DevFeed: [Securing AI agent identity with X.509 PKI on AWS](<https://devfeed.tech/articles/securing-ai-agent-identity-with-x-509-pki-on-aws-91297.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/securing-ai-agent-identity-with-x-509-pki-on-aws/>)

Author: Deepakkumar Sharma

Published: 2026-10-20T16:03:48Z

Content type: article

Language: en

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

Topics: [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [agent orchestration](<https://devfeed.tech/topics/agent-orchestration.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent-communication](<https://devfeed.tech/tags/agent-communication.md>), [agent-delegation](<https://devfeed.tech/tags/agent-delegation.md>), [agent-framework](<https://devfeed.tech/tags/agent-framework.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent-identity](<https://devfeed.tech/tags/ai-agent-identity.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-guardrails](<https://devfeed.tech/tags/amazon-bedrock-guardrails.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [aws](<https://devfeed.tech/tags/aws.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [delegation](<https://devfeed.tech/tags/delegation.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [multi-agent-ai-systems](<https://devfeed.tech/tags/multi-agent-ai-systems.md>), [ocsp](<https://devfeed.tech/tags/ocsp.md>), [pki](<https://devfeed.tech/tags/pki.md>), [reference-architecture](<https://devfeed.tech/tags/reference-architecture.md>), [request](<https://devfeed.tech/tags/request.md>), [rfc](<https://devfeed.tech/tags/rfc.md>)

### AI overview

The reference architecture links a user to each AI agent and tool call through X.509 certificates, signed delegation, and per-request proof of possession. With Keyfactor EJBCA and AWS services, the application keeps private keys locally, issues separate user and agent certificates, and gives agents an RFC 8693 token scoped to the MCP server. Signed envelopes include timestamps and unique nonces; agents and the MCP server validate signatures, CA trust, roles, audience, identity consistency, and certificate status through OCSP before processing requests. Logout revokes the user and agent certificates, deletes stored secrets, and ends the Keycloak session. The design fails closed if checks fail, including when OCSP is unreachable. Its example uses Amazon Bedrock, Strands Agents, and FastMCP with a database; the article says the pattern can extend to other MCP-compatible tools and frameworks. Distributed deployments may need a shared replay cache, such as ElastiCache.

### Source excerpt

Learn how to secure multi-agent AI systems with cryptographic identity using Keyfactor EJBCA and AWS services. This reference architecture combines signed request envelopes, user-signed delegation assertions, RFC 8693 audience-scoped tokens, and real-time OCSP revocation to prove agent identity and prevent request forgery across agent-to-agent and MCP tool calls.

## Keycloak DevDay 2027: The Call for Papers is open!

DevFeed: [Keycloak DevDay 2027: The Call for Papers is open!](<https://devfeed.tech/articles/keycloak-devday-2027-the-call-for-papers-is-open-90001.md>)

Original publisher: [Read original article](<https://www.keycloak.org/2026/10/keycloak-devday-2027-call-for-papers>)

Author: Niko Köbler, Sebastian Rose

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

Content type: news

Language: en

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

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Hacktoberfest](<https://devfeed.tech/topics/hacktoberfest.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [devday](<https://devfeed.tech/tags/devday.md>), [event](<https://devfeed.tech/tags/event.md>), [identity](<https://devfeed.tech/tags/identity.md>), [idm](<https://devfeed.tech/tags/idm.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [papers](<https://devfeed.tech/tags/papers.md>), [passkeys](<https://devfeed.tech/tags/passkeys.md>), [saml](<https://devfeed.tech/tags/saml.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [security](<https://devfeed.tech/tags/security.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

Keycloak DevDay 2027 is accepting talk proposals through October 24, 2026, for its April 8-9 conference in Darmstadt, Germany. Suggested topics include production operations, extensions, performance and scaling, security, identity standards, and cloud-native integrations. Speakers receive free event access, while travel and accommodation are not covered.

### Source excerpt

📣 It's time to share what you've built, learned and fought with! The Call for Papers for Keycloak DevDay 2027 is open until October 24, 2026. As announced in our Save the Date post back in June, the world's largest Keycloak community conference returns to Darmstadt, Germany, on April 8-9, 2027. And once again, we want the conference day to be shaped by the people who know Keycloak best: you, the community. What we're looking for 📝 Anything Keycloak-related is welcome! To give you some inspiration, we'd love to hear about: Real-world implementations and case studies Migration stories and lessons learned - including the things that went wrong Keycloak core features and new developments Extension development and customization (SPIs, themes, providers, ...) Operating Keycloak in production: deployment, monitoring, upgrades Performance optimization and scaling Security best practices and patterns Identity standards and protocols (OpenID Connect, OAuth 2.x, SAML, passkeys, ...) Integration with cloud-native technologies One thing to keep in mind: everyone at DevDay already knows Keycloak. Please don't submit an introduction talk. Our audience wants to go deep, so bring the details, the code and the war stories. How to submit 👉 Submit your proposal on Sessionize: sessionize.com/keycloak-devday-2027 ⏰ Deadline: October 24, 2026 As a speaker, you get free access to the event (main speaker only, not co-speakers). As a community conference, we keep costs as low as possible, so we can't cover travel or accommodation. Thanks for your understanding! Need some inspiration for your proposal? Check out the talks from previous editions on YouTube: Keycloak DevDay 2026 video playlist Keycloak DevDay 2025 video playlist Keycloak DevDay 2024 video playlist We're looking forward to your submissions - and to seeing you in Darmstadt next April! 🚀 Niko & Sebastian

## Keycloak 26.8.1 released

DevFeed: [Keycloak 26.8.1 released](<https://devfeed.tech/articles/keycloak-26-8-1-released-85893.md>)

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

Author: Keycloak Team

Published: 2026-10-13T00: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>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [2fa](<https://devfeed.tech/tags/2fa.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [cve](<https://devfeed.tech/tags/cve.md>), [delete](<https://devfeed.tech/tags/delete.md>), [github](<https://devfeed.tech/tags/github.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>), [permission](<https://devfeed.tech/tags/permission.md>), [release](<https://devfeed.tech/tags/release.md>), [saml](<https://devfeed.tech/tags/saml.md>), [security](<https://devfeed.tech/tags/security.md>), [sso](<https://devfeed.tech/tags/sso.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Keycloak 26.8.1 is a release with upgrade guidance and a list of resolved issues, including security fixes, weaknesses, and bugs affecting identity, access control, authentication, APIs, and related components.

### 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 #50945 [CVE-2026-15943] OIDC identity provider update reuses masked client secret after token URL changes identity-brokering #51381 [CVE-2026-18569] OIDC broker backchannel logout accepts unsigned forged logout tokens when signature validation is disabled oidc #52321 [CVE-2026-82968] Persistent wrong-account linking through null / GitHub identity provider identity-brokering #53057 [CVE-2026-94001] Admin credential DELETE bypasses denied reset-password permission admin/fine-grained-permissions #53060 [CVE-2026-94000] A delegated admin with only `manage-users` can become `realm-admin` by joining (or being created into) a group that maps an admin role admin/fine-grained-permissions #53070 [CVE-2026-94218] 2FA setup enforcement bypass via /realms/{realm}/login-actions/restart -- #YWH-PGM40475-254 authentication #53071 [CVE-2026-94215] Cross-realm realm resource read/write via per-request session-level cache in RealmCacheSession admin/api #53072 [CVE-2026-94213] Missing user view authorization in the Authorization Services policy evaluation endpoint, possible incomplete fix of CVE-2026-37978 authorization-services #53073 [CVE-2026-94217] UMA scope merge across resource owners via name collision in resolveResourcePermission authorization-services #53111 [CVE-2026-96446] Security vulnerability in Keycloak 26.7.3 -- PAR single-use bypass via prompt=none oidc #53112 [CVE-2026-96445] Conditional OTP trusts skip headers on untrusted proxy paths authentication #53158 [CVE-2026-97177] Generic user update bypasses denied reset-password permission admin/fine-grained-permissions #53159 [CVE-2026-95503] Potential KDC spoofing attack when Kerberos password authentication is enabled authentication #53160 [CVE-2026-97311] Broken access control in Admin REST API: roles/{role-name}/groups discloses groups the caller can

## Keycloak 26.8.0 released

DevFeed: [Keycloak 26.8.0 released](<https://devfeed.tech/articles/keycloak-26-8-0-released-63151.md>)

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

Author: Keycloak Team

Published: 2026-10-01T00: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>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [API](<https://devfeed.tech/topics/api.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [HTTP](<https://devfeed.tech/topics/http.md>)

Tags: [certificate](<https://devfeed.tech/tags/certificate.md>), [consent](<https://devfeed.tech/tags/consent.md>), [credential-management](<https://devfeed.tech/tags/credential-management.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [idm](<https://devfeed.tech/tags/idm.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [keycloak-release](<https://devfeed.tech/tags/keycloak-release.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [saml](<https://devfeed.tech/tags/saml.md>), [security](<https://devfeed.tech/tags/security.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

Keycloak 26.8.0 adds support for SCIM provisioning, stateless multi-cluster deployments, credential issuance and verification, and client secret rotation. The release also introduces preview token delegation for applications such as AI agents, with consent controls and fine-grained authorization.

### Source excerpt

To download the release go to Keycloak downloads. Highlights This release features new capabilities for users and administrators of Keycloak. The highlights of this release are: Issue and verify digital wallet credentials with OID4VCI and OID4VP Automate user provisioning across identity systems with the SCIM API Run multi-cluster deployments without an external cache using stateless mode (now supported) Simpler administration with automatic index creation, reduced memory usage, and enhanced HTTP performance Token exchange delegation for AI agents and automation with consent and FGAP authorization Read on to learn more about each new feature. If you are upgrading from a previous release, also review the changes listed in the upgrading guide. Security and Standards Verifiable Credential Issuance promoted to preview with credential management and revocation The OpenID for Verifiable Credential Issuance (OID4VCI) feature has been promoted from experimental to preview. It can now be enabled with --features=preview or --features=oid4vc-vci. Credential lifecycle management now includes revocation when refresh tokens are revoked, and a new Application Initiated Action (AIA) lets users request credential issuance within an authenticated session. Key attestation is configurable in the admin console with hardened x5c certificate validation following the HAIP profile. This release also adds experimental support for the mdoc format, provided by the new experimental feature oid4vc-mdoc. Integration guides for the Lissi and Valera wallets are available, along with documentation for SD-JWT signing key setup, credential management, and revocation. Example applications are provided in this release (for illustration, not officially supported): Quickstart OID4VCI deployment - a playground for rapid prototyping with mdoc and SD-JWT credentials OID4VCI Demo in Keycloak FAPI playground - available to show the details of the OID4VCI protocol messages exchanged between wallet and issuer, a

## Keycloak 26.7.5 released

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

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

Author: Keycloak Team

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

Content type: release

Language: en

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

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

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

### AI overview

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

### Source excerpt

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

## Apache Polaris with OIDC: Keycloak, Okta, and External Identity Providers

DevFeed: [Apache Polaris with OIDC: Keycloak, Okta, and External Identity Providers](<https://devfeed.tech/articles/apache-polaris-with-oidc-keycloak-okta-and-external-identity-providers-59925.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/apache-polaris-with-oidc-keycloak-okta-and-external-identity-providers/>)

Author: Alex Merced

Published: 2026-09-25T12:43:05Z

Content type: tutorial

Language: en

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

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [okta](<https://devfeed.tech/topics/okta.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>)

Tags: [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.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>), [jwt](<https://devfeed.tech/tags/jwt.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [okta](<https://devfeed.tech/tags/okta.md>)

### AI overview

A practical guide to configuring Apache Polaris with external OpenID Connect identity providers. It explains token validation, claim-to-role mapping, issuer and audience checks, JWKS verification, and production troubleshooting, with examples for Keycloak and Okta.

### Source excerpt

Configure Apache Polaris with an external OIDC provider, map claims to principals and roles, rotate keys, and troubleshoot Keycloak or Okta authentication. The post Apache Polaris with OIDC: Keycloak, Okta, and External Identity Providers appeared first on Dremio.

## Building a Headless Storefront Against the OpenTaberna API

DevFeed: [Building a Headless Storefront Against the OpenTaberna API](<https://devfeed.tech/articles/building-a-headless-storefront-against-the-opentaberna-api-59611.md>)

Original publisher: [Read original article](<https://philipptheserver.com/posts/opentaberna-storefront-against-the-api/>)

Author: Philipp Lehmann (philipp.lehmann@gruppe.ai)

Published: 2026-09-24T22:30:00Z

Content type: tutorial

Language: en

Sources: [Philipp Lehmann](<https://devfeed.tech/sources/philipp-lehmann.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Angular](<https://devfeed.tech/topics/angular.md>), [FastAPI](<https://devfeed.tech/topics/fastapi.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Pydantic](<https://devfeed.tech/topics/pydantic.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [pkce](<https://devfeed.tech/topics/pkce.md>), [Tailwind CSS](<https://devfeed.tech/topics/tailwind.md>)

Tags: [angular](<https://devfeed.tech/tags/angular.md>), [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [code](<https://devfeed.tech/tags/code.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [css](<https://devfeed.tech/tags/css.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [fastapi](<https://devfeed.tech/tags/fastapi.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [pkce](<https://devfeed.tech/tags/pkce.md>), [reference](<https://devfeed.tech/tags/reference.md>), [testing](<https://devfeed.tech/tags/testing.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

A practical guide to building a headless OpenTaberna storefront against an API. It describes an OpenAPI contract generated from FastAPI and Pydantic models, a small Angular and TypeScript client, standard OIDC with PKCE authentication, Stripe Elements payment integration, and frontend layering that keeps business logic and payment responsibilities in the API.

### Source excerpt

A headless storefront for OpenTaberna: a 37-line API client, TypeScript types generated from OpenAPI, and a compiler that catches field typos.

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