On Monday, 2 September 2019, Acquia Professional Services will begin mandating the use of Two-Factor Authentication (2FA) for all members of our Github organization. At that time, if affected customers have not enabled 2FA on their accounts, those accounts will be removed and affected customers will lose access to any forks of private repositories owned by Acquia.
Maintaining Your Access
If you still need access to private repositories owned by the Acquia Professional Services organization, you will need to enable 2FA on your Github account. Instructions can be found in this article, "Securing your account with two-factor authentication (2FA)."
If you no longer need access to Acquia PSO private repositories (including any forks of those repositories which you have created), you have two options: You can remove yourself from the organization or take no action and you will be removed automatically on 2 September 2019.
Q: What happens if I don't enable 2FA, I am removed from the organization, and then find I need access to the repositories?
If your github access is removed on 2 September 2019 and you discover that you still need access, you must first enable 2FA on your Github account. Once that is completed, please reach out to your contact in Acquia Professional Services or your Account Manager. We can then reinstate your membership.
Q: Will enabling 2FA on my Github account change how I work with git repositories?
If you're using SSH keys to authenticate to Github when working in git (a security measure Acquia strongly recommends), then your command line interactions with repositories hosted at Github will be unchanged.
If you use password-based access, some additional steps are needed. Full details on accessing Github with 2FA can be found in Github's documentation.
Q: I have some additional questions and concerns. Who can I contact?
If you have any questions about this or any other maintenance, you can contact Acquia Support.