Part 3: GitHub Integration in SAS Studio – Now even more secure!

4 Likes

The “what” – in SAS Help Center speak

Beginning with SAS Studio stable 2024.12 and LTS 2025.03, direct passwords/PATs entered inside SAS Studio are deprecated. All Git authentication using HTTPS or password‑protected SSH keys must use a credentials domain managed through SAS Environment Manager.

Why it matters

This subtle improvement is more significant than it appears. In this article, I’ll explain why it’s important for academics using SAS Viya for Learners – though the overall concept is relevant to anyone using SAS Viya.

On the surface, GitHub integration in SAS Studio still looks the same in SAS Viya 2025.09LTS.

You can still:

connect to GitHub
use HTTPS or SSH
clone, pull, and push repositories
teach reproducible analytics workflows

So… what changed?

The change is where and how credentials are managed — and that turns out to be a very intentional step forward.

Now… the “what” in plain English

Beginning with SAS Studio stable 2024.12 and LTS 2025.03, direct entry of passwords or Personal Access Tokens (PATs) inside SAS Studio is deprecated.

Instead: all Git authentication (HTTPS or password-protected SSH) now uses a credentials domain managed through SAS Environment Manager.

So… Nothing is broken. Nor is anything taken away.

But authentication is now:

centralized
more secure
and more aligned with enterprise analytics platforms

Why SAS made this change

This shift reflects a broader reality across modern analytics and software development:

Credentials should not live inside tools — they should be managed by platforms.

Storing passwords or tokens directly inside development interfaces:

increases exposure risk
complicates rotation and revocation
doesn’t scale well in shared or cloud environments

By moving Git credentials into SAS Environment Manager, SAS is aligning SAS Studio with:

enterprise security best practices
cloud-native authentication patterns
regulated-industry expectations

This isn’t about making life harder — it’s about making security invisible once it’s done right.

**Why this matters especially for academics**

Here’s the key point for teaching and learning:

🔐 Students are now learning how professional analytics platforms actually work

In the classroom, we often simplify workflows to reduce friction — understandably so. But that simplification sometimes hides important realities students will face in internships, research labs, and full-time roles.

This update introduces learners to:

credential separation (tools vs secrets)
secure authentication patterns
platform-managed access

All without changing the analytic tasks they’re trying to accomplish.

So, consider this a win for learning, if I may be so bold 😊

The teaching opportunity hiding in the upgrade

Let’s delve a bit further into the teaching opportunities here. Rather than framing this as “extra setup,” many instructors may find it useful to say:

“This is something professionals configure once — and then rely on every day.”

From a pedagogical perspective, this change:

reinforces analytics as a system, not just code
supports reproducible, shareable coursework
mirrors workflows used in industry and research
reduces risky credential practices students might otherwise carry forward

In other words, it quietly upgrades how we teach analytics — not just what we teach.

Reassurance: this is a one-time setup

Yes — there are a few more steps than before.

But:

credentials are created once
profiles are reusable
day-to-day Git usage in SAS Studio remains unchanged

And once configured, students and instructors can focus on what actually matters: writing code, collaborating, and learning analytics.

What comes next

The rest of this article is intentionally practical. We’ll walk through:

creating a Git credential domain in SAS Environment Manager
connecting that domain to SAS Studio
setting up a Git profile
and cloning a GitHub repository successfully

Step by step. Screenshot by screenshot. Beginner-friendly. 😊

A quick note: while my screenshots come from SAS Viya for Learners, the same approach applies to standard SAS Viya 2025.09LTS deployments.

If you’ve connected GitHub to SAS Studio before, you’re already most of the way there — this article simply helps you take the last (and more secure) step forward.

Before we start: this happens in two phases

Phase 1: Create a secure Git credential (one-time setup)

This happens in SAS Environment Manager, where you store your GitHub credentials in a managed domain.

Phase 2: Use that credential in SAS Studio

The focus here is SAS Studio, where you will connect your Git profile and clone repositories like before — but now you are backed by the credential domain.

Prerequisite

