Skip to main content
GR Patil
Phase Two

GR is the co-founder and CEO of Phase Two, and has been working on Keycloak for 10+ years, and running Phase Two for the past 6. A technology entrepreneur for 30 years, he was a founder at BrightRoll (sold to Yahoo! for $640M), an early engineer at Twitter, and founded or led several successful early-stage startups.

View all authors

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.

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.

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.

Data residency requirements for SaaS authentication

· 16 min read
GR Patil
Phase Two

Data residency requirements for a SaaS authentication service are not one requirement, they are four, and only the first of them is about a region. You have to name where each class of identity data is stored. You have to name a lawful transfer mechanism for every touchpoint outside that region, including remote administrative access, which is a transfer and not an exception to one. You have to hold Article 28 processing terms that say so in writing. And you have to be able to produce an inventory of where the identity data goes after it is stored — the brokers, mail relays, event listeners and relying parties your own realm sends it to. Below is the checklist a data protection officer sends, the document that answers each item, what a thin answer looks like, our own answers including the unflattering ones, and the commands that generate that fourth item from a running Keycloak realm, tested on 26.8.1.

What Azure AD B2C's end of sale actually means

· 10 min read
GR Patil
Phase Two

Azure AD B2C's end of sale means Microsoft stopped selling it to new customers on 1 May 2025 and committed to supporting it until at least May 2030. It is not being shut down. Existing customers keep their tenants, can still create new ones, and keep the SLA, the security updates and the compliance posture. What ended is the roadmap.

One other date is doing a lot of damage. Premium P2 was discontinued on 15 March 2026 for all customers, and tenants moved to P1. That is a pricing-tier retirement, not a tenant retirement — but it has been reported often enough as "B2C shuts down in March 2026" that it is worth saying plainly: your tenant is fine, and you have roughly four years to make a decision rather than four months to execute one.

Four years is enough time to make a good decision and short enough that the one you make now is the one you live with. Here is what the three realistic destinations actually cost.

Keycloak 502 Bad Gateway behind a reverse proxy

· 8 min read
GR Patil
Phase Two

A Keycloak 502 Bad Gateway never comes from Keycloak. RFC 9110 defines 502 as a status a gateway emits about its upstream — so the proxy is telling you it could not get a usable response out of Keycloak, and the explanation is in the proxy's error log rather than anywhere in Keycloak's configuration. Start there, every time. In nginx there are only six lines that produce a 502 in front of Keycloak, each maps to one cause, and three of the six are the Quarkus-era port layout catching out a config written for an older release.

Everything below was reproduced against Keycloak 26.8.1 behind nginx 1.29, and every error string is copied out of a real run.

Data residency vs data sovereignty for your identity provider

· 14 min read
GR Patil
Phase Two

Data residency is a statement about geography: your identity data is stored and processed in a named region and does not leave it. Data sovereignty is a statement about law and control: which legal systems can compel access to that data, and who holds the keys and the administrative credentials that make access technically possible. They are not the same claim, and the gap between them matters more for an identity provider than for almost any other system you run, because the IdP holds a record of every person who can sign in to anything you operate and a log of when and from where they did it. Below: both definitions, each applied to the four classes of data a Keycloak realm actually stores, the point where a region setting stops helping — demonstrated against Keycloak 26.8.1 — and the rubric European buyers have started scoring vendors with.

Migrating from Okta to Keycloak

· 18 min read
GR Patil
Phase Two

Migrating from Okta to Keycloak is not a user migration. The users are the easy part: Okta's Users API hands you profiles and group membership, and Keycloak's partial-import endpoint takes them. Two other things decide how long this takes. Okta will not give you password hashes — they are an import-only field, so every user either resets a password or authenticates through Okta one last time while you drain. And every SAML and OIDC application has to be re-pointed by hand, one at a time, because the assertion consumer URL, the entity ID and the signing certificate all change when the identity provider does.

So the schedule is set by the app inventory, not by the user count. A thousand users is one afternoon. Forty SAML apps is a quarter. Everything below was run against Keycloak 26.8.1 in start-dev, and the Okta side is from Okta's published API specification, read on 2026-10-19.