# Social Sign In Refresh Token and Access Token

**URL:** <https://community.auth0.com/t/social-sign-in-refresh-token-and-access-token/195750>\
**Category:** Get Help\
**Tags:** apis, application\
**Created:** [December 24, 2025, 3:52pm UTC](https://community.auth0.com/t/social-sign-in-refresh-token-and-access-token/195750 "2025-12-24T15:52:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![minthu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/minthu/32/71179_2.png) [@minthu](https://community.auth0.com/u/minthu)\
**Post date:** [December 24, 2025, 3:52pm UTC](https://community.auth0.com/t/social-sign-in-refresh-token-and-access-token/195750/1 "2025-12-24T15:52:34Z")

</div>

"Hello everyone,

I am currently implementing Social Sign-in using Auth0 (without using Universal Login).

My issue is that I want to validate the **ID Token** received from the mobile side on my backend, perform the auth checks, and then issue an **Access Token** and **Refresh Token** back to the mobile app.

I’ve researched this and found a grant type called **‘Custom Token Exchange,’** but apparently, it is only available for B2B/Enterprise plans. Is there any other way to achieve this? How do people usually handle this?

At the moment, I am considering just generating a custom JWT directly from my own app/backend. Any advice?"

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [December 30, 2025, 9:23pm UTC](https://community.auth0.com/t/social-sign-in-refresh-token-and-access-token/195750/3 "2025-12-30T21:23:03Z")

</div>

Hi @minthu

Welcome to the Auth0 Community!

I am sorry about the delayed response to your question!

Regarding the matter, the specified grant is indeed available for B2B and Enterprise plans, however, there is an additional endpoint available on Essentials or Pro plans called [Token Exchange for Native Social](https://auth0.com/docs/api/authentication/token-exchange-for-native-social/token-exchange-native-social) which you will be able to use to exchange tokens. However, this flow can be affected if the social provider changes their token format or if Auth0 deprecates support for the specific social login and it is not recommended.

Also, I would not recommend generating a custom JWT and handling the session in your own backend due to the fact that you will be losing access to certain Auth0 features, your API must be configured to handle your own private key accordingly and you will also experience session fragmentation where you will need to handle both an Auth0 session and the session generated by your application. Basically, instead of using Universal Login and Auth0 to handle all of these multiple sessions, you would need to handle the social login, JWT generation using the social attributes and then create/handle an Auth0 session.

If you have any other questions, let me know!

Kind Regards,  
Nik

---

<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:** [January 13, 2026, 9:23pm UTC](https://community.auth0.com/t/social-sign-in-refresh-token-and-access-token/195750/4 "2026-01-13T21:23:11Z")

</div>

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