# Auth0 Terraform provider: facing 403s when trying to modify an \`auth0\_client\` resource **URL:** \ **Category:** Get Help\ **Tags:** tenants, management-api\ **Created:** [November 29, 2023, 3:16am UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878 "2023-11-29T03:16:17Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![luis.ordaz](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luis.ordaz/32/51527_2.png) [@luis.ordaz](https://community.auth0.com/u/luis.ordaz)\ **Post date:** [November 29, 2023, 3:16am UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878/1 "2023-11-29T03:16:17Z")
I’ve been trying to get an answer for this question, which apparently has been asked before: [Error: 403 Forbidden with Terraform - #9 by luis.ordaz](https://community.auth0.com/t/error-403-forbidden-with-terraform/97194/9). I’ve been able to successfully auto generate my current configuration at my tenant, and I’ve been able to import it into terraform and now I’m keeping state. Nonetheless, when I try to modify a resource, I get this error message: ```auto Error: 403 Forbidden: The account is not allowed to perform this operation, please contact our support team. ``` The application/M2M I’m using has **ALL** scopes enabled. ---
**Author:** ![bharath](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/bharath/32/54612_2.png) [@bharath](https://community.auth0.com/u/bharath)\ **Post date:** [November 29, 2023, 7:20pm UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878/2 "2023-11-29T19:20:59Z")
I am facing the same issue…pls let me know if you have resolved it… ---
**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\ **Post date:** [November 29, 2023, 8:40pm UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878/4 "2023-11-29T20:40:13Z")
Hey there @luis.ordaz and @bharath! Do you see a `require_pushed_authorization_requests` in your `auth0_client` resource? If so, I believe if you omit that (it’s related to a feature flag) this error should be resolved. ---
**Author:** ![luis.ordaz](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luis.ordaz/32/51527_2.png) [@luis.ordaz](https://community.auth0.com/u/luis.ordaz)\ **Post date:** [November 29, 2023, 9:11pm UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878/5 "2023-11-29T21:11:58Z")
Hey @ty.frith : yup, I became aware of that attribute being the culprit and removed it a couple of hours ago. Do you know where we can find documentation explaining these sort of scenarios? ++ I filed a bug a couple of hours ago explaining the _expectation_ around an optional attribute (of having it set in the resource block with a false value and omitting it having the exact same result) ---
**Author:** ![luis.ordaz](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luis.ordaz/32/51527_2.png) [@luis.ordaz](https://community.auth0.com/u/luis.ordaz)\ **Post date:** [November 29, 2023, 9:13pm UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878/6 "2023-11-29T21:13:15Z")
Thanks a ton, btw, for adding context of it being part of a feature flag. ---
**Author:** ![bharath](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/bharath/32/54612_2.png) [@bharath](https://community.auth0.com/u/bharath)\ **Post date:** [November 29, 2023, 9:27pm UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878/7 "2023-11-29T21:27:33Z")
This was the issue…thanks a lot! ---
**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\ **Post date:** [November 29, 2023, 9:33pm UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878/8 "2023-11-29T21:33:29Z")
No problem, happy to help and sorry for the confusion! > [@luis.ordaz](#): > > ++ I filed a bug a couple of hours ago explaining the _expectation_ around an optional attribute (of having it set in the resource block with a false value and omitting it having the exact same result) Thanks @luis.ordaz ! > [@luis.ordaz](#): > > Do you know where we can find documentation explaining these sort of scenarios? It looks like there was a pull request to update the terraform registry docs, I think this particular issue was just an oversight 😕 ---
**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\ **Post date:** [December 13, 2023, 9:34pm UTC](https://community.auth0.com/t/auth0-terraform-provider-facing-403s-when-trying-to-modify-an-auth0-client-resource/121878/9 "2023-12-13T21:34:00Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.