GitHub App Integration

    Set up a GitHub app integration so that your users can sign into this app using the same credentials that they use for LastPass.

    Part 1 - Add the SSO app to LastPass

    About this task:
    1. Log in and access the LastPass new Admin Console by doing either of the following:
      • While logged in to LastPass, click the active LastPass icon active LastPass icon in your web browser toolbar, then select Admin Console in the menu.
      • Log in at with your admin email address and master password.
    2. Go to Applications > SSO apps.
    3. Select Add app in the upper-right navigation (or Search the catalog if you're adding your first app).
    4. Search for and select your app from the catalog (or Add an unlisted app if you can't find your app).
    5. Click Continue, and you are taken to the Set up LastPass section of the app configuration.

      Fastpath: LastPass automatically fills out all required information in the Set up app section for you. Some apps allow you to upload settings in an XML file, while others require you to copy and paste the following information:
      Name in LastPass Value
      Entity ID
      SSO Endpoint
      Logout URL
      Certificate fingerprint Provided in the Set up app section of the SSO app. If needed, download the LastPass certificate in PEM, DER, or Download metadata (XML) format.
      Certificate fingerprint (SHA256)
      Certificate (PEM)

    6. For the next steps, open a new web browser window or tab. Go to the app's settings to enable single sign-on, and make sure your app recognizes LastPass as the Identity Provider.

    Part 2 - Configure the app in GitHub

    About this task: For detailed instructions, see GitHub documentation.
    1. Log in to your GitHub admin account.
    2. Click your avatar in the upper right corner and select Your organizations from the drop-down menu.

      Your organizations in GitHub

    3. Select Settings next to your organization.

      Organization settings in GitHub

    4. Select the Security tab in the left navigation menu, then select Authentication security.

      Authentication Security

    5. Under the SAML single sign-on section enable the checkbox to Enable SAML authentication.
    6. Enter the following information:

      Name Description Value
      Sign on URL SSO endpoint value (copied from the LastPass Admin Console)
      Issuer Entity ID value (copied from the LastPass Admin Console)
      Public certificate LastPass certificate file you downloaded in Part 1 Paste the LastPass Certificate that you downloaded in Part 1

      SAML settings in GitHub

    7. Under the Public certificate section, copy your assertion consumer service (ACS) URL and paste it into a text editor.
    What to do next: Before testing and saving the SAML sign-on, finalize the GitHub app configuration in LastPass in Part 3.

    Part 3 - Finalize the GitHub SSO app configuration in LastPass

    1. Return to the LastPass new Admin Console.
    2. Back on the Configure app page in the LastPass Admin Console (from Part 1), select Set up LastPass.
    3. In the ACS field, paste the URL that you copied in Part 2.
    4. Select Advanced Settings and for the Entity ID field, enter<your-organization>.
    5. Optional: Enable Step-up authentication if you want to require users to confirm their identity using the LastPass Authenticator app upon each login to this SSO app.

      Remember: Passwordless login for SSO apps only supports authentication using stored biometrics (face or fingerprint) via push notification in the LastPass Authenticator app.

    6. Select Advanced settings.
    7. For the Entity ID field, paste the Service provider entity URL copied in Part 2.
    8. Optional: If desired, in the Advanced settings section, add any of the following additional customizations:

      Name in LastPass Description/Value
      Nickname The name of the app how it appears in the Admin Console (and Cloud Apps, if your users have a LastPass password management vault)
      Role Custom role that you created to organize users and the permissions assigned to them
      Identity Provider (LastPass) This is the URL of the identity provider, which is LastPass:
      Relay State URL to which the service provider redirects the user after processing the SAML response
      Identifier These settings will depend on the app you're configuring – please refer to the SSO app's documentation, then select one of the following:
      • Email (default)
      • Secondary Email
      • User ID
      • Groups
      • Roles
      • Custom
      SAML signature method SHA256 (uses 256-bit hash)
      Signing and encryption Make your desired selections from the following:
      • Sign assertion
      • Encrypt assertion
      • Sign request
      • Sign response
      Upload partner certificate Select the partner certificate you saved locally (if applicable)
      Custom attributes To add more custom attributes, select Add SAML attribute and choose from the following options:
      • Email
      • Secondary Email
      • User ID
      • Groups
      • Roles
      • Custom (associated with the SSO app)
      Tip: You can define custom attribute statements when creating a new SAML integration, or modifying an existing one. These statements are inserted into the SAML assertions shared with your app.

    9. Click Save & assign users > Users, groups & roles to begin making your selections.
    10. Search for and select your desired users, groups, and/or roles, then click Assign.
    11. Click Save & continue > Finish.

      Result: Setup for your SSO app is complete! The LastPass users you assigned to this SSO app can now use their LastPass account to sign in to this SSO app going forward.

    Part 4 - Finalize the GitHub SSO App configuration in GitHub

    1. Return to GitHub and select Test SAML configuration.
    2. After successfully testing the SAML configuration, select Save.

      Testing SAML configuration