How to secure 1Password with XFA
Add a device check to 1Password Unlock with SSO, so only devices that pass your XFA policy can unlock 1Password with Google or another OpenID Connect identity provider.
How it works
When someone unlocks 1Password with single sign-on, 1Password sends them to XFA. XFA checks their device against your policy, then sends them to your identity provider to sign in. After the sign-in, the person goes back to 1Password, which unlocks. 1Password receives the same sign-in result from your identity provider that it would get without XFA. XFA reads only the person's email address from that result, to know whose device it checked.
Note: This article assumes that you have an account set up with XFA for your organization and you are an admin for that organization. If you do not have an account, you can create one at https://dashboard.xfa.tech/signup.
Before you start
- A 1Password Business account, and an owner or administrator role in it
- Admin access to your identity provider
- An admin role in XFA
- Device approval for multi-factor authentication turned off in XFA (Require device approval for multi-factor authentication, under Connections > Settings). If your organization requires it, you can't use XFA with 1Password yet: XFA refuses the sign-in.
Your identity provider must:
- put the person's email address in the ID token;
- support PKCE (S256), if you use a Public Client (one without a client secret);
- have one fixed issuer address: the address of your identity provider that you give 1Password as Issuer, the same for every sign-in in your organization (for Microsoft Entra ID, use your tenant's own issuer, not the
commonone).
Google meets all of these. Any other provider that meets them can be used too.
1Password's own rules for Unlock with SSO apply:
- Members of the Owners group never unlock with SSO. They unlock with their account password and Secret Key.
- 1Password accepts only one identity provider for Unlock with SSO.
- 1Password saves a configuration only after a successful Test Connection.
Where each value goes
- XFA redirect URI: from XFA to your identity provider
- Authorization Endpoint and Token Endpoint: XFA's, from XFA to 1Password
- Issuer and User Info Endpoint: from your identity provider to 1Password
- Client ID (and client secret): from your identity provider to 1Password
- Discovery URL: from your identity provider to XFA (XFA's step 1, Other only)
Create the 1Password application in XFA
- In the XFA Dashboard, go to Integrations and click Set up on the 1Password card, then Set up in the Sign-in checks section. XFA opens Secure 1Password with XFA.
- In the Basics card, enter a Name. Under Policy, pick the XFA policy with the device checks you want at unlock.
- In XFA's step 1, Tell XFA about your 1Password account, enter Your 1Password sign-in address: the address you open 1Password at, for example
team-acme.1password.com. XFA fills in 1Password's own two redirect URIs, one for the browser and one for the 1Password apps. You don't need to do anything with them. The value you copy later is the XFA redirect URI, from step 2. - Under Identity provider, choose your provider. This choice is in XFA only. In 1Password you always choose Other, then Manual.
- Google: XFA fills in Google's details.
- Other, for every other provider: paste Your identity provider's discovery URL (it ends in /.well-known/openid-configuration) and click Fill in.
- Click Save and continue later. This saves step 1.
- XFA's step 2 shows the XFA redirect URI under For your identity provider. XFA's step 3, under For 1Password, shows XFA's Token Endpoint and Authorization Endpoint.
Set up your identity provider
You need an OAuth client (some providers call it an application or app integration) for 1Password in your identity provider. If your team already unlocks 1Password with SSO, you can keep using that client. If not, create it with 1Password's guide for your provider. Where that guide sets up 1Password, follow Configure Unlock with SSO in 1Password instead.
For every provider, the main change is the XFA redirect URI, as an extra allowed redirect URI. Don't remove 1Password's redirect URIs that are already there. Every provider must also put the person's email address in the ID token (Before you start). When you are done, copy the Client ID, and the client secret if there is one: they go into 1Password, not XFA. Then click Mark as done on XFA's step 2.
1Password's guide: Configure Unlock 1Password with Google. The client is of type Web application.
- In the Google Cloud console, open APIs & Services > Clients and select the client.
- Under Authorized redirect URIs, click Add URI, paste the XFA redirect URI and click Save.
- On the OAuth consent screen, open Branding. Under Authorized domains, add
xfa.technext to1password.comand click Save. - Copy the Client ID and the Client secret. Google always gives a client secret.
Google says changes can take 5 minutes to a few hours.
In 1Password: Issuer https://accounts.google.com, User Info Endpoint https://openidconnect.googleapis.com/v1/userinfo, Client Type Private Client with the client secret.
Microsoft Entra ID
1Password's guide: Configure Unlock 1Password with Microsoft Entra ID.
- In the app registration for 1Password, open Authentication. Under the Web platform, add the XFA redirect URI and click Save.
- Under Token configuration, click Add optional claim, choose ID and select email, so the ID token carries the email address.
- Copy the Application (client) ID and the client secret value.
The discovery URL is the OpenID Connect metadata document under Overview > Endpoints. It contains your tenant ID: https://login.microsoftonline.com/<your-tenant-id>/v2.0/.well-known/openid-configuration.
In 1Password: Issuer https://login.microsoftonline.com/<your-tenant-id>/v2.0, User Info Endpoint https://graph.microsoft.com/oidc/userinfo, Client Type Private Client with the client secret. Choose Public Client only if you added the XFA redirect URI under the Mobile and desktop applications platform instead of Web.
Okta
1Password's guide: Configure Unlock 1Password with Okta.
-
In the Okta app for 1Password, add the XFA redirect URI under Sign-in redirect URIs and click Save.
The 1Password app from the Okta catalog may not let you add a redirect URI. Then create your own app instead: Applications > Create App Integration > OIDC - OpenID Connect > Web Application. Add the XFA redirect URI under Sign-in redirect URIs.
-
Copy the Client ID, and the client secret if there is one.
The discovery URL is https://<your-okta-domain>/.well-known/openid-configuration.
In 1Password: open the discovery URL in your browser. Issuer is its issuer value and User Info Endpoint its userinfo_endpoint value. Client Type: Private Client with the client secret of a Web Application. Choose Public Client only with a Native Application or Single-Page Application that uses client authentication None and requires PKCE.
Auth0
1Password's guide: Configure Unlock 1Password with Auth0.
- In the Auth0 application for 1Password, add the XFA redirect URI to Allowed Callback URLs. Separate it from the URLs already there with a comma. Click Save Changes.
- Copy the Client ID, and the Client Secret if the application has one.
The discovery URL is https://<your-domain>.auth0.com/.well-known/openid-configuration.
In 1Password: open the discovery URL in your browser. Issuer is its issuer value and User Info Endpoint its userinfo_endpoint value. Client Type: Private Client if the application has a client secret, otherwise Public Client.
JumpCloud
1Password's guide: Configure Unlock 1Password with JumpCloud.
- In the JumpCloud OIDC app for 1Password, on the SSO tab, add the XFA redirect URI to Redirect URIs and save.
- Copy the Client ID, and the client secret if the app has one.
The discovery URL is https://oauth.id.jumpcloud.com/.well-known/openid-configuration, or https://oauth.id.eu.jumpcloud.com/.well-known/openid-configuration for an EU account.
In 1Password: open the discovery URL in your browser. Issuer is its issuer value and User Info Endpoint its userinfo_endpoint value. Client Type: Private Client if the app has a client secret, otherwise Public Client.
Other OpenID Connect providers
1Password's guide: Configure Unlock 1Password with other identity providers. Use this section for Duo, OneLogin, Ping Identity and any other OpenID Connect provider.
- In your provider's OpenID Connect application for 1Password, add the XFA redirect URI to the allowed redirect URIs.
- Check that the provider puts the email address in the ID token. Some providers need a setting or a claim mapping for this.
- Copy the Client ID, and the client secret if the application has one.
The discovery URL is in your provider's documentation.
In 1Password: open the discovery URL in your browser. Issuer is its issuer value and User Info Endpoint its userinfo_endpoint value. Client Type: Private Client if the application has a client secret, otherwise Public Client.
Configure Unlock with SSO in 1Password
- Sign in to your 1Password account on 1Password.com and select Policies in the sidebar.
- Under Single sign-on, select Manage policies.
- Choose Other, even if you use Google, then Manual, so you can enter each value yourself. 1Password must talk to XFA first. 1Password's Google option would skip XFA.
- Fill in the fields:
- Client ID: from your identity provider
- Issuer: your identity provider's
- Token Endpoint: XFA's
- Authorization Endpoint: XFA's
- User Info Endpoint: your identity provider's
- Client Type: follow your provider's section. 1Password labels Public Client as recommended; ignore that label. Choose Private Client if your provider gave you a client secret (Google always does), and paste it into Client secret (value). Choose Public Client only if there is no secret.
- Select Next. 1Password shows its redirect URIs. You don't have to copy these. XFA filled them in from your sign-in address.
- Back in XFA, click Mark as done on XFA's step 3.
- In 1Password, select Next, then Test Connection. 1Password opens XFA, which checks the device you are on and sends you to your identity provider to sign in. If your device fails a check, XFA shows what to fix. Fix it and run Test Connection again. Test Connection saves nothing, so nobody else is affected yet.
- When the test succeeds, select Save. Saving replaces your current SSO setup: from then on, everyone who unlocks 1Password with SSO goes through XFA's device check.
- Choose who unlocks with SSO under People unlocking 1Password with an identity provider. Start with Only groups you select and a small test group, then widen it once unlock works for them. When people switch to SSO, 1Password asks them once for their account password and Secret Key.
- Back in XFA, click Mark as done on XFA's step 4, Test the connection. Then click Finish setup.
What people see
XFA checks the device each time 1Password asks the person to sign in with SSO, in the browser and in the 1Password apps:
- In the browser, 1Password sends the person to XFA, then to the identity provider, and back to 1Password.
- In the 1Password desktop app, the browser opens for the device check and the sign-in. When it is done, the browser asks to open 1Password and the app unlocks.
If the device does not pass the policy, XFA shows which check fails and how to fix it. If your policy blocks a failing check, the unlock stops. If it only warns, the person can continue. You see whether a check blocks or warns in the policy, under Policies in XFA.
XFA does not check the device when:
- the person unlocks with biometrics (Touch ID, Windows Hello, face unlock), because that does not go through SSO;
- the person is in 1Password's Owners group;
- the person is not in a group that unlocks with SSO.
Test the connection
Any admin can run Test Connection, owners included: it tests the connection, not their own unlock. To test unlocking itself, use a member who is not an owner: owners never use SSO, so their unlock doesn't go through XFA. Add that member to the test group. Lock 1Password and unlock it with SSO in the browser and in the desktop app. They should pass through XFA's device check and your identity provider before 1Password unlocks.
Troubleshooting
The identity provider rejects the redirect URI
Google shows redirect_uri_mismatch when the XFA redirect URI is not in the client's Authorized redirect URIs; other providers show a similar error. Copy it again from XFA with the Copy button, so it matches exactly. It looks like https://device-api.xfa.tech/<application-id>/oauth2/redirect.
If XFA rejects the redirect, the 1Password sign-in address in XFA does not match your 1Password account. Correct it in XFA's step 1. Use the address in your browser's address bar when you use 1Password.
Test Connection fails
- Authorization Endpoint and Token Endpoint in 1Password are XFA's. Issuer and User Info Endpoint are your identity provider's.
- Client ID, Client Type and the client secret in 1Password match the client in your identity provider. If they don't, your provider shows
invalid_client. - The device you test from passes the XFA policy you picked.
- Your email address at the identity provider is the same as your email address in 1Password.
Test Connection fails with invalid_scope
XFA stops the sign-in with invalid_scope when the ID token from your identity provider has no email address. Set your provider to put the email address in the ID token: for Microsoft Entra ID, add the optional claim email (see Microsoft Entra ID).
The device does not pass the policy
XFA shows the person which check fails and how to fix it. After they fix it, they unlock 1Password again. To change which checks apply, edit the policy linked to the 1Password application in XFA.