# Why JWT tokens look different from refresh\_token? how can I generate a refresh token?

**URL:** <https://community.auth0.com/t/why-jwt-tokens-look-different-from-refresh-token-how-can-i-generate-a-refresh-token/17009>\
**Category:** JWT.io\
**Created:** [October 21, 2018, 1:05am UTC](https://community.auth0.com/t/why-jwt-tokens-look-different-from-refresh-token-how-can-i-generate-a-refresh-token/17009 "2018-10-21T01:05:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fddayan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/fddayan/32/9356_2.png) [@fddayan](https://community.auth0.com/u/fddayan)\
**Post date:** [October 21, 2018, 1:05am UTC](https://community.auth0.com/t/why-jwt-tokens-look-different-from-refresh-token-how-can-i-generate-a-refresh-token/17009/1 "2018-10-21T01:05:28Z")

</div>

I;m trying to get my idea around refresh tokens. How do I generate a refresh token? why they look different? Is it related to the JWT format?

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [November 5, 2018, 1:30pm UTC](https://community.auth0.com/t/why-jwt-tokens-look-different-from-refresh-token-how-can-i-generate-a-refresh-token/17009/3 "2018-11-05T13:30:54Z")

</div>

Hi there @fddayan!

Great that you’ve got interested in it. Here is a piece of useful content on understanding refresh tokens and how they work:

> **[Understanding Refresh Tokens](https://auth0.com/learn/refresh-tokens)**
>
> Learn about refresh tokens and the role they serve in the authorization process

> **[Refresh Tokens](https://auth0.com/docs/secure/tokens/refresh-tokens)**
>
> Describes how refresh tokens work to allow the application to ask Auth0 to issue a new access token or ID token without having to re-authenticate the user.

Basically, refresh tokens carry the information necessary to get a new access token. In other words, whenever an access token is required to access a specific resource, a client may use a refresh token to get a new access token issued by the authentication server.

Common use cases include getting new access tokens after old ones have expired, or getting access to a new resource for the first time. Refresh tokens can also expire but are rather long-lived. Refresh tokens are usually subject to strict storage requirements to ensure they are not leaked. They can also be blacklisted by the authorization server.

Let me know if that 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 5, 2018, 1:30pm UTC](https://community.auth0.com/t/why-jwt-tokens-look-different-from-refresh-token-how-can-i-generate-a-refresh-token/17009/4 "2018-12-05T13:30:55Z")

</div>

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