Managing physical access badge

The digital badge provisioning for Apple and Google wallet helps to connect with external physical access control systems (PACS) with IBM® Security Verify performing user provisioning. By using the SwiftConnect connector, users are synchronized to the underlying PACS and are updated when one or more specified user attributes changes

Before you begin

Note: Physical access badges is a requestable feature, CI-131380. To request this feature, contact your IBM Sales representative or IBM contact and indicate your interest in enabling this capability. If you have permission to create a support ticket, create it with the feature numbers. IBM Security Verify trial subscriptions cannot create support tickets.
  • ISV, CIC, CIG (Recon paid), and CIV subscriptions must be enabled.
  • You must have administrative permission to complete this task.
  • Log in to the IBM Security Verify administration console as an Administrator. For more information, see Accessing IBM Security Verify.

Procedure

  1. Select Integrations > Physical access badge.

    If no previous badge exists in the tenant, click the Create badge button to configure a new badge for Apple and Google wallet.

    In case of existing badges, the screen displays the records in a tabular format listed by Name, Description, Provider, Profile, Created and State.

    Click the open list of options icon and select to Edit or Delete the created badge. Selecting Provider information option opens the Provider information popup screen that displays the details required by SwiftConnect to validate the JSON web token (JWT) that is generated in the QR code or url to provision a digital badge to an end user.

  2. Click Create badge button to create a new badge. Refer Creating a physical access badge for further details.
  3. After the badge is created, it can be reviewed and any required changes can be made. Refer Editing a physical access badge for further details.