1Password XAM Configuration | Twingate

1Password XAM Configuration

Business & Enterprise only

Note that our 1Password Extended Access Management (XAM) Device Trust integration is limited to the Business and Enterprise product plans. See our pricing page for more information.

Background

Twingate integrates with 1Password Device Trust by leveraging their device verification to restrict access to only secure devices. Admins can add 1Password Device Trust as a verification requirement to macOS, Windows, and Linux Trusted Profiles. In turn, devices will be required to be verified by 1Password Device Trust to sign in to Twingate or access certain Resources.

How it works

Twingate integrates with 1Password Device Trust by matching the device serial numbers returned by the Twingate Client to those managed by 1Password. Devices are considered 1Password-verified if they meet the following requirements:

Configuring the 1Password Device Trust integration in Twingate

Generate a 1Password Device Trust API key

To set up the integration, you’ll need an API key from 1Password Device Trust:

Configure the integration on the Twingate Admin Console

Incorporate 1Password Device Trust into Security Policies

After the 1Password Device Trust integration has been set up, it can be configured into Device Security Trusted Profiles.

For macOS, Windows, and Linux, create a Trusted Profile and require 1Password Device Trust as a Trust Method. Only devices verified by 1Password Device Trust will satisfy the requirements of this Trusted Profile. This Trusted Profile can now be incorporated into Security Policies.

Troubleshooting

After the 1Password Device Trust integration is set up, the Device Integrations page will show the status as “Waiting to sync”. During this time, devices may be missing the correct 1Password Device Trust verification state. After a few minutes, the Device Integrations page will show the most recent sync time and devices will correctly show their state on their device details page.

A device can be listed as 1Password not verified for the following reasons:

In the case of an error, the 1Password Device Trust integration will show the time of the last successful sync. Twingate will attempt to connect for 28 hours. When we are able to reach the 1Password API, the errors will be resolved automatically. If Twingate is unable to connect within 28 hours, the integration will stop attempting to connect. Admins will be notified via email that the integration needs attention. For these errors, we recommend reconfiguring the integration and inputting new API client information.

Last updated 6 months ago