Prepare for Git Authentication Changes in SAS Studio on SAS Viya

[#1]

As the tech landscape evolves, so too do the tools and methods we use to secure our digital assets and workflows. If you’re working with Git repositories in SAS Studio on SAS Viya, you’ve likely noticed some changes in the Git authentication. Here’s a concise guide to help you navigate these updates and ensure a smooth transition.

What's Changing?

Since SAS Viya stable release 2024.06 (June 2024), when you access Git repositories in SAS Studio, you’ll encounter a warning message indicating that password-based authentication is being phased out. Clicking on the "More Details" hyperlink will direct you to the SAS documentation, which underscores the necessity of moving to an authentication domain for HTTPS authentication or SSH keys secured by a password.

By December 2024, this will be the only method available for Git repository authentication, so it's crucial to start the transition now.

Watch the following video that explains what is changing and how to adapt your Git profiles.

Cloning a Repository via HTTPS

Let’s walk through cloning a GitHub repository using the HTTPS method:

1. Copy the Repository URL: Obtain the URL from your GitHub repository.
2. Specify a Server Location: This should be an empty folder on a network file system associated with SAS Viya.
3. Create a New Git Profile: Choose the HTTPS option and provide the necessary details:
   • Profile Name
   • Commit Author Name (usually your user ID)
   • Email associated with your user ID
4. Credentials Method: Initially, you can enter a password, but by the end of 2024, you must use an authentication (password) domain. The password here is your GitHub Personal Access Token (PAT).

Storing Credentials in SAS Environment Manager

To store your PAT in My Credentials:

1. Navigate to SAS Environment Manager My Credentials.
2. Create a New Credential:
   • Associate it with an authentication domain (typically created by a SAS Administrator).
   • Store your user ID and the PAT.
   • The interface requires the user ID, although it plays no role in the Git authentication. We recommend you should match the user id in your Git HTTPS profile, inside SAS Studio, for consistency.

Using the Credential in SAS Studio

Once you store your credential in an authentication domain:

1. Go back to SAS Studio.
2. Select your Git profile.
3. Select the Authentication Domain associated with your password.

You can now clone the repository. 

Bonuses

Obtaining a GitHub Personal Access Token

To generate a PAT for GitHub:

1. Go to User Settings -> Developer Settings -> Personal Access Tokens.
2. Select Tokens (Classic) and Generate a New Token.
3. Choose Scopes: The minimal scopes are at least repo and user.
4. Generate and Store the Token in your authentication domain in SAS Environment Manager.

Creating an Authentication Domain (for SAS Administrators)

For SAS Administrators, here's how to create a new authentication domain:

1. Access SAS Environment Manager.
2. Under Security > Domains > Create a New Authentication Domain named, for example, GitAuth.
3. Set the Type to Authentication Password.
4. Add a Description and Select Members: These can be individual SAS users or groups (e.g., a group called "Git Users").
5. Use the administrator credentials, to finalize the domain setup.

Now, Git users can store their credentials in this domain and use it in their Git profiles within SAS Studio.

Conclusion

The move to authentication domains for Git in SAS Studio on SAS Viya is a necessary step towards enhanced security. By following these steps, you can ensure a seamless transition and continue to manage your Git repositories efficiently. Don’t wait until the last minute—start integrating these changes into your workflow today.

Thank you for your time reading this post. If you liked the post, give it a thumbs up! Please comment and tell us what you think. If you wish to get more information, please write me an email.

Find more articles from SAS Global Enablement and Learning here.