Interaction with the Management API from React
So to outline my problem in some bullets before going into more detail:
- I'd like to have some user management functionality exposed in my React application.
- I'd like to be able to list all the users in the organisation if the user is authenticated with the
- I'd like for someone with this
- I'd like for people to be able to amend their own user details regardless of having this role.
- I'd like to do this all client side using the authenticated session in the React application.
I've read https://zitadel.com/docs/support/troubleshooting#accessing-zitadels-apis and got some information but I can't work out how to do these management calls from the client side authenticated user token.
Do I need the Zitadel aud or the {projectId} aud to be able to do this? Current
It's working as expected via zitadel-go client library and the management examples - but it requires a service user as one would expect from a stand alone Go backend deployment.
Where should I start for making this work client side?
- I'd like to have some user management functionality exposed in my React application.
- I'd like to be able to list all the users in the organisation if the user is authenticated with the
Org User Management Zitadel management role.- I'd like for someone with this
Org User Management role be able to add new users and amend existing users in the organisation.- I'd like for people to be able to amend their own user details regardless of having this role.
- I'd like to do this all client side using the authenticated session in the React application.
I've read https://zitadel.com/docs/support/troubleshooting#accessing-zitadels-apis and got some information but I can't work out how to do these management calls from the client side authenticated user token.
Do I need the Zitadel aud or the {projectId} aud to be able to do this? Current
scope is "openid profile urn:zitadel:iam:org:project:id:zitadel:aud"It's working as expected via zitadel-go client library and the management examples - but it requires a service user as one would expect from a stand alone Go backend deployment.
Where should I start for making this work client side?
