Multi-Factor Authentication (MFA) is an extra layer of security used when logging into websites or apps. Individuals are authenticated through more than one required security and validation procedure that only you know or have access to.
Security Assertion Markup Language (SAML) is a protocol for authenticating to web applications. SAML allows federated apps and organizations to communicate and trust one another’s users. Acceptto, as a SAML provider, improves the user login experience for GitHub users with convenient MFA. This manual illustrates how to configure both GitHub and Acceptto using SAML metadata exchange.
- An Acceptto Appliance connected to your user directory (for example Microsoft ‘Active DirectoryTM’).
- The user population that is going to be authenticated via SAML must be enrolled in the It’sMe Application.
- A user with administrative privileges for the Acceptto Appliance.
- A user with administrative privileges for the GitHub server or instance.
Acceptto SAML Configuration as Identity Provider (IdP)
- Login to the Acceptto appliance admin panel with an administrative account and go to Applications.
- Create a new application by selecting the Create New Application.
- In the Add Application dialog, enter the following values (Advanced Options button allows additional optional configuration):
- App Name - The application name displayed in the admin panel and application portal. For example, GitHub
- Issuer or Entity ID – The Issuer/EntityID of your StoreFront instance you got from the previous section. For example, github.example.com
- Sign in URL - The link used by your users to access GitHub. For example, github.example.com.
- >Metadata URL - The URL containing metadata about your GitHub server or instance you. By default, it should be similar to github.example.com/saml/metadata
- Login to GitHub with an administrative user and access the site’s admin menu by selecting the rocket ship icon in the right corner of the page.
- In the site admin menu, select Management console, then select SAML under Authentication.
- In the URL configuration enter the information you got earlier from Acceptto SAML Appliance.
- Upload the X.509 certificate file you got from Acceptto SAML Appliance earlier.
- Click “Save settings.”
Test your setup
- Open a new browser session and navigate to your GitHub URL.
- Click “Sign in with SAML.”
- You will be redirected to the Acceptto SAML page.
- After successful authentication, you’ll see the Acceptto MFA options and need to select your desired method and pass the verification stage on It’sMe mobile app.
- You are now authenticated with Acceptto SSO-MFA and will be redirected to your GitHub.
- If you receive a message similar to NameID or username does not exist, please verify the username configuration in the Acceptto Appliance and the GitHub management console are identical. They must match.
- Once your testing is complete, and your user base is all migrated to SAML. You can prevent local login by de-selecting the control, “Allow creation of accounts with built-in authentication (for users not in SAML).”
If you require assistance, please email us at firstname.lastname@example.org
Want to learn more about our MFA solutions? Contact our Professional Services for a Demo today.
All product names, trademarks, and registered trademarks are the property of their respective owners.
All company, product, and service names used in this document are for identification purposes only. The use of these names, trademarks, and brands do not constitute an endorsement by the Acceptto Corporation.
GitHub is either registered trademarks or trademarks of GitHub, Inc. and/or one or more of its subsidiaries in the United States and/or other countries.
Microsoft and 'Active Directory' are either registered trademarks or trademarks of Microsoft and/or one or more of its subsidiaries in the United States and/or other countries.