GitLab Integration with AuthPoint

Deployment Overview

This document describes how to set up multi-factor authentication (MFA) for GitLab with AuthPoint as an identity provider. GitLab must already be configured and deployed before you set up MFA with AuthPoint.

GitLab Authentication Data Flow with AuthPoint

AuthPoint communicates with various cloud-based services and service providers with the SAML protocol. This diagram shows the data flow of an MFA transaction for GitLab.

Diagram of the data flow for an MFA transaction between GitLab and AuthPoint.

Before You Begin

Before you begin these procedures, make sure that:

Configure GitLab

To start, you must download the metadata file from the Certificate Management page in the AuthPoint management UI. After you have that, you can configure GitLab.

  1. Log in to WatchGuard Cloud.
  2. From the navigation menu, select Configure > AuthPoint. If you have a Service Provider account, you must select an account from Account Manager.
  3. Select Resources.
  4. Click Certificate.

Certificate

  1. Next to AuthPoint certificate you will associate with your resource, click and select Download Metadata. We recommend that you choose the certificate with the latest expiration date. If you do not have a certificate, or if all of your certificates have expired, click Add Certificate and use the newly created certificate.

    The AuthPoint metadata provides your resource, in this case GitLab, with information necessary to identify AuthPoint as a trusted identity provider.

Fingerprint

  1. Next the same certificate, click and select Copy Fingerprint.
    The Copy Fingerprint window appears.
  2. From the Algorithm drop down list, select SHA-1
  3. Click Copy next to the formatted or unformatted fingerprint. We recommend you leave this window open.

Copy Fingerprint

  1. Open a new tab in your web browser and log in to GitLab as an administrator.
  2. Select Groups > Your groups.
  3. Select Settings> SAML SSO.
  4. Copy the Assertion consumer service URL and the Identifier.
  5. Select the Enable SAML authentication for this group slider.
  6. Open the AuthPoint metadata file you downloaded and find the SingleSignOnService Location value.
  7. In the Identity provider single sign on URL text box, type or paste the SingleSignOnService Location value from the AuthPoint metadata file.
  8. In the Certificate fingerprint text box, type or paste the AuthPoint fingerprint you copied earlier.

SAML SSO settings

  1. Click Save changes.

    You must successfully test SAML single sign-on to save your changes. We recommend that you complete the steps in the next section to configure AuthPoint before you save your changes.

Configure AuthPoint

Before AuthPoint can receive authentication requests from GitLab, you must add a SAML resource in AuthPoint. You must also create an authentication policy for the GitLab resource to determine which users can authenticate and log in to GitLab and which authentication methods they can use (Push, QR code, and OTP).

Add a GitLab Resource in AuthPoint

From the AuthPoint management UI:

  1. From the navigation menu, select Resources. Click Add Resource.
    The Add Resource page opens.

  1. From the Type drop-down list, select SAML.
    Additional fields appear.

  1. On the SAML page, in the Name text box, type a name for this resource.
  2. From the Application Type drop-down list, select Gitlab.
  3. In the Service Provider Entity ID text box, type or paste the Assertion consumer service URL value copied from the SAML Single Sign On Settings page in GitLab.
  4. In the Assertion Consumer Service text box, type or paste the Assertion consumer service URL value copied from the SAML Single Sign On Settings page in GitLab.
  5. From the User ID drop-down list, select Email.
  6. From the Signature Method drop-down list, select SHA-256.
  7. From the AuthPoint Certificate drop-down list, select the AuthPoint certificate to associate with your resource. This must be the same certificate that you downloaded the metadata for in the previous section.
  8. Click Save.

Add a Group in AuthPoint

You must have at least one user group in AuthPoint to configure MFA. If you already have a group, you do not have to add another group.

To add a WatchGuard Cloud-hosted group to the WatchGuard Cloud Directory:

  1. Go to Configure > Directories and Domain Services.
  2. Click the WatchGuard Cloud Directory domain name. If you have not yet added the WatchGuard Cloud Directory, click Add Authentication Domain and select the WatchGuard Cloud Directory.
    The New Group page appears.

Screenshot that shows the Directories and Domain Services page.

  1. In the Groups tab, click Add Group.
  2. In the Group Name text box, type a descriptive name for the group.
  3. (Optional) In the Description text box, type a description of the group.

Screen shot of the Add Group page.

  1. Click Save.
    Your group is added to the WatchGuard Cloud Directory and to AuthPoint.

Add an Authentication Policy to AuthPoint

Authentication policies specify which resources users can authenticate to and which authentication methods they can use (Push, QR code, and OTP).

You must have at least one authentication policy in AuthPoint that includes the GitLab resource. If you already have authentication policies, you do not have to create a new authentication policy. You can add this resource to your existing authentication policies.

Users that do not have an authentication policy for a specific resource cannot authenticate to log in to that resource.

To configure an authentication policy:

  1. From the navigation menu, select Authentication Policies.
  2. Click Add Policy.

