Perforce Integration with AuthPoint

Deployment Overview

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

Perforce can be configured to support MFA in several modes. For this integration, we set up SAML with AuthPoint.

This integration was tested with Helix Core server (P4D) 2019.2 v1918134 on CentOS 7.

Perforce 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 Perforce.

Diagram that shows the data flow of an MFA transaction for a SAML resource with the push authentication method.

Before You Begin

Before you begin these procedures, make sure that:

Configure Perforce

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

  1. Log in to WatchGuard Cloud.
  2. From the navigation menu, select Configure > AuthPoint. If you have a Service Provider account, you must first pivot to your Subscriber view.
  3. Select Resources.
  4. Click 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.

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

  1. On your Perforce server, run this command to install the Git tool for Perforce authentication extensions:
    yum install git
  2. Create a folder and navigate to it.
  3. Run this command to get Helix-Authentication-Service (HAS):
    git clone https://github.com/perforce/helix-authentication-service.git
  4. Run this command to get Helix-Authentication-Extension (HAE):
    git clone https://github.com/perforce/helix-authentication-extension.git
  5. You must replace the certificates in folders because they all expired. You must also assign new certificates by your CA (if you use private CA) or a trusted public CA (if you do not have private CA). In our example, we have a private CA on a Linux server, so we use self-signed certificates to replace the certificates in our folders.
  6. Copy your ca.crt and ca.key file to a new folder where you will generate all of the certificates. Navigate to the folder.
  7. Run this command to get the HAE client.key and client.csr files:
    openssl req -newkey rsa:4096 -keyout client.key -out client.csr -nodes -days 365 -subj "/CN=LoginExtension"
  8. Run this command to generate client.crt:
    openssl x509 -req -in client.csr -CA ca.crt -CAkey ca.key -out client.crt -set_serial 01 -days 365
  9. Run this command to get HAS server.key and server.csr:
    openssl req -newkey rsa:4096 -keyout server.key -out server.csr -nodes -days 365 -subj "/CN=AuthService"
  10. Run this command to generate server.crt:
    openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key -out server.crt -set_serial 01 -days 365
  11. Delete the client.csr and server.csr files.
  12. Run this command to replace the expired certificates:
    cp ca.* <your prepared folder path>/helix-authentication-service/certs/
  13. Run this command to replace the expired server certificates:
    cp server.* <your prepared folder path>/helix-authentication-service/certs/
  14. Run this command to replace the expired CA certificates:
    cp ca.crt <your prepared folder path>/helix-authentication-extension/loginhook
  15. Run this command to replace the expired client certificates:
    cp client.* <your prepared folder path>/helix-authentication-extension/loginhook
  16. Navigate to the HAS folder and run this command to install the authentication service:
    sh install.sh
  17. To edit the ecosystem.config.js file, run sudo vi ecosystem.config.js.
    1. Delete the OIDC_CLIENT_ID, OIDC_CLIENT_SECRET_FILE and OIDC_CLIENT_SECRET_FILE values. Leave the quotation marks and comma.
    2. Replace the SAML_IDP_SSO_URL value with the SingleSignOnService Location value from the AuthPoint metadata. This value should be 'https://sp.authpoint.usa.cloud.watchguard.com/saml/<WatchGuard Cloud account ID>/sso/spinit'.
    3. Replace the SAML_IDP_SLO_URL value with the SingleLogoutService Location value from the AuthPoint metadata file. This value should be 'https://sp.authpoint.usa.cloud.watchguard.com/saml/<WatchGuard Cloud account ID>/slo/spinit'.
    4. For the SAML_SP_ISSUER value, type '<your issuer name here>'. When you configure a SAML resource in AuthPoint, this value is the entityID.
    5. Replace the SVC_BASE_URI value with your AuthService URL. This value should be 'https://<perforce server instance name>:3000'. Add a comma at the end of this line.
    6. Comment out the DEFAULT_PROTOCOL line. Delete the comma at the end of this line.
    7. Save and quit.
  18. Run this command to reload the file and put your changes into effect:
    pm2 startOrReload ecosystem.config.js
  19. Go to the HAE folder and run this commmand to get a zip file named loginhook.p4-extension:
    p4 extension --package loginhook
  20. Run this command:
    p4 extension --install loginhook.p4-extension -y
  21. You must configure a global configuration for your extension. Run p4 extension --configure Auth::loginhook.
    1. Change the ExtP4USER value to super.
    2. Set the Auth-Protocol value to be saml. This value does not need quotes.
    3. Set the Service-URL value to be https://<your AuthService URL>/.
    4. Save and quit.
  22. You must configure a single instance for your environment. Run p4 extension --configure Auth::loginhook --name <your instance name>.
    1. In the ExtConfig section, set enbale-logging to be true in case you need to troubleshoot an issue.
    2. Set the name-identifier value to be nameID.
    3. Delete the description for non-sso-groups and add your own group, which bypasses the SSO authentication.
    4. Set the non-sso-users value to be super. You can also add other users here.
    5. Set the user-identifier value to be email.
    6. Save and quit.
  23. Run this command to restart the service:
    p4 admin restart
  24. If you use private CA certificate, you must trust your CA certificate on every client that will run P4V to connect to P4 server.

Configure AuthPoint

Before AuthPoint can receive authentication requests from Perforce, you must add a SAML resource in AuthPoint. You must also assign an access policy for the Perforce resource to the user group(s) that must authenticate to log in.

Add a SAML Resource in AuthPoint

From the AuthPoint management UI:

  1. From the navigation menu, select Resources.
  2. From the Choose a Resource Type drop-down list, select SAML. Click Add Resource.

  1. Type a name for this resource. In our example, we type Perforce.
  2. From the Application Type drop-down list, select Other.
  3. In the Service Provider Entity ID text box, type your Perforce issuer name. This should be the same value from the previous section.
  4. In the Assertion Consumer Service text box, type https://<your Perforce AuthService URL>/saml/sso.
  5. From the AuthPoint Certificate drop-down list, select the certificate to associate with your resource. This must be the same certificate that you downloaded the metadata for in the previous section.
  6. Click Save.

Add an Access Policy to AuthPoint

You must have at least one user group in AuthPoint for authentication with Perforce, and you must assign an access policy for the Perforce resource to that group. If you already have a group, you do not have to add another group.

In the AuthPoint management UI:

  1. From the navigation menu, select Groups.
  2. To add a new group, click Add Group. If you already have a group that you want to use, select the group to edit it.

  1. In the Name text box, type a descriptive name for the group.
  2. (Optional) In the Description text box, type a description of the group.

  1. In the Access Policy section, click Add Policy.

  1. In the Add Policy dialog box, from the Resource drop-down list, select the resource you want to add an access policy for.
  2. (Optional) To require that users type their password before they authenticate for this resource, enable the Require Password Authentication toggle.
  3. Select the authentication options that users in this group can select 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. Click Add.

  1. (Optional) Add one or more safe locations to your group. For more information about safe locations and detailed instructions to add them, see About Safe Locations.
  2. Click Save.

Before you assign users to a group, you must add the users to AuthPoint. You can manually add user accounts or import user accounts from an external user database. For more information on how to add user accounts, see Add User Accounts.

Test the Integration

To test AuthPoint MFA with Perforce, you can authenticate with a mobile token on your mobile device. For SAML resources, 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. Open your P4V client.
  2. Type your server address and user name. Click OK.
    A new window appears and redirects you to AuthPoint authentication page.
  3. Type your user name and password.
  4. For the authentication method, select Push.
  5. Click Send.
  6. Approve the authentication request that is sent to your mobile device.
    You are logged in to Perforce.