Issuing mobile passes for HID Mobile Access
This article primarily focuses on issuing passes for HID Mobile Access (for BLE)
Other pass types can also be issued using a similar method:
- Issuing HID Mobile Access passes for Apple/Google Wallet
- Issuing PassFlow mobile passes for Apple/Google Wallet
- Issuing Apple Access mobile passes
Sequence diagram
This sequence diagram shows two approaches - pass issuance triggered from the DoorFlow UI; and pass issuance triggered via the API.
All interaction with HID services are handled by DoorFlow to ensure a consistent flow for all credential types. Issuing credentials for other mobile schemas is done in a very similar way via the DoorFlow API.
In this case:
- The Person is the end user
- The HID Mobile SDK resides inside the app being used for access. This could be either the HID Mobile Access app or a 3rd party app that incorporates the HID Mobile Access SDK
- HID Origo is the HID service infrastructure responsible for populating the SDK above
- DoorFlow is the access control platform that manages connections between all parties
- The Client App populates DoorFlow as/when access control is required
- The DoorFlow Admin UI is the interface that customer staff can use to manage the access control platform
Also see