AZ CLI token refresh issue, go-azure-helpers v0.10.0

[easkay-castlight]

Community Note

• 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

Terraform (and AzureAD Provider) Version

Terraform v0.12.16
+ provider.azuread v0.5.1

Affected Resource(s)

All (provider auth issue)

Terraform Configuration Files

N/A

Debug Output

N/A

Panic Output

N/A

Expected Behavior

The Azure AD provider refreshes the token on behalf of the user, as recently fixed in hashicorp/terraform-provider-azurerm#4775.
Could the github.com/hashicorp/go-azure-helpers dependency please be updated to v0.10.0 to incorporate the fixes relating to Azure token refresh?

Actual Behavior

The user receives an error relating to the current operation once the token has expired:

 azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://graph.windows.net/<tenant_id>/<resource>: StatusCode=0 -- Original Error: Manually created ServicePrincipalToken does not contain secret material to retrieve a new access token

Steps to Reproduce

N/A

Important Factoids

N/A

References

• Getting an intermittent failed to refresh Bearer token error when trying to delete my AKS cluster terraform-provider-azurerm#2602
• Dependencies: upgrading Azure/azure-sdk-for-go and hashicorp/go-azure-helpers terraform-provider-azurerm#4775
• https://github.com/hashicorp/go-azure-helpers/releases/tag/v0.10.0
• Azure CLI: refreshing the token fails go-azure-helpers#22
• authentication: using a custom refresh function for Azure CLI Authentication go-azure-helpers#43

[easkay-castlight]

Apologies folks, I didn't realise this had been shipped as part of 0.7.0, since it wasn't mentioned in the CHANGELOG or in the notes on the release. On further investigation of the PR (#169), I can see I need to upgrade my provider version.

Sorry for any bother!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!