GitHub has announced today(August 12, 2021) that account passwords will no longer be accepted for authenication Git operations starting tomorrow.
This change was first announced last year, in July when git operations would require using an SSH key or token-based authentication. Starting on August 13, 2021 at 9:00 PST we will no longer accept account passwords when authenticating Git operations on Github.com “the company said”. “Instead, token-based authentication/for example peron access OAuth SSH key or GitHub App Installation token) will be required for all authenticated Git operations.
- For developers, if you are a password to authenticate Git operations with GitHub.com today, you must begin using a personal access token over HTTPS (recommended) or SSH key by August 13, 2021 to avoid disruption, if you receive a warning that you are using an outdated third party integration, you should update your client to the latest version
- For integrators, you must authenticate integrations using the web or device authorization flows by August 13, 2021 to and avoid disruption. For more information see Authorizing OAuth Apps and the announcement on the developer blog. If you want to ensure that you’re no longer using password based authentication you can enable two-factor authentication, which requires OAuth or personal access tokens for all authenticated operations via Git and third-party integrations