You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2021. It is now read-only.
When the admin wishes to update the user's profile, the admin console backend would be calling the Auth User API for the same.
However, to do so, the admin console backend would need to call the Auth User API with the user's token which it doesn't have.
Therefore, the backend would need to generate the same ( a very shortlived one ~ 1min ) and make the necessary API calls to accomplish the administration task.
The text was updated successfully, but these errors were encountered:
@sbose78 could we possibly have the endpoint support both a user's access token and a service account token?
Edit: Actually of course this wouldn't work as we need to be able to identify the user in question.. how about another set of endpoints just for admin console?
When the admin wishes to update the user's profile, the admin console backend would be calling the Auth User API for the same.
However, to do so, the admin console backend would need to call the Auth User API with the user's token which it doesn't have.
Therefore, the backend would need to generate the same ( a very shortlived one ~ 1min ) and make the necessary API calls to accomplish the administration task.
The text was updated successfully, but these errors were encountered: