TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Migrate Users from Keycloak to Zitadel

37 点作者 ffo超过 1 年前

4 条评论

ffo超过 1 年前
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:&#x2F;&#x2F;github.com&#x2F;zitadel&#x2F;passwap#algorithms">https:&#x2F;&#x2F;github.com&#x2F;zitadel&#x2F;passwap#algorithms</a>
dabbz超过 1 年前
A couple of comments from skimming through it. If I&#x27;m migrating from Keycloak, I don&#x27;t need to see how to set it up. I&#x27;ve already got a keycloak instance running if I&#x27;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&#x27;ve already gone through the tedious effort of setting up Keycloak. You&#x27;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&#x27;t see a way to migrate those values over.
snapplebobapple超过 1 年前
for those of us that have no idea about this stuff, why would one want to move from keycloak to zitadel?
评论 #37859790 未加载
评论 #37858473 未加载
BartjeD超过 1 年前
I might give this a try.