
Solution
First, I manually searched for the GitHub Enterprise
integration within the Okta platform, selecting the
cloud version with internal account support. I
configured the authentication method to use
SAML for the Service Provider (SP), which in this
case was GitHub Enterpise.
STEP 1: Okta SAML App
Configuration
I enabled SAML Single Sign-On (SSO) and configured
the core identity parameters. I specified the Sign-In
URL, the Issuer ID, and uploaded the X.509 public
certificate provided by Okta to authenticate the
assertion signature. This ensured GitHub would only
trust login attempts issued by Okta.
STEP 2: GitHub Enterprise
SSO Configuration
Before running the login testing flow, I double-
checked that the certificate was active and
correctly assigned to the SAML application in
Okta. I also verified that Multi-Factor
Authentication (MFA) was fully enforced for all
members of the Developers group.
STEP 3: SAML Certificate
and MFA After signing in through the login testing flow
using a Chrome extension, I verified the entire
SAML exchange. The extension confirmed that the
SAML assertion was successfully sent from Okta
and received by GitHub. I inspected the payload
to ensure it contained the correct user
attributessuch as name, email, and role.
STEP 4: SAML Assertion
Why SAML? Mainly for its security. Once the user successfully authenticates with the Identity Provider (IDP)—Okta—
the IDP sends a secure assertion to the SP containing user data such as name, role, and email, all structured in XML
format. GitHub then verifies the digital signature and grants access based on the attributes provided.