MLabs Publications
The many minds at MLabs present news, case studies, editorials, tutorials, whitepapers, Cardano Catalyst proposals, and more.
Three of our fifteen Keycloak tests refuted the thing they were written to prove.
The most useful records in a fifteen-scenario Keycloak upgrade lab are the negative ones. Three tests failed to demonstrate what they were written to demonstrate. Published, because negatives are the cheapest credibility available.
Keycloak 26.7 needs PostgreSQL 13. Keycloak 26.0 didn't.
The minimum supported PostgreSQL major moved from 12 to 13 inside Keycloak major version 26, across what looks like a routine minor bump. We upgraded 26.0.0 on Postgres 12.22 and watched where it stopped.
Keycloak advisory batch 2026-09-16: 1 advisory, 1 high or critical — what clears them
Keycloak's 2026-09-16 advisory batch: one high-severity replay protection bypass, patched in 26.7.4. What clears it, and what breaks on the way there.
Your Keycloak database user has DDL rights. That’s the wrong question.
We gave Keycloak's database user full DDL rights, proved it could create and drop tables seconds before the upgrade, and the migration failed anyway. Here is what actually decides it.