Since ZITADEL now uses passwap [1] for password hashing, we are now able to allow migrations from Keycloak to ZITADEL.<p>In the past we only supported bcrypt while Keycloak used PBKDF2 ;-)<p>[1] <a href="https://github.com/zitadel/passwap#algorithms">https://github.com/zitadel/passwap#algorithms</a>
A couple of comments from skimming through it. If I'm migrating from Keycloak, I don't need to see how to set it up. I've already got a keycloak instance running if I'm interested in migrating.<p>I would have imagined if you are a Keycloak alternative, migrating would be easier. I would have imagined some kind of built-in integration. Provide a service token from Keycloak into your importer tool and let it run. This feels complicated and error prone.<p>I've already gone through the tedious effort of setting up Keycloak. You'll need some amazing value prop to convince me to set up a whole other system.<p>Additionally, I have more than Users configured on my keycloak. I have auth providers that are setup such as Epic Games, Riot Games, and Steam. I didn't see a way to migrate those values over.