# Unable to enable the refresh\_token legacy grant type **URL:** \ **Category:** Get Help\ **Tags:** auth0-configuration, grant-types, refresh-tokens\ **Created:** [July 10, 2017, 7:17pm UTC](https://community.auth0.com/t/unable-to-enable-the-refresh-token-legacy-grant-type/7440 "2017-07-10T19:17:29Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![casper.kuijjer](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@casper.kuijjer](https://community.auth0.com/u/casper.kuijjer)\ **Post date:** [July 10, 2017, 7:17pm UTC](https://community.auth0.com/t/unable-to-enable-the-refresh-token-legacy-grant-type/7440/1 "2017-07-10T19:17:29Z")
We’ve noticed users of our production environment getting a “Grant type `grant_type` not allowed for the client.” error. This happens when our client side web application needs to use the refresh\_token to get a new id\_token. After analysing this we think that our clients didn’t get the grant\_types populated with all Auth0 legacy grant types. From the Web UI it’s impossible to configure this, the option “Legacy: Delegation Refresh Token” simply isn’t there. We’ve been able to use the Auth0 Management API to add the [http://auth0.com/oauth/legacy/grant-type/delegation/refresh\_token](http://auth0.com/oauth/legacy/grant-type/delegation/refresh_token) grant. After doing this however the Web UI still doesn’t show this option, and worse: making a change to the settings removes the grant. Could you please investigate if and where this went wrong, and make us able to enable or disable this grant type using the Web UI. ---
**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:** [July 10, 2017, 9:24pm UTC](https://community.auth0.com/t/unable-to-enable-the-refresh-token-legacy-grant-type/7440/2 "2017-07-10T21:24:53Z")
In relation to the issue itself, I have seen similar situation happening when the client application in question was not explicitly identified as a first-party client. This is something that I it’s not yet surfaced in the Dashboard, but if the client application in question is a first-party client (it’s developed by you the same owner as the Auth0 account) then you may want to consider doing a PATCH request to the Management API in order to update that client application to explicitly state that it is a firs-party client. The PATCH request would contain the following payload: ``` { "is_first_party": true } ``` If my guess is correct this would resolve your situation and the Dashboard would now show the missing legacy grants and it would also mean that you could update the settings without side-effects. ---
**Author:** ![casper.kuijjer](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@casper.kuijjer](https://community.auth0.com/u/casper.kuijjer)\ **Post date:** [July 10, 2017, 9:35pm UTC](https://community.auth0.com/t/unable-to-enable-the-refresh-token-legacy-grant-type/7440/3 "2017-07-10T21:35:12Z")
Awesome! That indeed does the trick, thanks a lot ---
**Author:** ![casper.kuijjer](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@casper.kuijjer](https://community.auth0.com/u/casper.kuijjer)\ **Post date:** [July 10, 2017, 9:35pm UTC](https://community.auth0.com/t/unable-to-enable-the-refresh-token-legacy-grant-type/7440/4 "2017-07-10T21:35:12Z")
Awesome! That indeed does the trick, thanks a lot ---
**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:55am UTC](https://community.auth0.com/t/unable-to-enable-the-refresh-token-legacy-grant-type/7440/5 "2018-03-02T05:55:15Z")