# identity and access management Published articles for identity and access management. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Architecting resilient authentication with Amazon Cognito multi-Region replication DevFeed: [Architecting resilient authentication with Amazon Cognito multi-Region replication]() Original publisher: [Read original article]() Author: Abrom Douglas Published: 2026-09-15T19:00:52Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [Amazon Cognito](), [Replication](), [Authentication](), [identity and access management](), [Amazon Web Services](), [real-time](), [JSON Web Tokens]() Tags: [advanced-300](), [amazon-cognito](), [authentication](), [aws](), [failover](), [identity-and-access-management](), [real-time](), [replication](), [security-blog](), [security-identity-compliance](), [technical-how-to](), [token]() ### AI overview This AWS article explains how Amazon Cognito multi-Region replication supports resilient authentication by replicating user pools across AWS Regions, with eventual consistency, failover, and interoperable sessions and JSON web tokens. It also covers preparation, architecture decisions, and failover strategies for B2C, B2B, and M2M use cases. ### Source excerpt Your consumer identity and access management (CIAM) system is the foundation of your customer experience. It's how users sign in, access services, and engage with your applications. As your business scales across geographies, ensuring authentication is always available becomes a core architectural requirement. However, building multi-Region authentication has traditionally required complex custom replication solutions that [...] ## What is CIAM in 2026 and why does it matter? DevFeed: [What is CIAM in 2026 and why does it matter?]() Original publisher: [Read original article]() Author: Ravleen Kaur Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [identity and access management](), [trust](), [ai-governance](), [Security](), [Artificial Intelligence](), [IAM](), [Generative AI]() Tags: [ai-agents](), [ai-governance](), [email](), [fraud](), [fraud-detection](), [identity](), [identity-and-access-management](), [industry-insights](), [messaging](), [mobile](), [trust]() ### AI overview This article explains how customer identity and access management (CIAM) is evolving from point-in-time password checks into a continuous trust and control layer. It describes CIAM's role in authenticating users, governing delegated authority for AI agents, evaluating risk across channels, and balancing low-friction access with fraud detection. It also distinguishes customer identity from workforce IAM. ### Source excerpt Discover how customer identity and access management (CIAM) uses continuous trust, deepfake defense, and agentic AI governance to protect users. ## Unmasking Cloud Identities: From Behavioral Clustering to Automated Detection DevFeed: [Unmasking Cloud Identities: From Behavioral Clustering to Automated Detection]() Original publisher: [Read original article]() Author: Osher Jacob Published: 2026-09-14T10:00:01Z Content type: article Language: en Sources: [Unit 42]() Topics: [AWS CloudTrail](), [Cloud](), [threat detection](), [Threat Research](), [SIEM, Security, Observability](), [Machine learning](), [Algorithms](), [SQL](), [IAM](), [identity and access management](), [Amazon Web Services]() Tags: [algorithms](), [amazon-web-services-aws](), [analysis](), [aws-cloudtrail](), [cloud](), [cloud-cybersecurity-research](), [cloud-detection](), [devops](), [iam](), [identity-and-access-management](), [logs](), [machine-learning](), [post](), [sql](), [threat-detection](), [threat-research]() ### AI overview This article presents a behavioral clustering model for mapping cloud identities to functional roles using activity patterns from audit logs. It applies unsupervised machine learning with UMAP and HDBSCAN to data from more than 40,000 identities across 125 cloud environments, and shows how the resulting map can support automated threat detection. The article also explains how lightweight heuristics extracted from the map can classify identities at scale using standard SQL, reducing the need for continuous resource-intensive machine learning pipelines. ### Source excerpt We designed a behavioral clustering model to map cloud identity roles from audit logs, enabling continuous threat detection using standard SQL queries. The post Unmasking Cloud Identities: From Behavioral Clustering to Automated Detection appeared first on Unit 42. ## Managing identity source transition for AWS IAM Identity Center DevFeed: [Managing identity source transition for AWS IAM Identity Center]() Original publisher: [Read original article]() Author: Xiaoxue Xu Published: 2026-09-02T20:36:31Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [migration](), [AWS IAM]() Tags: [advanced-300](), [automation](), [aws-iam-identity-center](), [compliance](), [identity-and-access-management](), [migration](), [security-blog](), [security-identity-compliance](), [technical-how-to]() ### AI overview A walkthrough for safely changing the identity source used by AWS IAM Identity Center, including an Active Directory-to-Okta example. ### Source excerpt September 2, 2026: This post was republished to include Active Directory migration strategies and automation for permission sets. AWS IAM Identity Center manages user access to Amazon Web Services (AWS) resources, including both AWS accounts and applications. You can use IAM Identity Center to create and manage user identities within the Identity Center identity store [...] ## How Does CockroachDB Automate SQL User Lifecycle Management? DevFeed: [How Does CockroachDB Automate SQL User Lifecycle Management?]() Original publisher: [Read original article]() Author: Pritesh Lahoti,Biplav Saraf,Sourav Sarangi Published: 2026-08-28T00:00:00Z Content type: tutorial Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [IAM](), [identity and access management](), [active directory](), [Entra ID](), [okta](), [Microsoft]() Tags: [active-directory](), [cockroachdb](), [entra-id](), [iam](), [identity-and-access-management](), [microsoft](), [okta]() ### AI overview The article addresses how CockroachDB automates SQL user lifecycle management and notes that large enterprises commonly rely on identity provider and identity and access management platforms such as Okta, Microsoft Entra ID, Microsoft Active Directory, and Ory. ### Source excerpt Fortune 1000 enterprises widely rely on major Identity Provider (IdP) and Identity and Access Management (IAM) platforms like Okta, Microsoft Entra ID, Microsoft Active Directory, and Ory. ## Break-glass access for Amazon EKS when federated identity fails DevFeed: [Break-glass access for Amazon EKS when federated identity fails]() Original publisher: [Read original article]() Author: Sam Mukherjee Published: 2026-08-26T16:20:28Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon EKS](), [AWS Identity and Access Management (IAM)](), [Infrastructure as code](), [MFA](), [Authorization](), [iac-security](), [migration]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [aws-iam](), [best-practices](), [identity-and-access-management](), [infrastructure-as-code](), [mfa](), [migration](), [technical-how-to]() ### AI overview This post presents a break-glass access pattern for Amazon EKS clusters when a federated identity provider fails. It describes a dedicated cross-account IAM role with enforced, recency-aware MFA, infrastructure-as-code templates, validation tests, and post-incident recovery procedures. ### Source excerpt Implementing break-glass access for Amazon EKS clusters removes the circular dependency where a federated identity provider outage locks you out of the clusters you need to reach to fix it. This post supplies a cross-account IAM role with enforced MFA, infrastructure-as-code templates, validation tests, and a post-incident recovery procedure. ## Fine-Grained Access Control Now Available for All Heroku Customers DevFeed: [Fine-Grained Access Control Now Available for All Heroku Customers]() Original publisher: [Read original article]() Author: Alberto Sigismondi Published: 2026-08-21T17:07:29Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Access Control](), [Security](), [IAM](), [Zero Trust](), [legacy]() Tags: [access-control](), [deploy](), [heroku](), [iam](), [identity-and-access-management](), [least-privilege](), [legacy](), [news](), [permissions](), [pipelines](), [security](), [security-compliance](), [zero-trust]() ### AI overview Heroku announces that Fine-Grained Access Control is available to all customers. The feature replaces fixed legacy roles with capability-based roles and app-specific permissions for roles such as view, deploy, operate, and manage. ### Source excerpt Fine-Grained Access Controls is now available to all Heroku customers. Heroku's legacy system gave you predefined roles like admin, member, or collaborator, each with a fixed bundle of permissions. It replaces that system with fine-grained roles like view, deploy, operate, and manage, with specific capability sets. Access control is managed at an app-specific layer, giving [...] The post Fine-Grained Access Control Now Available for All Heroku Customers appeared first on Heroku. ## Updates to your AWS Sign-In experience DevFeed: [Updates to your AWS Sign-In experience]() Original publisher: [Read original article]() Author: Vaibhav Chowla Published: 2026-08-17T17:22:33Z Content type: release Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services (AWS)](), [AWS IAM](), [identity and access management](), [AWS IAM Identity Center](), [browser]() Tags: [amazon-web-services-aws](), [aws](), [aws-iam](), [aws-iam-identity-center](), [aws-identity-and-access-management-iam](), [browser](), [identity-and-access-management](), [intermediate-200](), [scripted](), [security-blog](), [security-identity-compliance](), [uncategorized](), [updates]() ### AI overview AWS is gradually introducing a redesigned sign-in and sign-up experience to a limited number of customers. The changes add new account access options, unify the initial email entry point, and refresh the session selection page while existing customers continue using their current credentials and sign-in methods. ### Source excerpt Amazon Web Services (AWS) is gradually introducing updates to the AWS Sign-In and sign-up experience to a limited number of customers. We're sharing these changes so you will know what to expect as we gradually make the updated experience available to more customers. These updates include new options for creating and accessing AWS accounts. To [...] ## Avoid Azure secret rotation with secretless authentication DevFeed: [Avoid Azure secret rotation with secretless authentication]() Original publisher: [Read original article]() Author: Cody Murray-Bruce; Ben Johnson-Staub Published: 2026-08-12T00:00:00Z Content type: tutorial Language: en Sources: [Datadog | The Monitor blog]() Topics: [Azure](), [Authentication](), [Entra ID](), [OpenID connect (OIDC)](), [telemetry](), [Terraform](), [migration]() Tags: [authentication](), [azure](), [cli](), [entra-id](), [identity-and-access-management](), [infrastructure-monitoring](), [integration](), [microsoft](), [migration](), [oidc](), [secrets](), [telemetry](), [terraform]() ### AI overview This article explains how Datadog's secretless authentication for Azure replaces long-lived client secrets with federated identity using Microsoft Entra ID and OpenID Connect. It describes the short-lived token flow and configuration or migration options through Quickstart, Terraform, the Azure CLI, or the Azure portal. ### Source excerpt Learn how secretless authentication for Datadog's Azure integration helps prevent telemetry interruptions that result from expired client secrets. ## Why AI Agents Need Dedicated Identity and Access Controls DevFeed: [Why AI Agents Need Dedicated Identity and Access Controls]() Original publisher: [Read original article]() Author: Quentin Packard Published: 2026-07-17T00:00:00Z Content type: opinion Language: en Sources: [Cockroach Labs]() Topics: [AI Agent](), [identity and access management](), [Security](), [Authorization](), [audit trail]() Tags: [ai-agent](), [apis](), [audit-trail](), [identity-and-access-management](), [permission](), [security]() ### AI overview The article argues that production AI agents need dedicated identities and access controls because shared service accounts, broad permissions, and incomplete audit trails make it difficult to determine what agents accessed and why. Traditional IAM was designed around human actors and does not fully address autonomous software processes that act rapidly, access many records, call external APIs, or delegate work to other agents. ### Source excerpt The agent your team just shipped to external users has the ability to read customer records, execute transactions, and call external APIs. ## Responding to the Five Eyes guidance on AI and cyber risk DevFeed: [Responding to the Five Eyes guidance on AI and cyber risk]() Original publisher: [Read original article]() Published: 2026-07-15T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [Cybersecurity](), [Artificial Intelligence](), [Frontier AI](), [Resilience](), [vulnerability](), [chainguard]() Tags: [ai](), [chainguard](), [deployment](), [five-eyes-security](), [government-of-canada](), [identity-and-access-management](), [mythos](), [resilience](), [security](), [software-supply-chain](), [software-supply-chain-security](), [vulnerability]() ### AI overview The article interprets joint Five Eyes guidance warning that frontier AI may increase the speed, scale, and sophistication of cyberattacks. It argues that organizations should strengthen software supply chain security, accelerate vulnerability remediation, reduce unnecessary dependencies, address legacy systems, improve identity and access management, and build cyber resilience into business and development practices. ### Source excerpt The Five Eyes AI guidance urges organizations to strengthen software supply chain security. Learn how Chainguard helps teams stay ahead. ## How CockroachDB and IBM LinuxONE Rockhopper 5 Power Resilient AI Infrastructure DevFeed: [How CockroachDB and IBM LinuxONE Rockhopper 5 Power Resilient AI Infrastructure]() Original publisher: [Read original article]() Author: Kyle Basile Published: 2026-07-07T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [AI Infrastructure](), [NVIDIA DGX](), [CockroachDB](), [ibm](), [Databases](), [AI Development]() Tags: [ai](), [ai-infrastructure](), [availability](), [cockroachdb](), [concurrency](), [consistency](), [customers](), [data](), [digital](), [distributed](), [engineering](), [enterprise](), [failover](), [financial](), [ibm](), [identity](), [identity-and-access](), [identity-and-access-management](), [infrastructure](), [security]() ### AI overview The article explains how enterprise AI workloads increase requirements for continuous data availability, high concurrency, real-time decision-making, and elastic scaling. It presents IBM LinuxONE Rockhopper 5 and CockroachDB as infrastructure and data-platform components for resilient AI applications, including semantic retrieval, embeddings, agent memory, and transactional consistency. ### Source excerpt Why does AI require a new approach to infrastructure? ## Agent identity architectures: Delegated, bounded, and autonomous DevFeed: [Agent identity architectures: Delegated, bounded, and autonomous]() Original publisher: [Read original article]() Author: info@1password.com (Wen Li) Published: 2026-06-26T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [AI Bots](), [CI/CD]() Tags: [ai](), [ai-agent](), [architecture](), [autonomous](), [identity](), [identity-and-access-management](), [security]() ### AI overview The article outlines delegated, bounded, and autonomous authority models for AI agents, focusing on their differing identity, authorization, and threat-model requirements across local and remote deployments. ### Source excerpt This is the second post in a series that follows 1Password's response to NIST's call for input on how those principles should apply to agents. In our last post on agent identity, we introduced why the ability to reason makes agents fundamentally different from traditional machine workloads, why it breaks the assumptions traditional identity and access management was built on, and why real-time attestation establishes agent identity at runtime. This post maps those principles to production agent profiles The agents running in your environment aren't all the same and neither are the risks they carry. A CI/CD pipeline runner and a long-running autonomous coding agent have fundamentally different access needs, threat surfaces, and identity requirements. Traditional IAM has been successful at governing login for humans and machine workloads with predictable behavior, but controlling non-deterministic agentic systems require unique authority models that a single identity architecture cannot fully govern. An agent that starts with access to a QA database may determine mid-task that it needs production access to complete its task, and the architecture governing it has to respond in real time without over-provisioning. That sort of dynamic authorization looks different depending on the type of agent that's running, who authorized it, and what it has access to. At 1Password, we've mapped the AI agent architectures we see in production into delegated, bounded, and autonomous authority models, each with variants for local and remote deployments. In this post, we'll explore the distinct threat models and required controls to secure all six profiles at your organization. The three agent authority models The authority model describes who or what the agent is acting on behalf of, and what accountability chain that creates. Delegated authority: The agent acts on behalf of a named human. The human's identity is the delegation subject, and the agent's actions must be traceable back to ## Automating Identity and Access for FedRAMP 20x KSIs with Teleport DevFeed: [Automating Identity and Access for FedRAMP 20x KSIs with Teleport]() Original publisher: [Read original article]() Author: info@goteleport.com (Nicolas Morris) Published: 2026-06-17T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [audit trail](), [identity and access management](), [Logging](), [Monitoring](), [Security](), [CI/CD](), [Cloud]() Tags: [audit-trail](), [ci-cd](), [credentials](), [fedramp](), [fedramp-20x](), [hardcoded-credentials](), [identity-and-access-management](), [logging](), [monitoring](), [security]() ### AI overview This article explains how FedRAMP 20x changes identity and access compliance toward persistent validation using machine-readable evidence. It describes how unified identity management and audit trails can help address gaps in machine-to-machine authentication and continuous KSI validation. ### Source excerpt Learn how to automate identity and access for FedRAMP 20x KSIs with a unified audit trail for identities, access, and persistent evidence. ## Auth0 joins the Vercel Marketplace DevFeed: [Auth0 joins the Vercel Marketplace]() Original publisher: [Read original article]() Author: Hedi Zandi Published: 2026-06-15T04:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Auth0](), [Vercel](), [Authentication](), [identity and access management](), [Next.js](), [Provisioning](), [dashboards](), [SDKs](), [App]() Tags: [authentication](), [dashboards](), [development](), [identity-and-access-management](), [integration](), [next-js](), [platform](), [production](), [sync](), [vercel]() ### AI overview Auth0 is now available through the Vercel Marketplace for quick integration with Vercel apps. The integration supports Next.js applications through the Auth0 Next.js SDK and provides authentication, user management, hosted dashboards, sessions, roles, automatic application provisioning, and synchronized configuration across Development, Preview, and Production environments. ### Source excerpt You can now add Auth0, a production-ready authentication to your Vercel app in just a few clicks. Built for modern frameworks like Next.js, Auth0 is an identity and access management platform for securing your apps and agentic workflows. This integration enables: Automatic provisioning of an Auth0 application that connects to your Vercel project Out-of-the-box support for your Next.js applications using the Auth0 Next.js SDK Complete user management with hosted dashboards, sessions, and roles Sync authentication configuration across Development, Preview, and Production environments Get started with Auth0 on the Vercel Marketplace. Read more ## Modernize Datadog API authentication with scoped credentials DevFeed: [Modernize Datadog API authentication with scoped credentials]() Original publisher: [Read original article]() Author: Anthony Dagneaux; Bowen Chen Published: 2026-06-09T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [API](), [Authentication](), [OAuth](), [CI/CD](), [MCP Server](), [Security](), [Terraform](), [Artificial Intelligence]() Tags: [agents](), [ai](), [api](), [api-keys](), [audit-trail](), [authentication](), [ci-cd](), [devsecops](), [identity-and-access-management](), [mcp-server](), [oauth](), [security](), [terraform]() ### AI overview Datadog introduces a scoped, identity-aware API authentication model for human users and non-human workloads. It covers Personal Access Tokens, Service Access Tokens, workload identity federation, and customer-managed OAuth clients, addressing CI/CD pipelines, Terraform workflows, autonomous systems, and AI agents. ### Source excerpt Learn how Datadog's new API authentication model replaces application keys with scoped, identity-aware access using PATs, SATs, Workload Identity Federation, and OAuth. ## Announcing Keycloak's Identity Summit: KEYCONF26 DevFeed: [Announcing Keycloak's Identity Summit: KEYCONF26]() Original publisher: [Read original article]() Author: Nathalia Pinesi, Alexander Schwartz Published: 2026-05-02T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [IAM](), [identity and access management](), [OAuth 2.0](), [OpenID connect (OIDC)](), [Single sign-on (SSO)](), [Kubernetes](), [Security]() Tags: [2026](), [conference](), [identity](), [identity-and-access-management](), [idm](), [implementation](), [kerberos](), [keycloak](), [kubernetes](), [ldap](), [oauth2](), [oidc](), [openid-connect](), [saml](), [security](), [sso](), [summit]() ### AI overview Keycloak announces KEYCONF26, its annual Identity Summit for the Keycloak user community, taking place in Prague on October 8, 2026. The event will feature interactive sessions, practical discussions, networking, and a call for speakers and sponsors. ### Source excerpt Our annual conference dedicated to the Keycloak user community returns, with even more content and networking opportunities than last year. It's the perfect place to interact, learn, share, and exchange insights and real-world use cases, network with fellow experts, users, and contributors. 📍 Introducing KEYCONF26 - taking place in Prague on October 8th, 2026! This year's edition of the Keycloak Identity Summit features interactive sessions, and even more opportunities to engage with the people shaping the future of identity and access management. Call for sessions The call for sessions is open until May 24th, 2026 -- we'd love to hear from you! We're looking for sessions on topics such as: Keycloak deployment and operations at scale Human and non-human identities in the world of AI OAuth2, OIDC, and evolving identity standards Security best practices and hardening EU Digital Identity Wallets and eIDAS Migration stories and real-world use cases Extending and customizing Keycloak Submit your proposal now! What to expect at KEYCONF26 Inspiring Keynote Speaker Hear from Hannah Short, Team Lead for Identity and Access Management at CERN, how they are using Keycloak as a highly performant and reliable SSO running on Kubernetes. Connect with like-minded professionals From long-time contributors to those just starting their IAM journey, KEYCONF26 is the perfect place to meet others working with identity, OAuth2, OIDC, and more. Networking lunch Our extended lunch break is designed to help you meet fellow attendees, swap ideas, and build meaningful professional connections in a relaxed setting. Business drinks Stick around after the last session for informal networking over drinks. Want to sponsor this year's Business Drink? Get in touch with us--we'd love to partner with you! Expert sessions and real-world use cases Gain practical insights into Keycloak implementation, security improvements, OAuth2 best practices, and evolving identity standards. Learn how to use EU Digital ## NIST and AI agents: 1Password's approach to agent identity DevFeed: [NIST and AI agents: 1Password's approach to agent identity]() Original publisher: [Read original article]() Author: info@1password.com (Jacob DePriest; Nancy Wang; Jeff Malnick) Published: 2026-04-08T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [AI Agent](), [Authorization](), [Authentication](), [Zero Trust](), [Security](), [Artificial Intelligence](), [identity and access management](), [interoperability](), [IAM](), [Deployment](), [Architecture & Design]() Tags: [ai](), [ai-agents](), [authentication](), [deployment](), [iam](), [identity-and-access-management](), [interoperability](), [security](), [zero-trust]() ### AI overview This article presents 1Password's approach to agent identity for AI agents. It describes identity as a set of challenges involving identification, attestation, enrollment, authentication, and authorization, with an emphasis on interoperability, continuous access decisions, and Zero Trust for reasoning workloads. ### Source excerpt NIST published a concept paper stating, "Organizations need to understand how identity principles such as identification, authentication, and authorization can apply to agents to provide appropriate protections while enabling business value." This post, and the series that follows, is 1Password's response to NIST's call for input on how those principles should apply to agents. At 1Password, we approach security through simplicity. We are developing an agent identity architecture to simplify and enhance the security of AI agents, ensuring interoperability with existing systems. Our approach is built in collaboration with customers, partners, and the standards community. As part of this work, we recently responded to NIST's AI agent authorization paper. Our view is that agent identity is not a single problem. It is a set of challenges spanning identification, attestation, enrollment, authentication, and authorization for machine workloads with reasoning capabilities. The ability to reason is what sets AI agents apart from traditional machine workloads. This post is the first in a multi-part series on why agent-driven systems require us to rethink identity to enable continuous authentication and authorization for reasoning agents, and how that shapes both our response to NIST and our own approach to agent identity. The agent identity problem Where traditional machine workloads have a "set and forget" policy, the nature of reasoning workloads means a static policy can become out of date as the agent interprets and takes its next action. Agents that automatically deploy software are a great example of this escalation chain. A deployment agent begins with access to QA resources, but its access needs evolve when tests pass and may then require access to production services. The principle of Zero Trust maintains that you should provide only the minimum access needed, but infinitely evolving logic makes it difficult to apply the correct access for the lifetime of an agent pr ## Deploying Keycloak on CockroachDB with Phase Two: A Complete Guide DevFeed: [Deploying Keycloak on CockroachDB with Phase Two: A Complete Guide]() Original publisher: [Read original article]() Author: Amine El Kouhen, Ph.D. Published: 2026-01-14T00:00:00Z Content type: tutorial Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Software as a service](), [Databases](), [Authentication](), [Authorization](), [OpenID connect (OIDC)](), [Single sign-on (SSO)](), [consistency](), [Open Source](), [backups](), [patches](), [Entra ID]() Tags: [access-control](), [authentication](), [authorization](), [availability](), [backups](), [cockroachdb](), [consistency](), [databases](), [distributed](), [guide](), [high-availability](), [iam](), [identity-and-access-management](), [keycloak](), [oidc](), [openid-connect](), [patches](), [saas](), [saml](), [security]() ### AI overview This guide explains how Phase Two's managed Keycloak platform can be deployed with CockroachDB to support authentication, authorization, enterprise SSO, and multi-tenant SaaS applications. It describes Keycloak's identity-management capabilities and CockroachDB's globally distributed SQL database, transactional consistency, and tenant isolation. ### Source excerpt Today's SaaS products face twin demands: the digital identity layer must be seamless and enterprise-grade, and the data layer must scale globally while remaining reliably consistent. ## Keycloak announces talks and speakers for the 2025 Identity Summit in Amsterdam DevFeed: [Keycloak announces talks and speakers for the 2025 Identity Summit in Amsterdam]() Original publisher: [Read original article]() Author: Alexander Schwartz Published: 2025-06-27T00:00:00Z Content type: news Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [IAM](), [Model Context Protocol](), [observability]() Tags: [2025](), [event](), [identity-and-access-management](), [idm](), [kerberos](), [keycloak](), [ldap](), [mcp](), [openid-connect](), [saml](), [sso]() ### AI overview Keycloak announces the talks and speakers for its 2025 Identity Summit in Amsterdam. The program covers identity, MCP, observability, dynamic configuration, and Keycloak configuration, with a maintainer panel and networking sessions. ### Source excerpt The talks and speakers have now been announced for Keycloak's Identity Summit. Save your spot today! 📍 KEYCONF25 - taking place in Amsterdam on August 28th, 2025! This year's edition of the Keycloak Identity Summit promises more content, more connections, and even more opportunities to engage with the people shaping the future of identity and access management. Talk highlights Our talks highlight the broad spectrum of the Keycloak ecosystem: How to run it with confidence and securely, how extend it, and how to apply it in existing and new scenarios. See below for a short-list of topics we cover: Human and Workload Identities: Bridging the Gap with Keycloak AI Meets Identity: Managing Keycloak with Natural Language via MCP Observability in Keycloak: Where Does It Hurt? The Event Sorcerer with the Keycloak: The Battle against Dynamic Configuration Protectors of the Realm: Breaking and Fixing Keycloak Configurations A great place to network Networking lunch Our extended lunch break is designed to help you meet fellow attendees, swap ideas, and build meaningful professional connections in a relaxed setting. Meet the maintainers We will have a panel discussion with the maintainers. Ask your questions live and get a response from the experts! Business drinks Stick around after the last session for informal networking over drinks. Want to sponsor this year's Business Drink? Get in touch with us--we'd love to partner with you! Get your ticket and join us! Whether you're a developer, architect, security specialist, or product owner, KEYCONF25 is your opportunity to gain knowledge, grow your network, and contribute to the future of the Keycloak community. 📅 August 28th, 2025 📍 Amsterdam, Netherlands Tickets are now available at keyconf.dev - secure your spot! Want to get involved? Let's continue building a stronger, smarter IAM community--together. We can't wait to see you in Amsterdam! ## The Agentic Identity Journey: Building IAM for Autonomous Actors DevFeed: [The Agentic Identity Journey: Building IAM for Autonomous Actors]() Original publisher: [Read original article]() Author: Ken Adler Published: 2025-06-03T21:53:51Z Content type: opinion Language: en Sources: [Indeed]() Topics: [IAM](), [identity and access management](), [Artificial Intelligence](), [Web]() Tags: [agentic-ai](), [agentic-iam](), [architecture](), [authentication](), [authorization](), [autonomous](), [iam](), [identity](), [identity-and-access](), [identity-and-access-management](), [privacy](), [resilience](), [security](), [software]() ### AI overview This commentary introduces Indeed's perspective on building an Agentic IAM architecture for a future in which autonomous and potentially malicious software agents interact with its platform. It emphasizes precise authorization, trustworthy delegation, verifiable auditing, speed, resilience, and privacy, and presents the post as the first entry in a series. ### Source excerpt Every so often, the web changes in a way that rewires how we live. In the early days, Web 1.0 let us read. It was a window into information -- static pages, digital brochures, news sites. We were spectators peering into a new world. Then came Web 2.0, and we learned to write. We didn't [...] ## OpenTalk Keycloak case study published DevFeed: [OpenTalk Keycloak case study published]() Original publisher: [Read original article]() Author: Alexander Schwartz Published: 2025-05-15T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [IAM](), [identity and access management](), [Security]() Tags: [architecture](), [case-study](), [cncf](), [data-privacy](), [iam](), [identity-and-access-management](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [regulatory](), [saml](), [sso]() ### AI overview This announcement reports that OpenTalk, a videoconferencing solution, uses Keycloak as a secure and scalable Identity and Access Management solution across its services. It highlights OpenTalk's goals around security, user sovereignty, data privacy, and regulatory requirements, and announces the first CNCF case study published for the Keycloak project. ### Source excerpt OpenTalk, a videoconferencing solution, needed a secure and scalable Identity and Access Management (IAM) solution to authenticate users across various services. Keycloak meets OpenTalk's goals for security, user sovereignty, data privacy and regulatory requirements, so they use it in their architecture. Read more on their challenges and the solution in the first CNCF case study published for the Keycloak project! We are now starting to collect all case studies at our case studies page. If you want to share your case study with the Keycloak community, contact me to sort out the details. ## Keycloak at KubeCon EU 2025 DevFeed: [Keycloak at KubeCon EU 2025]() Original publisher: [Read original article]() Author: Ryan Emerson Published: 2025-04-16T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [identity and access management](), [observability](), [openid](), [Single sign-on (SSO)]() Tags: [2025](), [cncf](), [community](), [iam](), [identity-and-access-management](), [idm](), [kerberos](), [keycloak](), [kubecon](), [kubecon-eu](), [ldap](), [observability](), [openid](), [openid-connect](), [saml](), [sso]() ### AI overview Keycloak recaps its presence at KubeCon EU 2025 in London, including its project pavilion, conversations with users, and a talk on the evolution of OpenID Connect and observability in Keycloak. The post also invites user feedback and highlights upcoming Keycloak community events in Japan. ### Source excerpt Keycloak had a very active presence at this year's KubeCon EU in London. This blog presents a few of the highlights as well as ways you can contribute to Keycloak's CNCF journey. Project Pavilion Keycloak hosted a project pavilion stand during Wednesday, Thursday and Friday afternoon slots. Attending the booth were Keycloak contributors Takashi Norimatsu and Yoshiyuki Tabata from Hitachi, alongside Martin Bartos and Ryan Emerson from Red Hat. During these sessions, we had the opportunity to connect with both existing and prospective Keycloak users to talk all things related to Identity and Access Management. Keycloak stickers were as popular as ever, with both the CNCF sticker wall and our own stash completely emptied! It was fantastic to hear firsthand feedback - what's working well and where there's room for improvement. Insights like these are invaluable as we continue to grow the project and shape the future roadmap. If you weren't able to stop by the pavilion, we'd still love to hear from you, please feel free to share your thoughts via the online feedback form. Keycloak Talk Takashi Norimatsu and Ryan Emerson presented a talk titled "Evolving OpenID Connect and Observability in Keycloak". Watch the recording to hear about how OpenID Connect and observability have evolved over the past year in the Keycloak project. A video of the talk is linked below. Thank you to all who attended and asked questions, there were good follow-up conversations that continued well after our time was up. Keycloak Survey Are you a Keycloak user who is deploying in production or just considering starting with Keycloak? We would love to hear more from you about your success stories, what is crucial to your deployments and what can be done better. Please fill out the online Keycloak Survey so we can better understand your use cases. Your story maybe a candidate for a CNCF Case Study. If you would like to share your success story with our community, answer yes to the "Would you be intere ## Managing Machine Identities to Reduce Anonymous Computing Risks DevFeed: [Managing Machine Identities to Reduce Anonymous Computing Risks]() Original publisher: [Read original article]() Author: jason@intellyx.com (Jason Bloomberg) Published: 2025-02-25T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [identity and access management](), [Security](), [Vulnerabilities](), [Network](), [GitHub Actions]() Tags: [ci-cd-pipeline](), [identity-and-access](), [identity-and-access-management](), [network](), [security](), [toolchain](), [vulnerabilities]() ### AI overview The article argues that anonymous computing occurs when infrastructure assets use fictitious or shared identities without identifying the human making a request. It presents machine-identity management as a way to reduce security vulnerabilities without obstructing necessary work. ### Source excerpt It's Finally Time to Embrace Trusted Computing Does your corporate network treat users on VPNs as trusted regardless of who they are? Does your web server connect to its database as a fictitious user with a password in a config file somewhere? Or perhaps the most frightening scenario: did your platform engineer log in as root to configure your CI/CD pipeline toolchain? [Next page]()