Skeddly Integration with AuthPoint
Deployment Overview
This document describes how to set up multi-factor authentication (MFA) for Skeddly with AuthPoint as an identity provider.
Skeddly can be configured to support MFA in several modes. For this integration, we set up SAML with AuthPoint.
Skeddly only supports identity provider initiated single-sign on (SSO). To configure AuthPoint MFA for Skeddly, you must configure an IdP portal resource in AuthPoint. End users must use the IdP portal to log in to Skeddly.
Skeddly 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 Skeddly.
Before You Begin
Before you begin these procedures, make sure that:
- You have registered a Skeddly account
- A token is assigned to a user in AuthPoint
- You have an AuthPoint identity provider (IdP) certificate (go to Certificate Management)
- You have an IdP portal resource in AuthPoint
Configure Skeddly
To start, you must download the metadata file from the Resources page in the AuthPoint management UI. After you have that, you can configure Skeddly.
- Log in to WatchGuard Cloud.
- From the navigation menu, select Configure > AuthPoint. If you have a Service Provider account, you must select an account from Account Manager.
- Select Resources.
- Click Certificate.
- 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 Skeddly, with information necessary to identify AuthPoint as a trusted identity provider.
- Go to https://app.skeddly.com and log in to Skeddly.
- Navigate to Users & Identity > Identity Providers.
- Click Create Identity Provider.
The Create Identity Provider page opens. - In the Name text box, type a name for your identity provider. In our example, we name the identity provider AuthPoint.
- From the Provider Type drop-down list, select SAML.
- Click Select Your Metadata File and upload the AuthPoint metadata file that you downloaded in Step5.
- Click Create Identity Provider.
- After Skeddly saves your identity provider, you receive a Provider SRN. Copy or note this value. You need it to configure AuthPoint in the next section.
- Click the skeddly-metadata.xml link. A new tab opens with Skeddly metadata. Leave this tab open. You need this information to configure AuthPoint in the next section.
Configure AuthPoint
Before AuthPoint can receive authentication requests from Skeddly, you must specify Skeddly as a SAML resource in AuthPoint and you must add an IdP portal resource.
You must also create an authentication policy for the Skeddly resource and the IdP portal resource to determine which users can authenticate and log in to these resources and which authentication methods they can use (Push, QR code, and OTP).
Add a SAML Resource in AuthPoint
From the AuthPoint management UI:
- From the navigation menu, select Resources.
Click Add Resource.
The Add Resource page opens.
- From the Type drop-down list, select SAML.
Additional fields appear.
- In the Name text box, type a name for this resource. In our example, we name the resource Skeddly.
- From the Application Type drop-down list, select Others.
- In the Service Provider Entity ID text box, type https://app.skeddly.com/. This value comes from the Skeddly metadata in the previous section.
- In the Assertion Consumer Service text box, type https://app.skeddly.com/sso/saml/. This value comes from the Skeddly metadata in the previous section.
- From the User ID drop-down list, select which user ID attribute to send to the service provider. The service provider compares the user ID attribute for the AuthPoint user with the user name in your application. These values must match. You can choose to send the user's email address or user name.
- From the Signature Method drop-down list, select SHA-256.
- 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 Configure Skeddly section.
- You must add a custom attribute to your SAML resource for Skeddly. To add a custom attribute:
- Click Add Attribute.
The Add Attribute window opens. - In the Attribute Name text box, type https://skeddly.com/SAML/Attributes/Roles. This value is case-sensitive.
- From the Get Value From drop-down list, select Fixed value.
The Fixed Value text box appears. - In the Fixed Value text box, type a comma separated list with these values:
- The SRN of your Skeddly identity provider from Step 13 in the previous section. You can only enter one Skiddly identity provider SRN. You can copy this value from the Identity Provider Information page in your Skeddly account.
- One or more SRNs of the Skiddly managed policies to apply to the user when they sign-in. You can find these SRNs on the Managed Policies pages in your Skeddly account.
In our example, the fixed value that we specify is srn:skeddly:idp::3473c399:AuthPoint, srn:skeddly:policy:::standard.
- Click Save.
The Add Attribute window closes.
- Click Add Attribute.
- Click Save to save your SAML resource.
Add an IdP Portal Resource
You must have an IdP portal resource to use MFA for Skeddly. If you already have an IdP portal resource, you must add the IdP portal resource to any authentication policy that includes the Skeddly resource.
If you already have an IdP portal resource, skip this section and continue to Add a Group in AuthPoint.
To add an IdP portal resource, from the Resources page in the AuthPoint management UI:
- From the Choose a resource type drop-down list, select IDP Portal. Click Add Resource.
- In the Name text box, type a descriptive name for the resource.
- In the Account Alias text box, type a unique value to append to the URL for your IdP portal. The URL for the IdP portal is always https://authpoint.watchguard.com/<account_alias>. In our example, the account alias is washington, so the URL for the IdP portal is https://authpoint.watchguard.com/washington.
- To allow users to activate hardware and software tokens from the IdP portal, enable the Allow users to manage their tokens from the IdP portal toggle.
- Click Save.
To learn more about the IdP portal, see Configure the IdP Portal.
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:
- Go to Configure > Directories and Domain Services.
- 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.
- In the Groups tab, click Add Group.
- In the Group Name text box, type a descriptive name for the group.
- (Optional) In the Description text box, type a description of the group.
- 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 Skeddly 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:
- From the navigation menu, select Authentication Policies.
- Click Add Policy.
- Type a name for this policy.
- 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.
- 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.
- 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.
-
(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.
- 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.
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.
Test the Integration
To test AuthPoint MFA with Skeddly, you can authenticate with a mobile token on your mobile device. You can choose any method (one-time password, QR code, or push).
In this example, we show the push authentication method (users receive a push notification in the AuthPoint mobile app that they must approve to authenticate).
- In a web browser, go to the IdP portal. You can see the URL for the IdP portal when you edit your IdP portal resource in the AuthPoint management UI.
- Type your email address or AuthPoint user name. Click Next.
- If required, in the Password text box, type your password.
- For the authentication method, select Send Push.
- Approve the authentication request that is sent to your mobile device.
You are logged in to AuthPoint Idp portal successfully. - In the IdP portal, select Skeddly.
You are logged in to Skeddly.