Edit: This actually has started happening regularly when executing action via a custom form external source value.
Hi, I use the vRA plugin within vRO to do calls to the vRA8 REST APIs. Occasionally I have seen the following error:
Error fetching access token. Invalid refresh token provided.
This has not happened often, but recently happened a few times within a short period of time, causing issues with some workflows and actions.
Since this is the vRA plugin within vRO, I would not expect to see these kind of errors, as it is all happening within the OOTB plugin and there is no getting tokens with separate commands like with curl, etc. Any ideas what might be causing this?
If you want to use access_token instead of refresh_token, you should update the provider block to use the access_token argument that uses VRA_ACCESS_TOKEN environment variable.
Refer to https://github.com/vmware/terraform-provider-vra/blob/master/website/docs/index.html.markdown#argume... for info on this.
It may also be beneficial to suggest the use of Vault for more sensitive values like refresh tokens for vRA 8 or long ttl API tokens for vRA Cloud. Just a quick link would probably be enough.
We encountered the same issue with 8.5, after a couple of months running the appliance. The only fix I could find is to restart vRO pods on the appliance.
Sad to hear the same issue persists on 8.8