Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.
TF 0.13.7
Affected Resource(s)
GCP
google_*
Terraform Configuration Files
# Copy-paste your Terraform configurations here.
#
# For large Terraform configs, please use a service like Dropbox and share a link to the ZIP file.
# For security, you can also encrypt the files using our GPG public key:
# https://www.hashicorp.com/security
#
# If reproducing the bug involves modifying the config file (e.g., apply a config,
# change a value, apply the config again, see the bug), then please include both:
# * the version of the config before the change, and
# * the version of the config after the change.
Debug Output
See attached screenshots pls
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform init
terraform plan
Important Factoids
Have tried using google application default login as well service account key file but had same issue.
References
0000
I'm having a weird issue with TF provider authentication on a local machine from a corporate machine.
It seems to be having provider auth issues within the google provider as per screenshots but does seem to work on a similar build within another corporate machine.
From the TF debug logs, it seems to be trying to authenticate initially with ww.googleapis.com/auth/userinfo then fallback to openidconnect.com/auth which also seems to fail. Having tried authentication with CURL and seen it working, I assume this isn't some corporate proxy related issue.
Hi @rubansiva did you solve this issue? I see that it is an authentication fail, so what is the authentication method that you implemented? You can review the authentication guides on the next links:
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.TF 0.13.7
Affected Resource(s)
GCP
Terraform Configuration Files
Debug Output
See attached screenshots pls
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
Important Factoids
Have tried using google application default login as well service account key file but had same issue.
References
0000
I'm having a weird issue with TF provider authentication on a local machine from a corporate machine. It seems to be having provider auth issues within the google provider as per screenshots but does seem to work on a similar build within another corporate machine.
From the TF debug logs, it seems to be trying to authenticate initially with ww.googleapis.com/auth/userinfo then fallback to openidconnect.com/auth which also seems to fail. Having tried authentication with CURL and seen it working, I assume this isn't some corporate proxy related issue.
Any ideas?