# Non interactive with refresh token

**URL:** <https://community.auth0.com/t/non-interactive-with-refresh-token/7193>\
**Category:** Get Help\
**Tags:** google, refresh\_token, non-interactive\
**Created:** [June 22, 2017, 2:12am UTC](https://community.auth0.com/t/non-interactive-with-refresh-token/7193 "2017-06-22T02:12:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vaporware.test](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@vaporware.test](https://community.auth0.com/u/vaporware.test)\
**Post date:** [June 22, 2017, 2:12am UTC](https://community.auth0.com/t/non-interactive-with-refresh-token/7193/1 "2017-06-22T02:12:07Z")

</div>

I have a non interactive application that is going to use a google drive to store media, since the google access token expires, how the interactive application can refresh the token without the need to login?

---

<div class="post-metadata">

**Author:** ![mauricio](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mauricio/32/17809_2.png) [@mauricio](https://community.auth0.com/u/mauricio)\
**Post date:** [June 22, 2017, 7:20am UTC](https://community.auth0.com/t/non-interactive-with-refresh-token/7193/2 "2017-06-22T07:20:34Z")

</div>

Have you tried this? [Auth0](https://auth0.com/rules/google-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:** [June 23, 2017, 5:57pm UTC](https://community.auth0.com/t/non-interactive-with-refresh-token/7193/3 "2017-06-23T17:57:16Z")

</div>

If your non interactive client application is some type of backend service that will do those Google drive operations on behalf of an end-user of your application and that end-user has authenticated through Google then you should be able to do the following:

- ensure that you configure Google authentication in such way that a refresh token is issued as part of the user authentication flow (for Google this implies passing an `access_type=offline` when starting the authentication process).
- obtain the refresh token (using the method described [here](https://auth0.com/docs/tokens/idp#renewing-the-token)) and then perform the access token renewal directly with Google.

The above process should allow your service to get renewed access tokens to perform the operations necessary in association with a particular end-user.

---

<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:54am UTC](https://community.auth0.com/t/non-interactive-with-refresh-token/7193/4 "2018-03-02T05:54:51Z")

</div>


