Skip to content
This repository has been archived by the owner on May 6, 2021. It is now read-only.

Add support for opaque user impersonation #41

Open
sbose78 opened this issue Dec 11, 2018 · 1 comment
Open

Add support for opaque user impersonation #41

sbose78 opened this issue Dec 11, 2018 · 1 comment
Labels
type/enhancement New feature or request

Comments

@sbose78
Copy link
Member

sbose78 commented Dec 11, 2018

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.

@sbose78 sbose78 added the type/enhancement New feature or request label Dec 11, 2018
@xcoulon xcoulon added this to the Sprint 161 milestone Jan 16, 2019
@sbryzak
Copy link
Member

sbryzak commented Jan 17, 2019

@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?

@xcoulon xcoulon modified the milestones: Sprint 161, Sprint 162 Feb 7, 2019
@alexeykazakov alexeykazakov removed this from the Sprint 162 milestone Feb 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants