hi @Rapha is there's any more details you'd like to provide if possible, is there's anything you already tried/tested?. Anything practical use cases/example OR code/curl request maybe?. Or any docs that you already followed/tried?. Thanks
Thanks for giving more info, now that you are already going ahead with Option 3. I think Option 2 was also something that could be achived with a mix of a custom endpoint+Zitadel Actions.
The two step approach I could think of
Create your API endpoint (lets call it /user-claims/user-claims) that returns the required claims for a user create an action post-authentication to set it via actions. You can do a bit of reading about zitadel actions and how can you call your API within actions with http and finally you can read how to set claims from actions here It involves a lots of reading as actions are still fairly new but it was designed with an intention to extend custom usecases/logic that a user might have.
ahh I see, thanks for clarifying that part about the "develop locally" part in great detail, I think there's no out of the box solution as such. if that is a case, you can try running zitadel locally as well? If that's soemthing that might suit your use case? Here's a way to do ti via docker compose could this be a possibility
Looks like you just helped out another community member! Thanks for being so helpful @403882453653127168! You're now one step closer to leveling upโkeep up the amazing peer support!