# Token Exchange to act on behalf of another user

**URL:** <https://community.auth0.com/t/token-exchange-to-act-on-behalf-of-another-user/104620>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [April 13, 2023, 11:28am UTC](https://community.auth0.com/t/token-exchange-to-act-on-behalf-of-another-user/104620 "2023-04-13T11:28:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![allinformatix](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/allinformatix/32/44650_2.png) [@allinformatix](https://community.auth0.com/u/allinformatix)\
**Post date:** [April 13, 2023, 11:28am UTC](https://community.auth0.com/t/token-exchange-to-act-on-behalf-of-another-user/104620/1 "2023-04-13T11:28:47Z")

</div>

Hi Community,

We are migrating our IdP to auth0 and I have following usecase, which I could not migrate:

An **admin** user needs to act on behalf of different **enduser** , without the need of the enduser’s password!  
With our old IdP we were able to use grant\_type ‘urn:ietf:params:oauth:grant-type:jwt-bearer’ to request an access token for the admin. After that we use grant\_type ‘urn:ietf:params:oauth:grant-type:token-exchange’ to retreive an access token on behalf of the enduser. We were then logged in as the enduser!

Anyone same situation?  
BR F.M.

---

<div class="post-metadata">

**Author:** ![peter.fernandez](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/peter.fernandez/32/45477_2.png) [@peter.fernandez](https://community.auth0.com/u/peter.fernandez)\
**Post date:** [April 13, 2023, 3:35pm UTC](https://community.auth0.com/t/token-exchange-to-act-on-behalf-of-another-user/104620/2 "2023-04-13T15:35:01Z")

</div>

Hi @allinformatix 👋

Welcome to the community 🕶

The situation you describe appears to suggest some requirement for _impersonation_ and/or (3rd party) _token exchange_ Neither of which Auth0 natively supports out of the box. However, it is possible to achieve some level of each - typically utilising Auth0 [Custom Database Connection](https://auth0.com/docs/authenticate/database-connections/custom-db) functionality. Whilst possible, it’s not a simple solution to describe/implement…at least not securely at any rate. For situations like these I would typically recommend reaching out to [Auth0 Professional Services](https://auth0.com/docs/get-started/professional-services) - either via your (Auth0) Technical Account Manager if you have one or directly via the link provided.

Hope this helps 🙂

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [December 7, 2024, 1:58am UTC](https://community.auth0.com/t/token-exchange-to-act-on-behalf-of-another-user/104620/3 "2024-12-07T01:58:45Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
