Skip to main content

Is EU hosting enough? An honest answer

· 15 min read
GR Patil
Phase Two

No. EU hosting is not enough on its own, and we would rather write that sentence ourselves than have a procurement questionnaire extract it from us. Choosing an EU region settles one question — where the identity data is stored — and leaves three open: which company you contract with, which laws that company is subject to, and who can reach the data in order to operate it. We are a managed Keycloak vendor whose EU clusters run in Frankfurt and whose contracting entity, Phase Two, Inc., is incorporated in the United States, so we are squarely inside the critique rather than above it. What follows is which parts of a residency claim you can verify without the vendor's cooperation, which parts come down to disclosure, and the buyers for whom EU hosting plus a documented transfer position is genuinely sufficient — and the ones for whom it structurally is not. The fast-moving regulatory facts below were re-checked on 16 November 2026.

Java4Shell (CVE-2026-114938): What Keycloak Operators Need to Do

· 7 min read
Jeff Patzer
Phase Two

Bottom line: if you run Keycloak on x86-64 servers with recent Intel or AMD CPUs, add -XX:-UseBASE64Intrinsics to the JVM today, then move to a patched Java runtime. Java4Shell (CVE-2026-114938), disclosed on November 17, 2026, is a memory-corruption bug in OpenJDK's Base64 decoder, and Keycloak is the first application on the researchers' list of products where they demonstrated remote code execution without authentication, in a default configuration. ARM64 is not affected, which is why Phase Two hosted clusters were never exposed.

Update, November 19, 2026: Red Hat has shipped the patched OpenJDK, the official Keycloak 26.8 images have been refreshed, and every image Phase Two publishes is now on the fixed JDK (21.0.13.1). The tags are listed under the permanent fix.

Send Keycloak events straight to Microsoft Sentinel, Datadog and Google SecOps

· 7 min read
GR Patil
Phase Two

Keycloak webhooks from Phase Two can now send login and admin events directly to Microsoft Sentinel, Datadog Cloud SIEM and Google Security Operations, each in the format that platform's ingestion API and detection content expect. You set a payloadFormat on a webhook, give it the platform's credentials, and events start arriving. There is no log shipper, agent or translation function to run in between.

The feature is open source in keycloak-events 0.70, and it is available today on every Phase Two hosted cluster.

Migrating Azure AD B2C users without password hashes

· 16 min read
GR Patil
Phase Two

Azure AD B2C will not give you password hashes. Microsoft Graph's passwordProfile is a write path — you set a password on an account you are creating — and there is no property, endpoint or support process that reads one back. So moving users to Keycloak means moving profiles, which is easy, and then dealing with credentials, which is the whole project.

There are three patterns, and most migrations use two of them. Broker B2C as an OIDC identity provider and let users keep signing in through it while applications move. Validate the password at first login against B2C and store it locally. Send a reset to whoever is left at the cutover date.

The received wisdom — the pattern that works for Auth0 and Cognito — is that the second one is the default. For B2C it is not, and the reason is in Microsoft's own documentation: the only endpoint that can validate a B2C password from your code is the ROPC endpoint, which is documented as local-accounts-only and explicitly unsupported server-to-server. Start from brokering instead.

Everything below was run against Keycloak 26.8.1 in start-dev; the Java compiles against 26.8.1. Every HTTP status and response body is copied from an actual run.

GDPR and Keycloak: erasure, retention, and residency

· 15 min read
GR Patil
Phase Two

Keycloak gives you a working mechanism for roughly half of what the GDPR asks of an identity provider, no mechanism at all for the other half, and — the part that costs people — one mechanism that looks like it worked and did not. It has no concept of a data subject request, no data export for one person, no retention default other than forever, and no setting anywhere called residency. What it does have is a complete admin API over every record it keeps, which is enough to build the rest if you know which four gaps to fill. This post maps each obligation to the mechanism that actually serves it, tested against Keycloak 26.8.2 on 2026-11-09, including the moment where a user erases their own account and Keycloak writes a fresh record of their username and IP address on the way out.

Native login for Keycloak: sign users in with your app's own screens on iOS and Android

· 6 min read
Jeff Patzer
Phase Two

Today we're opening up native authentication for Keycloak: a set of Keycloak extensions and iOS and Android SDKs that let a mobile app sign users in with its own screens instead of a browser. Passwords, passkeys, TOTP, email and SMS codes, recovery codes, push approvals with number matching, step-up and required actions all run natively, while Keycloak still decides what the user has to do. The SDKs are Apache 2.0, and the code is on GitHub.

Login Tracer: debug SAML and OIDC logins in Chrome DevTools

· 6 min read
Jeff Patzer
Phase Two

Today we're releasing Login Tracer by Phase Two, a free Chrome DevTools extension for debugging SAML and OpenID Connect / OAuth logins. Open DevTools, select the Login Tracer panel, and log in: every SSO request in the tab is decoded, grouped into a login flow, and checked for common misconfigurations, with explanations of the Keycloak setting most likely behind each problem. It requests no permissions and makes no network requests.

Keycloak 26.8.2: 33 CVEs and a Critical SAML Bypass

· 8 min read
GR Patil
Phase Two

Bottom line: upgrade now if Keycloak terminates or brokers SAML; within the week otherwise. Keycloak 26.8.2 fixes 33 CVEs. The one that should move your schedule is critical and needs no credentials — a signature bypass in the SAML HTTP-Redirect binding that upstream describes as leading to full account takeover of federated users. The harder problem is that 26 of the 33 have no published advisory yet, so most of this release carries no severity you can plan against.

The CLOUD Act and your identity provider

· 17 min read
Jeff Patzer
Phase Two

The CLOUD Act does not hand anyone a key to a European data centre. It does something narrower, and for an identity provider more awkward than the usual telling. 18 U.S.C. § 2713 makes the location of data irrelevant to whether a provider under US jurisdiction has to produce it, and the process that reaches most of what an identity provider holds is the cheapest instrument in the Stored Communications Act: a subpoena for subscriber records, no warrant, no judicial finding, and no obligation to tell the customer. Below is what the statute says, which level of process reaches which table in a Keycloak realm (tested on 26.8.1), why the defence the CLOUD Act added does not cover an EU customer's identity data on either of its two conditions, and what a vendor with a US parent can honestly promise. Including us.

Porting Azure AD B2C custom policies to Keycloak

· 15 min read
Jeff Patzer
Phase Two

Most of an Azure AD B2C custom policy maps onto Keycloak configuration rather than code. A user journey becomes an authentication flow, orchestration steps become executions, preconditions become conditional subflows, the claims schema becomes the declarative user profile, and page layouts become themes. None of that is Java.

Three things are not configuration. RESTful technical profiles called mid-journey become a custom Authenticator. Long claims-transformation chains become either several protocol mappers or one script mapper — and the script mapper is a JAR you build, not JavaScript you paste into the console, which surprises people. And orchestration that branches on a computed value rather than on the presence of a claim has no declarative equivalent at all.

Everything below was run against Keycloak 26.8.1 in start-dev. The Java compiles against 26.8.1; every HTTP status and response body is copied from an actual run.