12 Replies
It's not possible according to the docs and https://github.com/zitadel/zitadel/issues/9053 However, it would be essential in order to use meta data outside of Zitadel. Our usecase is that we save our internal IDs on the metadata, but we currently have now way to match our identifier to a Zitadel ID @FFO I remember talking with you about this usecase and you said it's perfect to use meta data for this, but search functionality will come later. What's the current status here?
GitHub
POST /v2/users Add option to query for user metadata · Issue #9053...
Preflight Checklist I could not find a solution in the existing issues, docs, nor discussions I have joined the ZITADEL chat Describe your problem We are heavily using the user metadata. It would b...
Hi @SebastianB let me check with my team
raised it internally, wil get back to you!
@Rajat thanks!
Hey @SebastianB good afternoon, I checked with my team internally and they say that it was not implemented because we where unsure how well that scales because of the potentially high cardinality this can have.
IDs are unique and as a result too many different or unique items in one field, which can make systems slower or harder to scale.
It may not be a problem anymore as there've been a lot of changes since the last time it was discussed so I will wait for a bit more time to come back to you if we can get it done soon enough.
Hi @Rajat Singh thanks for the response. It would be great to have this functionality. Alternatively, I saw that we could create a custom user schema and put our own ID there, but it's not ready for production on your side according to the docs and I'm also not sure if we easily can query custom user schemas as well?
Also, another alternative: We saw that when doing HumanUserImport for creating customers we can optionally set the ID of the zitadel user. However, we have UUIDv4 format and zitadel uses a different one. Would that be compatible? Would we also be able to change existing Zitadel IDs for our own UUIDs?
Hi @Rajat do you have any news on this topic? It's quite central for our current restructuring and we would like to move on.
@Rajat Singh do you have an update?
@SebastianB I don't have an update, do you wanna do a PR for the same?
What do you mean a PR?
The two additional questions?
yes, if you have any suggestions/poc, ideas if you'd like to do it (we're open source :D)
you can do anyone if you'd like
Did you even read the two additional questions?
hi @SebastianB apologies as I mixed you up with some other user perhaps 🤦♂️ , I am looking into this now
I will check with the team, but just for more clarification, is this the one you are talking about if I am right?.
also an update on this, we discussed this more internally, with the new api, this could be doable, but we're checking to be sure.
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
Hi Fabina, thanks for the input. This is an interesting approach indeed. However, currently we create a zitadel account only after our internal client object are created and thus the internal client ids are at the point when we create the zitadel user already generated. Maybe there are indeed a lot of usecases where your solution fits perfectly 👍🏻