Failure at Error: Error 401 creating VeracodeFlaw label "VeracodeFlaw: Very High": Bad credentials

[omegazeng]

    - name: import flaws as issues
      uses: buzzcode/veracode-flaws-to-issues@v1
      with:
        scan-results-json: 'filtered_results.json'
        github-token: ${{ secrets.GITHUB_TOKEN }}

Run buzzcode/veracode-flaws-to-issues@v1
Processing file: filtered_results.json
Importing pipeline flaws into  xxx/yyy.  2 seconds between imports (to handle GitHub rate limiting)
Creating VeracodeFlaw labels
Failure at Error: Error 401 creating VeracodeFlaw label "VeracodeFlaw: Very High": Bad credentials
    at /home/works/actions-runner/_work/_actions/buzzcode/veracode-flaws-to-issues/v1/label.js:95:23
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Object.createLabels (/home/works/actions-runner/_work/_actions/buzzcode/veracode-flaws-to-issues/v1/label.js:75:9)
    at async importFlaws (/home/works/actions-runner/_work/_actions/buzzcode/veracode-flaws-to-issues/v1/importer.js:5[6](https://git.example.com/xxx/yyy/runs/9223?check_suite_focus=true#step:4:6):5)

[buzzcode]

OK...??

Are you trying to report a bug? Asking for help? Other?

Looks like the problem trying to access your GitHub repo and create an Issue Label. Is your GitHub token correct? Do you have permissions to create Issues (and labels) in your repo?

[omegazeng]

Hi,
GitHub Enterprise Server 3.2.6
Internal Repo

Organization Settings - Actions - General

Default permission is read_all & Write_all
https://docs.github.com/en/enterprise-server@3.2/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token

I don't know how to debug, maybe a compatibility issue?

Thx!

[omegazeng]

I changed to a personal access token with Full control of private repositories.
The same error.

[buzzcode]

After a bit more digging, I'm not sure what's going on in your case. All the code is doing is making this API call: https://docs.github.com/en/rest/reference/issues#create-a-label. It still works in the public github.com, but I can't say what's going on with your Enterprise instance. You could try using something like curl, or Postman, or Insomnia to manually create a label and see what happens.

[omegazeng]

 curl https://git.example.com/api/v3/repos/xxx/yyy/labels \
> -H "Authorization: token ghp_AAAAAAAAAAAAAAAAAAAAAA" \
> -H "Accept: application/vnd.github.v3+json" \
> -X POST \
> -d '{"name": "Veracode"}'
{
  "id": 22673,
  "node_id": "MDU6TGFiZWwyMjY3Mw==",
  "url": "https://git.example.com/api/v3/repos/xxx/yyy/labels/Veracode",
  "name": "Veracode",
  "color": "ededed",
  "default": false,
  "description": null
}

only the API path is different.

[buzzcode]

I'm not sure what you're trying to tell me. Is the second part of your post, the stuff in the brackets with "url":"https://git.example.com/xxx" the response to the curl command? It seems like a really odd response with the URLs mis-matched (git.example.com vs. git.laiye.com).

But if you're saying that curl works, but this Action does not in your Workflow, I'd suspect something is configured wrong with the workflow. A 401 return code means Unauthorized, so perhaps a permission problem?

[omegazeng]

sorry, typo.
I mean curl works