FreshService Integration with AuthPoint

Deployment Overview

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

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

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 FreshService

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

  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 select Download Metadata and Download Certificate. We recommend that you choose the certificate with the latest expiration date.

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

  1. Open a new tab and log in to FreshService as an administrator.

Screenshot of the Admin page.

  1. Click Admin.

Screenshot of the Admin page.

  1. From the General Settings section, click Helpdesk Security.

Screenshot of the Security page.

  1. Click Go to Freshworks 360 Security.
  2. Under Default Policy enable Single sign-on.
  3. From the Login Method drop-down list, select SAML SSO.

Screenshot of the SAML config

  1. Copy the Assertion Consumer Service(ACS) URL and Service Provider(SP) Entity ID values.
  2. Open the AuthPoint metadata file you downloaded and find the entityID SingleSignOnService Location and SingleLogoutService Location values.
  3. In the Entity ID provided by the IdP text box, type or paste the entityID value from the AuthPoint metadata file.
  4. In the SAML SSO URL text box, type or paste the SingleSignOnService Location value from the AuthPoint metadata file.
  5. From the Signing Options drop-down list, select Only Signed Response.
  6. In the Logout URL text box, type or paste the SingleLogoutService Location value from the AuthPoint metadata file.
  7. In the Security certificate text box, type or paste the AuthPoint certificate value from the AuthPoint certificate file.

Screenshot of the SAML config

  1. Click Save.
    You are prompted for confirmation before you save the configuration.

Configure AuthPoint

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

Add a FreshService 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. On the SAML page, in the Name text box, type a name for this resource.
  2. From the Application Type drop-down list, select FreshService.
  3. In the Service Provider Entity ID text box, type the Service Provider(SP) Entity ID value copied from FreshService SAML configure page.
  4. In the Assertion Consumer Service text box, type the Assertion Consumer Service(ACS) URLvalue copied from FreshService SAML configure page.
  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 an Access Policy to AuthPoint

You must have at least one user group in AuthPoint for authentication with FreshService, and you must assign an access policy for the FreshService 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.

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 local 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, Azure Active Directory, 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 Azure Active Directory, you must add an Azure AD 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, see Sync Users from Active Directory or LDAP and Sync Users from Azure Active Directory.

You can create local AuthPoint users on the Users page in the AuthPoint management UI. Because you can create only one user at a time, you most commonly do this when you want to create test users or to add only a small number of users.

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

To learn how to add local AuthPoint user accounts, see Add Local AuthPoint Users.

Test the Integration

To test the integration of AuthPoint and FreshService, you can authenticate with a mobile 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, go to your FreshService URL (https://Domain name.freshservice.com).

Screenshot of the sign in page.

  1. Click Sign in.

Screenshot of the sign in page.

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