question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[CI] Migrate bots to use Authorization HTTP Header

See original GitHub issue

Tracking issue raised by GitHub’s API regarding our CI bots script (bots/code-analysis-bot.js):

On February 12th, 2020 at 21:09 (UTC) your personal access token (public_repo) using octokit.js/16.43.1 Node.js/12.15.0 (Linux 4.15; x64) was used as part of a query parameter to access an endpoint through the GitHub API.

Please use the Authorization HTTP header instead, as using the access_token query parameter is deprecated and will be removed July 1st, 2020.

Depending on your API usage, we’ll be sending you this email reminder once every 3 days for each token and User-Agent used in API calls made on your behalf. Just one URL that was accessed with a token and User-Agent combination will be listed in the email reminder, not all.

Visit https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters for more information.

The access token is publicly available in .circleci/config.yml.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
cortinicocommented, Jan 26, 2022

Fixed by #32891

2reactions
cortinicocommented, Jan 15, 2022

I’m proposing to update the user agent and octokit version to see if this issue is still occuring in the tracker. What do you think 🧐 #32891

Is this needed? As @fabriziobertoglio1987 mentioned I believe this is already solved:

maybe this was solved with #28050 as I can not reproduce

So i think we can just close this issue

Read more comments on GitHub >

github_iconTop Results From Across the Web

GitLab CI/CD job token
You can use a GitLab CI/CD job token to authenticate with specific API endpoints: Packages: Package Registry. Packages API (project-level). Container Registry ( ......
Read more >
Bot accounts - Mattermost Documentation
Use bot accounts to integrate with Mattermost through plugins or the ... To authorize your bot via RESTful API use curl -i -H...
Read more >
Configuration Options - Renovate Docs
If enabled, Renovate will raise a pull request if config file migration is needed ... To use a bare token in the authorization...
Read more >
Access Tokens - JFrog - JFrog Documentation
An access token can be used as a bearer token in authorization headers. This is especially useful for authenticating CI servers with Artifactory ......
Read more >
Authenticate using API keys - Google Cloud
Migrate from PaaS: Cloud Foundry, Openshift ... Request a quote. Pricing Overview ... Authentication at Google · Authentication use cases.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found