Brivo Wallet Pass Provisioning with Identity Connector for Okta

Alicia Allen Updated by Alicia Allen

Overview

Brivo's Identity Connector integration with Okta allows users to provision Brivo Wallet Passes to users synced to Brivo Access via Okta.

Prerequisites

Before you begin, ensure that you have the following required elements:

  • An active Okta account
  • An active Brivo Access account with an Identity Connector subscription.
  • A configured Okta integration in Brivo Access.
  • Brivo Mobile Passes available to issue.
  • Brivo Wallet Passes available to issue.

To issue Brivo Wallet Passes from Okta, a custom attribute will need to be added to be passed to Brivo with each user.

The attribute will be a boolean(true or false) value. If the value is true, a new Brivo Wallet Pass will be issued to the user if they do not have an existing Brivo Wallet Pass. If the value is false, an existing pass will be revoked. If the value is null no change will be made.

NOTE: In order for a user to be issued a pass, the Brivo account must have available passes. The user must already have a Brivo Mobile Pass. If they do not, one can be provisioned via Okta, or a Brivo Wallet Pass will not be issued.

Add the Brivo Wallet Pass custom field to your default Okta user profile.

  1. Click on Directory on the navigation bar, then click Profile Editor and select your default Okta user profile from the list.
  1. Click Add Attribute.
  2. On the Add Attribute mapping page, set your data type to boolean. Set your display name and variable name to brivoWalletPass. Save the attribute.

Add the attribute to your existing Brivo Identity Management application.

  1. Click on Directory on the navigation bar, then click Profile Editor and select your Brivo Identity Management application from the list.
  1. Click Add Attribute.
  1. On the Add Attribute mapping page, set your data type to boolean. Set your display name to Brivo Wallet Pass. Set your variable name to brivoWalletPass, this will also set your external name. Set the External namespace to urn:ietf:params:scim:schemas:core:2.0:User Give the attribute a description and save the attribute.

NOTE: The variable name and external namespace must be entered exactly as indicated in Step 3. They are case-sensitive.

Add the mapping to your existing Brivo Identity Management Application.

  1. Click Applications, then Applications, and select your application from the list.
  1. Click on the provisioning tab.
  1. Scroll to the bottom of the provisioning tab and click Show unmapped attributes then click the edit icon in line with the Brivo Wallet Pass attribute.
  1. Select Map from Okta Profile. Select brivoWalletPass | boolean.

Issue a pass to a user.

  1. Click the assignments tab then click the edit icon for the user.
  1. Scroll to the Brivo Wallet Pass Field and select true. Click Save.

When this user is provisioned, if they don't already have an assigned Brivo Wallet Pass, one will be issued.

NOTE: If the Brivo Wallet Pass value is set to false, assigned passes will be revoked from the user upon the next sync.

Troubleshoot Brivo Wallet Pass Provisioning

  1. Make sure the users already have a Brivo Mobile Pass assigned or change their BMP value to TRUE in Okta. Users are required to have a Brivo Mobile Pass to receive a Brivo Wallet Pass.
  2. Confirm with your reseller that a TCI value has been set to use Brivo Wallet Passes on your account. If they have not set this value, Brivo Wallet Passes cannot be issued.

How did we do?

Custom Field Mapping with Identity Connector for Okta

Contact