Screenshot of the Add Policy button on the Authentication Policies page.

  1. Type a name for this policy.
  2. From the Select the Authentication Options drop-down list, select Authentication Options and select which authentication options users can choose from when they authenticate.

    For SAML resources, if you select more than one authentication option, users must select one of the available options when they authenticate. For example, if you select OTP and Push, users can choose to type their OTP or approve a push to authenticate. You cannot require that they do both.

  1. Select which groups this policy applies to. You can select more than one group. To configure this policy to apply to all groups, select All Groups.
  2. Select the resource that you created in the previous section. If you want this policy to apply to additional resources, select each resource this policy applies to. To configure this policy to apply to all resources, select All Resources.

Screenshot of the Add Policy page with the groups and resources selected

  1. (Optional) If you have configured policy objects such as a Network Location, select which policy objects apply to this policy. When you add a policy object to a policy, the policy only applies to user authentications that are the same as the conditions of the policy objects. For example, if you add a Network Location to a policy, the policy only applies to user authentications that come from that Network Location. Users who only have a policy that includes a Network Location do not get access to the resource when they authenticate outside of that Network Location (because they do not have a policy that applies, not because authentication is denied).

    If you configure policy objects, we recommend that you create a second policy for the same groups and resources without the policy objects. The policy with the policy objects should have a higher priority.

Screenshot of the Policy Objects drop-down list.

  1. Click Save.
    Your policy is created and added to the end of the policy list.

    When you create a new policy, we recommend that you review the order of your policies. AuthPoint always adds new policies to the end of the policy list.

Screenshot of the Save button on the Add Policy page.

Add Users to AuthPoint

Before you assign users to a group, you must add the users to AuthPoint. There are two ways to add AuthPoint user accounts:

  • Sync users from an external user database
  • Add WatchGuard Cloud-hosted AuthPoint users

Each user must be a member of a group. You must add at least one group before you can add users to AuthPoint.

To import users from Active Directory, Microsoft Entra ID, or an LDAP database, you must add an external identity in the AuthPoint management UI. External identities connect to user databases to get user account information and validate passwords.

  • To sync users from Active Directory or an LDAP database, you must add an LDAP external identity
  • To sync users from Microsoft Entra ID, you must add a Microsoft Entra ID external identity

When you sync users from an external user database, you can sync any number of users and they are all added to AuthPoint at one time. Users synced from an external user database use the password defined for their user account as their AuthPoint password.

To learn how to sync users, go to Sync Users from Active Directory or LDAP and Sync Users from Azure Active Directory.

You create WatchGuard Cloud-hosted users and groups from the WatchGuard Cloud Directory in WatchGuard Cloud. Directories and Domain Services is where you add shared authentication domains for WatchGuard Cloud devices and services, such as AuthPoint.

Users that you add to the WatchGuard Cloud Directory are automatically added to AuthPoint as well.

You add local AuthPoint users form Directories and Domain Services. You manage the users in AuthPoint on the Users page.

When you add WatchGuard Cloud-hosted AuthPoint users, you choose whether the user is an MFA user or a non-MFA user.

  • MFA users are user accounts that will use AuthPoint multi-factor authentication to authenticate. This is not related to the AuthPoint Multi-Factor Authentication license type.
  • Non-MFA users are users that will only ever authenticate with a password, such as a service account user. Non-MFA users do not consume an AuthPoint user license and cannot authenticate to resources that require MFA. They can only authenticate to protected resources if the non-MFA user account has a password only authentication policy for that resource.

After you add a user, you can edit the user account if you need to change their account type. When you change a user account from MFA to non-MFA, AuthPoint deletes the tokens and password vault (if applicable) that belong to the user. This action cannot be undone.

Unlike users synced from an external user database, WatchGuard Cloud-hosted AuthPoint users define and manage their own AuthPoint password. When you add a WatchGuard Cloud-hosted user account, the user receives an email that prompts them to set their password.

To learn how to add WatchGuard Cloud-hosted AuthPoint user accounts to the WatchGuard Cloud Directory, go to Add Local Users to an Authentication Domain.

The email address or user name of your AuthPoint user account must match the user name or email address you use to log in to GitLab.

Test the Integration

To test AuthPoint MFA with GitLab, you can authenticate with a token on your mobile device. You can choose any method (push, QR code, or one-time password).

In this example, we show the push authentication method (users receive a push notification in the mobile app that they must approve to authenticate).

  1. In a web browser, navigate to the GitLab single sign on URL (shown on the SAML Single Sign On Settings page in GitLab).
  2. Click Sign in with Single Sign-On

sso login

  1. Type your email address or AuthPoint user name. Click Sign In.
  2. If required, in the Password text box, type your password.
  3. For the authentication method, select Push.
  4. Click Send.
  5. Approve the authentication request that is sent to your mobile device.
    You are logged in to GitLab successfully.