Certified: May 22, 2025

Solution Summary

This guide describes GitHub integration with RSA (or ID Plus) using SAML 2.0. Use this information to determine which use case and integration type your deployment will employ.

Use Case

GitHub can be integrated with RSA using My Page SSO and Relying Party. When integrated, users must authenticate with RSA to sign in to GitHub.

Integration Types 

This article describes the configuration steps involved in integrating Microsoft Github with RSA Cloud Authentication service using SAML 2.0 and as a SCIM server

My Page SSO provides Single-Sign-On (SSO) to Microsoft Github users leveraging RSA self-service portal My Page. When integrated, users must authenticate with RSA to sign in Microsoft Github. SP-initiated SSO is supported.

Modern Cloud-hosted SSO with My Page replaces the existing SAML SSO support with the IDR.

Existing SSO integrations using IDR My Applications continue to be supported and will be listed in this document as applicable.

Note: RSA will continue to maintain existing SAML SSO integrations using IDR My Applications. At a to-be-determined future date, RSA will announce the end-of-life (EOL) date for the SAML SSO support with the IDR. For more information Available Now: My Page SSO Enhancements - RSA Community - 680715

Relying Party integration allows Microsoft Github users’ web browsers to be automatically redirected to RSA Cloud Authentication Service for authentication. With Relying Party integration, Cloud Authentication Service can manage either additional authentication only or both primary authentication (for example, user ID and password) and additional authentication depending on the service provider's capability.

SCIM integration allows the administrators of RSA Cloud Authentication Service and end users who exist in the RSA Cloud Authentication Service Unified Directory to be provisioned in Microsoft Github. End users can request access to an application in the My Page portal and gain access to the external application depending on the approver type configured in RSA. Users can also check the status of their submitted requests from My Requests in the My Page portal. 

Supported Features 

This section shows all the supported features by integration type and by RSA components. When integrated with RSA Cloud Authentication Service using SAML 2.0, Microsoft Github users can authenticate with any of the following multi-factor authentications.

GitHub Integration with RSA Cloud Authentication Service

Authentication Methods	RSA MFA API (REST)	RADIUS	Relying Party	My Page SSO
Approve	-	-
LDAP Password	-	-
SecurID OTP	-	-
Authenticate OTP	-	-
Device Biometrics	-	-
SMS OTP	-	-
Voice OTP	-	-
FIDO Security Key	-	-
QR Code	-	-
Emergency Access Code	-	-

GitHub Integration with RSA Authentication Manager

	Supported
-	Not supported
n/t	Not yet tested or documented, but may be possible
n/a	Not applicable

Configuration Summary

This section contains instruction steps that show how to integrate Microsoft Github with RSA Cloud Authentication Service using all supported integration types. This document is not intended to suggest optimum installations or configurations. It is assumed that the reader has both working knowledge of all products involved, and the ability to perform the tasks outlined in this section. Administrators should have access to the product documentation for all products in order to install the required components. All RSA and Microsoft Github components must be installed and working prior to the integration.

Integration Configuration

RSA Cloud Authentication Service

• GitHub - SAML My Page SSO Configuration - RSA Ready Implementation Guide
• GitHub - SAML Relying Party Configuration - RSA Ready Implementation Guide
• GitHub - SCIM Configuration - RSA Ready Implementation Guide

RSA Terminology Changes

The following table describes the differences in the terminologies used in the different versions of RSA products and components. 

Certification Details

RSA Cloud Authentication Service
GitHub

Known Issues

No known issues