VMware Workspace One Access Integration with AuthPoint
Deployment Overview
This document describes how to set up multi-factor authentication (MFA) for VMware Workspace One Access with AuthPoint as an identity provider. VMware must already be configured and deployed before you set up MFA with AuthPoint.
VMware Workspace One Access 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 VMware Workspace One Access.
Before You Begin
Before you begin these procedures, make sure that:
- Users can log in to VMware Workspace One Access.
- You have a VMware Workspace One Access user account and an AuthPoint user account. Both accounts must use the same email address.
- You have an AuthPoint identity provider (IdP) certificate (go to Certificate Management).
Additional charges might apply to use VMware Workspace One Access.
Configure VMware Workspace One Access
Create a New SAML IDP
Before you can configure VMware Workspace One Access, download the metadata file from the Certificate Management page in the AuthPoint management UI.
- 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 the AuthPoint certificate that you want to associate with your resource, click and select Download Metadata or Copy Metadata URL.
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 new certificate.The AuthPoint metadata URL provides your resource, in this case VMware Workspace One Access, with information necessary to identify AuthPoint as a trusted identity provider.
- Log in to VMware Workspace One Access as an administrator.
- Select Integrations > Identity Providers.
- Click Add Identity Provider and select Create SAML IDP.
- In the Identity Provider Name text box, type a name for the new identity provider. In this example, we type WatchGuard AuthPoint.
- From the Binding protocol drop-down list, select HTTP Redirect or HTTP Post.
This field appears after you enter the metadata URL or metadata file in the Identity Provider Metadata(URL or XML) text box, and click Process IDP Metadata. - In the Identity Provider Metadata (URL or XML) text box, type or paste the metadata URL copied from AuthPoint or the metadata file downloaded from AuthPoint in the previous section.
- Click Process IdP Metadata.
- From Identity User Using, select NameID Element.
- From the Name ID format mapping from SAML Response section, click twice to add Name ID values for userName and emails.
- From the Name ID Format drop-down list, select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified, then from the Name ID Value drop-down list, select userName.
- From the Name ID Format drop-down list, select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress, then from the Name ID Value drop-down list, select emails.
- From the Name ID Policy in SAML Request drop-down list, select the same value that you added for Name ID Format in the previous step. In this example, we select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.
- Keep the Send Subject in SAML Request(when available) check box cleared.
- From the Network section, select the ALL RANGES check box.
- In the Authentication Methods text box, type a name for the AuthPoint authentication method. In this example, we type AuthPoint Auth Method.
- From the SAML Context drop-down list, select urn:oasis:names:tc:SAML:2.0:ac:classes:unspecified.
- From the Single Sign-Out Configuration section, select the Enable check box.
- Open the AuthPoint metadata file you downloaded in the previous section and copy the SingleLogOutService Location value.
- In the IdP Sign-out URL text box, type or paste the SingleLogOutService Location value from the AuthPoint metadata.
- From the SAML Signing Certificate section, select Service Provider(SP) Metadata and save. You use this metadata to configure AuthPoint.
- Leave the other settings as the default values.
- Click Add.
Update the Default Access Policy
- Select Resource > Policies.
- Select default_access_policy_set.
- Click Edit Default Policy.
The Definition page opens. Leave the default values as is. - From the Configuration page, click Next.
- Click Add Policy Rule.
The Add Policy Rule page opens. - From the If a user's network range is drop-down list, select All Ranges.
- From the And the user accessing content from drop-down list, select Web Browser.
- Leave the And user belongs to group(s) text box blank.
- Disable the And user is registering FIDO2 authenticator toggle.
- From the Then perform this action drop-down list, select Authenticate using.
- From the Then the user may authenticate using drop-down list, select AuthPoint Auth Method.
The AuthPoint auth method is created in the authentication method section. - From the If the preceding method fails or is not applicable, then drop-down list, select Password (Local Directory).
- Leave the other settings as the default values.
- Click Save.
- Drag the new AuthPoint Auth Method rule to the first row.
- From the Summary page, click Next.
- Click Save.
Configure AuthPoint
Before AuthPoint can receive authentication requests from VMware Workspace One Access, you must add a SAML resource in AuthPoint. You must also create an authentication policy for the VMware Workspace One Access resource to determine which users can authenticate and log in to VMware Workspace One Access 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.
- From the SAML page, in the Name text box, type a name for this resource.
- From the Application Type(Integration Guide) drop-down list, select VMware Workspace One Access.
- Open the service provider metadata file you saved and copy the entityID, AssertionConsumerService Location, and SingleLogoutService Location values.
- In the Service Provider Entity ID text box, paste the entityID value from the Service Provider metadata file.
- In the Assertion Consumer Service text box, paste the AssertionConsumerService Location value from the Service Provider metadata file.
- From the User ID sent on redirection to service provider drop-down list, select one of the values. In this example, we select Email.
- In the Logout URL text box, type or paste the SingleLogoutService Location value from the Service Provider metadata file.
- 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 previous section.
- 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:
- 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 VMware Workspace One Access 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 VMware Workspace One Access, you can authenticate with a mobile token on your mobile device. You can choose any method (Push, QR code, or OTP).
In this example, we show the push authentication method. Users receive a push notification in the mobile app that they must approve to authenticate.
- In a web browser, go to your VMware Workspace One Access URL.
- 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.
- Click Send.
- Approve the authentication request that you received on your mobile device.
You are logged in to the catalog portal of Workspace One Access.