Join Slack
Powered by
Hi, We are using Pactflow in our CICD pipelines to...
# pactflow
j
Jegadeesan Ponnusamy
08/08/2023, 3:08 AM
Hi, We are using Pactflow in our CICD pipelines to record the deployment of a microservice. But we are getting the below error message, whenever I try to record the deployment for an environment using Pacttoken. I am pretty sure that, I am using the ReadWrite token for recording the deployment. So I am not sure why Pactflow is giving this misleading error message. Could someone help me to figure out the root cause of this issue? Error making request to
https://avevasoftwarellc.pactflow.io/pacticipants/platform-catalog-async/versions/2a557f724adad76caff2e2a9596659cd80624f67/deployed-versions/environment/f92b098b-73f7-48e4-9075-ea6153311f15
status=403 Forbidden. Either you are using a read only token for a request that requires a write token (the most likely cause), or you do not have the required permissions. Error making request to
https://avevasoftwarellc.pactflow.io/pacticipants/platform-catalog-sync-api/versions/2a557f724adad76caff2e2a9596659cd80624f67/deployed-versions/environment/f92b098b-73f7-48e4-9075-ea6153311f15
status=403 Forbidden. Either you are using a read only token for a request that requires a write token (the most likely cause), or you do not have the required permissions. Error making request to
https://avevasoftwarellc.pactflow.io/pacticipants/platform-catalog-sync-internal/versions/2a557f724adad76caff2e2a9596659cd80624f67/deployed-versions/environment/f92b098b-73f7-48e4-9075-ea6153311f15
status=403 Forbidden. Either you are using a read only token for a request that requires a write token (the most likely cause), or you do not have the required permissions. Error making request to
https://avevasoftwarellc.pactflow.io/pacticipants/platform-catalog-sync-operations/versions/2a557f724adad76caff2e2a9596659cd80624f67/deployed-versions/environment/f92b098b-73f7-48e4-9075-ea6153311f15
status=403 Forbidden. Either you are using a read only token for a request that requires a write token (the most likely cause), or you do not have the required permissions.
m
Matt (pactflow.io / pact-js / pact-go)
08/08/2023, 3:11 AM
if you are using a read/write token, then you do not have the required permissions (the other part of the error)
Matt (pactflow.io / pact-js / pact-go)
08/08/2023, 3:12 AM
Alternatively, there is an intermediate proxy, and you aren’t authenticated. You can confirm this by adding
--verbose
to the command and seeing what requests/responses are made.
Open in Slack
Previous
Next