Configure Unlock 1Password with Okta

With 1Password Business, you can bring single sign-on (SSO) authentication to your team members by connecting Okta with 1Password using Unlock with SSO.

Before you begin

Before you can set up Unlock with SSO, you’ll need to:

After confirming these prerequisites, follow the steps below.

Step 1: Add the 1Password Business application to Okta

To get started, sign in to your account on Okta.com  , click Admin in the top right, and follow these steps.

These steps were recorded in November 2022 and may have changed since. Refer to the Okta Help Center documentation  for the most up-to-date steps.

1.1: Create the app integration

1. In the Admin Console, go to Applications > Applications.
2. Click Create App Integration.
3. Select OIDC - OpenID Connect as the sign-in method.
4. Select Native Application as the application type.
5. Click Next.

1.2: Configure the application

In General Settings:

• App integration name: Specify a name for your app integration.
• Logo: Upload a logo to associate with the integration (optional).
• Grant type: Choose Authorization Code.
• Sign-in redirect URIs: Copy the URI from the Unlock 1Password with Identity Provider setup page. You’ll also need to add onepassword://sso/oidc/redirect as a sign-in redirect URI. Okta will send the authentication response and ID token for the user’s sign-in request to this URI. The URI will use the following format, depending on your region:
  • https://YOUR_DOMAIN.1password.com/sso/oidc/redirect/
  • https://YOUR_DOMAIN.1password.ca/sso/oidc/redirect/
  • https://YOUR_DOMAIN.1password.eu/sso/oidc/redirect/
  • https://YOUR_DOMAIN.ent.1password.com/sso/oidc/redirect/

In Assignments:

• Controlled access: Select “Skip group assignment for now” and create the app without assigning a group. You can adjust this later.

When you’re finished, click Save. You’ll be redirected to the settings page for the app integration.

1.3: Edit assignments and settings

If you make any changes to your 1Password Unlock with SSO configuration after initial setup, you’ll also need to update the OIDC settings of your Okta application integration.

Assignments:

1. Select the Assignments tab, and click Assign > Assign to People.
2. Search for the email address associated with your 1Password admin account and click Assign.
3. Confirm the user information, then click Save and Go Back.
4. Click Done.

Client Credentials:

Select the General tab, and click Edit to change any of the listed options.

This section has the Client ID and Client authentication information for your app integration. You can edit the authentication type:

• Client authentication: Select None. This option requires the use of a Proof Key for Code Exchange (PKCE) for additional verification. PKCE makes sure that the access token can be redeemed only by the client that requested it.
• Proof Key for Code Exchange (PKCE): Check “Require PKCE as additional verification”.

Click Save to commit your Client Credentials changes.

General Settings:

Select the General tab, and click Edit to change any of the listed options.

• Application:
  • App integration name: You can edit the name you provided when creating the app integration.
  • Grant type: You can edit the grant type you provided when creating the app integration.
• Login:
  • Sign-in redirect URIs: You can edit the URI you provided when creating the app integration. Copy the URI from the Unlock 1Password with SSO setup page. It will use the following format, depending on the region your account is in: https://YOUR_DOMAIN.1password.com/sso/oidc/redirect and onepassword://sso/oidc/redirect.
  • Initiate login URI: Optional. Include a URI to have Okta initiate the sign-in flow. When Okta redirects to this endpoint, the client is triggered to send an authorize request.

Click Save to commit your General Settings changes.

1.4 Required claims

1Password requires sub, name, and email claims from Okta. With Okta’s default settings, no action is required on your part. By default, Okta provides a subject claim, and name and email are mapped automatically.

If needed, you can map Okta attributes to 1Password app attributes in the Profile Editor. 

Step 2: Configure Unlock with SSO

You can only save an identity provider configuration after successfully testing the connection by signing in to both Okta and 1Password. Changes won’t be saved if you can’t successfully authenticate with Okta. This prevents locking yourself out of 1Password.

To unlock 1Password with Okta, the email address you use to sign in to 1Password must match the email address you use to sign in to Okta.

1. Sign in to your account on 1Password.com.
2. Click Security in the sidebar.
3. Click Unlock 1Password with Identity Provider.
4. Follow the onscreen instructions to set up Unlock with SSO.
   • The instructions list a single sign-in URI. When configuring in Okta, add onepassword://sso/oidc/redirect as an additional sign-in redirect URI.
   • Refer to your Okta documentation to find your Okta well-known URL. It may follow one of the following formats: YOUR_OKTA_DOMAIN.okta.com/.well-known/openid-configuration or YOUR_OKTA_DOMAIN.okta.com/oauth2/default/.well-known/openid-configuration
5. Test your connection. You’ll be directed to Okta to sign in, then redirected to 1Password to sign in. This verifies connectivity between 1Passsword and Okta.

   The email address you use to sign in to 1Password must match the email address you use to sign in to Okta.

6. Click Save.

Step 3: Specify which team members will unlock 1Password with Okta and set a grace period

