Migrating using existing UUIDs #5736
Skyppid
started this conversation in
Ideas and Product Feedback
Replies: 1 comment 2 replies
-
|
Hi @Skyppid , Specifying UUIDs for new users isn't supported through the Admin API or Import API today. If you're self-hosting, writing directly into the Authgear database should work for your migration scenario. You'll just need to make sure all related tables and foreign key references are populated consistently. I'd recommend testing carefully on a staging environment first. I'll note this internally as a feature request for the Import API. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We need to migrate from Keycloak to Authgear. To apply our own rules (which users get into which group, to migrate custom attributes, etc.) we implemented a tool instead of the Import API.
But in any case, both the Admin API and the Import API do not allow to specify UUIDs for new users. Is there a way to do so that is not documented or is it possible you implement that as feature?
Our whole ecosystem relies on those user IDs and by creating new ones the links break. Some parts cannot be updated (EventStore for example), so impact is critically high.
My idea as workaround would be to directly write into the database of Authgear, by that it should be possible to inject the existing UUIDs from Keycloak, right? Or do you see any issue with that?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions