SPIKE: update the format of API authentication tokens
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 776
- PR merge metrics
- No merged PRs in 30d
Description
**Outcome:**
Determine which tokens are responsible for the email alert coming from GIthub.. For example, is it our keys or the users login tokens.. Need to determine which of those is causing the issue..
**Email from Github**
> We noticed that an application, gitcoin, owned by an organization you are an admin of, gitcoinco, used a token with an outdated format to access the GitHub API on February 28th, 2022 at 13:15 (UTC), with a user-agent header of PyGithub/Python.
>
> In order to provide additional security benefits to all our customers, we recently updated the format of our API authentication tokens. We encourage you to reset any authentication tokens used by this app, as well as tokens used by any other apps you may have, with our [reset token API](https://docs.github.com/en/rest/reference/apps#reset-a-token/).
>
> Alternatively, you can prompt your users to step through the authorization flow again, as outlined in the docs for either [GitHub Apps](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps) and [OAuth Apps](https://docs.github.com/en/developers/apps/authorizing-oauth-apps).
>
> To understand more about this change and why it's important, visit https://github.blog/2021-04-05-behind-githubs-new-authentication-token-formats.
>
> Thanks,
> The GitHub Team
Contributor guide
Assessment
This issue has not been assessed yet.