# Authentication Token endpoint not providing a Refresh Token?

**URL:** <https://community.auth0.com/t/authentication-token-endpoint-not-providing-a-refresh-token/8810>\
**Category:** Get Help\
**Tags:** refresh-tokens\
**Created:** [November 23, 2017, 12:58am UTC](https://community.auth0.com/t/authentication-token-endpoint-not-providing-a-refresh-token/8810 "2017-11-23T00:58:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jc1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jc1/32/7454_2.png) [@jc1](https://community.auth0.com/u/jc1)\
**Post date:** [November 23, 2017, 12:58am UTC](https://community.auth0.com/t/authentication-token-endpoint-not-providing-a-refresh-token/8810/1 "2017-11-23T00:58:17Z")

</div>

We’re trying to call the Authentication Token endpoint with a call like this:

```
curl -X "POST" "https://ourapp.eu.auth0.com/oauth/token" \
     -H 'Cache-Control: no-cache' \
     -H 'Content-Type: application/json' \
     -d $'{
  "password": "PASSWORD",
  "scope": "openid profile offline_access",
  "grant_type": "http://auth0.com/oauth/grant-type/password-realm",
  "realm": "{OUR_REALM}",
  "username": "{USER}",
  "audience": "{AUDIENCE}",
  "client_id": "{CLIENT_ID}"
}'

```

From a Native Client, and the API for that audience is set to Allow Offline Access.  
However, in response we get:

```
{
  "access_token": ...,
  "id_token": ...
  "scope": "openid profile",
  "expires_in": 86400,
  "token_type": "Bearer"
}

```

So I’m not sure what we’re doing wrong. Are we using the flow incorrectly? What is the way we should be authenticating our mobile apps with a refresh token?

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [November 23, 2017, 9:06pm UTC](https://community.auth0.com/t/authentication-token-endpoint-not-providing-a-refresh-token/8810/2 "2017-11-23T21:06:11Z")

</div>

The token endpoint response includes a `scope` value that represents the requested scopes minus the `offline_access` one so one possible explanation is if you have a rule to restrict the issued scopes and that rule restricts the scopes being issued to not include the offline access one. I just updated a sample rule on a previous [question](http://community.auth0.com/questions/8250/multiple-access-level-in-app) to include a note about handling offline access when restricting scopes in rules so if you’re in that situation you may want to look at the linked quesion; have in mind, that the example rule in the linked question makes some assumptions so it should only be used if you consider it applicable also to your scenario.

---

<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:** [March 2, 2018, 5:57am UTC](https://community.auth0.com/t/authentication-token-endpoint-not-providing-a-refresh-token/8810/3 "2018-03-02T05:57:31Z")

</div>


