GitLab Service Changes

Updated 11/12/2024 - Maintenance Completed
Users should now be able to access the gitlab service over the web from outside the UW campus network.

We're excited to announce that our GitLab service will soon be accessible from outside the UW campus network. To reduce impacts to your GitLab related workflows, we will be releasing a few changes to GitLab in the coming months:

Tonight (2024-09-30), after scheduled maintenance, a new login option will appear on the GitLab web interface. This new login option will require you to use 2-factor authentication (2FA) via DUO, similar to ARCC's other login pages. We ask that you please test this login method to ensure you can get in and access your repositories. Please let us know immediately if you run into any issues. Note: During this validation period, you will still be able to use the old login page.
Beginning Monday, October 28th (2024-10-28), the old login page will be disabled and the following workflow changes will be put in place:

2FA will be required for access to the GitLab web interface.
Git operations over HTTP(S) will no longer support password-based login. Instead, you must use a personal access token[1] or SSH. Git operations over SSH are preferred.
Access to the GitLab instance cannot be granted via the UWIT-RESEARCH-GITLAB active directory group. ARCC will facilitate user access requests. (Most end-users are not impacted by this change.)

Beginning Monday, November 12th (2024-11-12), GitLab will become accessible from off-campus.

We encourage you to audit all repositories with "Public" visibility (from the repository -> Settings -> "Visibility, project features, permissions" -> Project visibility") for any secrets or other accidentally committed keys prior to November 12th.

[1] - https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html

As always, please feel free to reach out to arcc-help@uwyo.edu with any questions or concerns.