Questions related to integrating Zitadel with my application
I'm struggling to understand something related to using an identity platform like Zitadel with my application. For example, I often see websites that the user can register, login, reset credentials, has a profile page, can see the sessions and everything seems to be in the same application, nothing external like I often see with identity platforms that has the login page and everything separated that I must redirect the user. I understand this can be personalized and a few often has UI elements that we can use to make it feel like the user is not doing something externally but what I'm mostly struggling with is in the backend.
Identity platforms has their own internal tables and states to handle things but my application also needs the user table and other information for relations and the identity platforms often gets that part of handling most things about the user and that is what makes me confused. If the identity platform is handling the user table, how am I going to internally connect that user with other things like posts (for example)? How do normally applications that use identity platforms handle this situation? I have to duplicate things like have an user registered in the identity plaform and one in my application and sync things up? Or there's a better way of doing that and I'm missing out?
Thank you
1 Reply
Hi @theprobugmaker, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. [Use case for User Metadata, provision user to external system][(11) ]:
Discusses how you can use ZITADEL user metadata to link your internal application user table with ZITADEL users, for example by storing an internal user ID or a "registered" flag in ZITADEL metadata, and using that to correlate between your app and ZITADEL.
2. [OAuth / Onboard User with additional Meta-Data][(9) ]:
Covers approaches for onboarding users and associating additional metadata, including storing information in ZITADEL metadata to bridge between your user model and ZITADEL's.
Feel free to tag @Ask Inkeep with additional questions.
Got it. Tagging @Rajat for additional help.