You’ll need a GitHub Personal Access Token (PAT). If you don’t have one yet, see Part II of my earlier article: GitHub + SAS Studio Integration in SAS Viya for Learners 4 (VFL4) - SAS Support Communities.

Let’s do it!

Demo: Setting up a GitHub repo in SAS Studio

Phase 1: Create a secure Git credential (one-time setup)

Again, this phase lives in SAS Environment Manager and is where you securely store your GitHub credentials. You only need to do this once.

In SAS Viya for Learners, start in the SAS Environment Manager – found here:

Once SAS Environment Manager is open, you’ll land on a general overview page (don’t worry if mine looks busy — that’s to be expected):

Click the My Credentials icon on the left and you’ll likely have a whole lot of nothing. And that’s all good – because it’s time to create your first SAS Viya credential!

Select the New icon in the upper right corner:

A New Credential dialog box appears with Domain options. This is a “slow down, don’t skim” moment — and that’s good:

Select GitAuth… and then you’ll be prompted with some new options:

Almost done with your new credential! Your User ID is your GitHub username. For example, mine is lincolngroves. And the Password is the Personal Access Token you created above. Can I just give you mine?

Click Save when you’ve entered your info to lock in those New Credential settings. You should then see something like:

Credential created! Now, let’s move on over to SAS Studio…

Phase 2: Use that credential in SAS Studio

Our next phase takes place in SAS Studio, where you connect your Git profile and clone repositories just like you’ve always done. Except now it’s backed by a managed credential.

To get us started on Phase 2, move on over to SAS Studio. One way is to click on Develop Code and Flows in the Applications menu:

Step 1 in SAS Studio is to simply create a new folder on the SAS Server, so you can put the contents of the forthcoming cloned repo there. To do so, create a folder in Files >> Home >> casuser >> e.g., RandomData. Like so:

Open Git Repositories. You’ll be prompted to configure a Git connection — this is expected:

Now, follow the prompts and select Options >> Manage Git Connections, like so:

Profile time! The Manage Git Connections window:

Click the button to Add Git profile:

So… much… progress! The Add a Profile window appears:

And let’s keep using the HTTPS connection to GitHub like we’ve used in the past. But in the latest update you’ll notice a refined set of options:

Profile name, Commit author name, and Commit author email are usually the same as those you used in your GitHub profile. I’ll share mine because they’re no big secret. Additionally, for Domain ID, select GitAuth as the domain. This will pull in the credentials that we set up in SAS Environment Manager. Those cumulative changes:

Save the profile by clicking OK. If everything is configured correctly, you’ll see a successful profile, like so:

With this profile, you should now see the Clone or add a Git repository options available:

Yay! Let’s Clone repository. The following dialog box pops up:

To illustrate, I’ll bring in my RandomData-RandomThoughts repo and paste that into Remote repository: https://github.com/lincolngroves/RandomData-RandomThoughts.git
For SAS Server Location, I’ll click on the folder icon:

And then select the RandomData folder that I just created. Then click Clone when you’ve got everything properly specified!

Successful View, Part 1 – the repo:

Successful View, Part 2 – the files:

Wrapping up

GitHub integration in SAS Studio hasn’t been taken away — it’s been grown up.

By moving credentials out of SAS Studio and into SAS Environment Manager, SAS Viya now follows modern security best practices while preserving the workflows that educators, students, and our commercial clients rely on every day. Yes, there’s a bit more setup up front — but it’s a one-time cost that pays off with better security, clearer separation of responsibilities, and a learning experience that more closely mirrors professional analytics environments.

For academics, that’s a win. Students still learn version control, collaboration, and reproducible analytics — now with an added layer of real-world context around secure authentication.

And if you’re looking to go deeper on day-to-day Git usage in SAS Studio, this SAS Communities article still has some great content to get you on your GitHub pushing and pulling merry way:

GitHub + SAS Studio Integration in SAS Viya for Learners 4 (VFL4)
https://communities.sas.com/t5/SAS-Communities-Library/GitHub-SAS-Studio-Integration-in-SAS-Viya-for...

Thanks for reading — and here’s to more secure (and more confident) analytics workflows in SAS Viya.