The way to access internal GitHub Enterprise resources is changing
From Wednesday 26 June, University of Leeds Single Sign On authentication will be required for internal (University of Leeds-owned) GitHub Enterprise resources. From this date, only current University of Leeds staff and students will be able to access internal GitHub repositories and organisations that are part of the GitHub Enterprise account. This change will help create a more secure, efficient, and user-friendly environment for our students and academic and research communities.
For current University of Leeds staff and students
From Wednesday 26 June, you will be required to use the university’s new Single Sign On authentication method to access University of Leeds-owned GitHub organisations and repositories.
Users with existing GitHub accounts
If you already have a GitHub account, you should log into that account as normal, then when you access any University of Leeds repositories or organisations, you will be asked to enter your usual university login credentials. This will link your university identity to your existing GitHub account – a separate account will not need to be created. When signing in via the new method, you will retain access to any University of Leeds repositories and organisations.
For non-University of Leeds users (‘external collaborators’)
If you are currently (or have recently been) supporting University of Leeds staff or students but are not a member of staff or student, you will lose access to content saved within the University of Leeds GitHub Enterprise account. If you need to retain access to this content, please contact the owner of your GitHub organisation or repository (or the person you are collaborating with at University of Leeds) and ask them to add you as an external collaborator.
You will retain access to any GitHub repositories that are already external to the University of Leeds Enterprise.
What are the benefits of this new sign-in process?
Our priority is to ensure the security and integrity of our systems and this update is a necessary step in that direction. We are committed to consolidating authentication processes to reduce the risk of data breaches resulting from compromised credentials. This new authentication process will enforce consistent security policies and access controls, protecting sensitive academic and research data.
Who should I contact if I have a question?
At the moment, the University doesn't provide any support or management for GitHub, including its additional functionality, features and services. If you have any questions or need assistance, please Submit a request via IT Services.