After configuring Unlock with SSO, you’ll be redirected to the settings page.

Prerequisites

Before you begin, we recommend creating a test group in 1Password for each group of team members who plan to test Unlock with Okta.

1. Create a custom group.

   Give the group a descriptive name, like "Okta testers", for clarity.

2. Add team members to the group.

   If you plan on inviting additional team members to test Unlock with Okta at a later date, create a new custom group for each additional set of testers.

3.1 People unlocking 1Password with an identity provider

By default, “People unlocking 1Password with an identity provider” is set to “No one”. To specify which team members will unlock 1Password with Okta, select one of the options:

“No one”

To turn off Unlock with Okta, select “No one”.

“Selected groups” (recommended)

Only the team members in groups you choose will sign in with Okta. Learn how to use custom groups in 1Password Business.

1. Choose “Selected groups” under “People unlocking 1Password with an identity provider”, then click Select Groups.
2. Select the groups you want to unlock 1Password with Okta and click Update Groups.

   You'll see the number of people in the groups you selected.

“Everyone except guests”

All team members, except owners and guests, will sign in with Okta. All existing users will be prompted to switch to Unlock with Okta, and all new users will use their Okta username and password when joining 1Password. Guests and owners will sign in with an account password and Secret Key.

“Everyone” (not recommended)

Guests and all team members, except owners, will sign in with Okta. All existing users will be prompted to switch to Unlock with Okta, and all new users will use their Okta username and password when joining 1Password.

3.2 Set a grace period

Team members who already have 1Password accounts will need to switch to unlocking with Okta. Specify the number of days before team members must switch to unlocking with Okta, and how often they should be reminded to migrate. By default, the grace period is set to 5 days.

The grace period begins when an administrator adds a group after they choose the “Selected groups” option or when an administrator configures Unlock with Okta for everyone on the team. You’ll see the grace period listed next to each group configured to unlock with Okta.

If the grace period has already expired when a user first attempts to sign in, they’ll be asked to contact their 1Password administrator to have their account manually recovered.

If you plan to have more team members unlock with Okta after initial configuration, we recommend that you create a new custom group with its own grace period. This will avoid newly assigned team members needing to go through manual account recovery.

Optional: Add a 1Password tile to your team’s Okta Dashboard

For the time being, the Unlock with SSO integration for 1Password won’t be included in the Okta App Catalog.

If you’d like to add a 1Password tile to your team members' Okta Dashboards, refer to the Okta Help Center guide to create a Bookmark App integration. 

You’ll be asked for a URL. Enter <YOURSUBDOMAIN>.1password.com/signin/.

Manage settings

To manage your settings, sign in to your account on 1Password.com, then click Security in the sidebar and choose Unlock 1Password with Identity Provider.

Configuration

To change your configuration with Okta, click Edit Configuration, then follow the onscreen instructions to set up Unlock with SSO.

You can only save an identity provider configuration after you've successfully tested the connection. Changes won't be saved if you can't successfully authenticate with Okta. This prevents locking yourself out of 1Password.

People assignments and biometrics

Click Edit at the bottom of the settings page to change which users are assigned to unlock 1Password with Okta.

• To specify which team members will unlock 1Password with Okta, select “No one”, “Selected groups”, “Everyone except guests”, or “Everyone”.

  "Selected groups" is recommended. Learn how to use custom groups in 1Password Business. To turn off Unlock with Okta, select "No one".

• Specify the number of days before team members must switch to unlocking with Okta.

  The default grace period is 5 days. If a team member doesn't migrate to Unlock with Okta before the end of the grace period, they must contact their administrator to recover their account.

• To allow team members to unlock with Touch ID, Face ID, Windows Hello, and other biometrics, select “Allow people to unlock 1Password using biometrics”. Specify the number of days or weeks before they’ll be asked to sign in to Okta again.

  When biometric unlock is turned on, your team members can access 1Password while offline, until the time period specified. Vault access will be online-only after the elapsed period.

Click Review Changes to verify your choices, then click Save.

Next steps

To use Unlock with Okta yourself, get started with Unlock 1Password with Okta as a team member.

Learn how to unlock 1Password with Okta on all of your devices and add additional trusted devices.

Get help

You can find your Client ID in the Okta Admin Console.

Refer to your Okta documentation to find your Okta well-known URL. It may follow one of the following formats: YOUR_OKTA_DOMAIN.okta.com/.well-known/openid-configuration or YOUR_OKTA_DOMAIN.okta.com/oauth2/default/.well-known/openid-configuration. The format may be different if you have a custom authorization server.

If a team member is moved from a group that unlocks with Okta to one that doesn’t, they’ll be prompted to create an account password and download their Emergency Kit.

Learn more

• About 1Password Unlock with Okta
• Understanding Unlock with SSO security
• Add and remove team members
• Use custom groups in 1Password Business
• If you’re having trouble unlocking 1Password with Okta