|
Purpose/Overview:
Rancher has a GitHub token that still uses the old GitHub authentication format.
Reset that token and replace it by a token in the new GitHub authentication format for better security.
Notices from GitHub:
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on August 20th, 2021 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on October 20th, 2021 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on November 20th, 2021 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on December 20th, 2021 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on January 20th, 2022 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on February 20th, 2022 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on March 20th, 2022 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on April 20th, 2022 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on May 20th, 2022 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on June 20th, 2022 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
We noticed that an application, FOLIO Rancher, owned by an organization you are an admin of, folio-org, used a token with an outdated format to access the GitHub API on July 20th, 2022 at 00:00 (UTC), with a user-agent header of Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36).
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.
|