Enable Axiad Confirm

To enable Axiad Confirm, you must complete the following steps in Axiad Conductor and the Identity Provider (currently only Microsoft Entra ID).

Update config.properties File

Update the UCMS config.properties file with the following information:

• jumio.baseURL=<UCMS URL>, replacing <UCMS URL> with your environment’s URL

• jumio.successUrl=<UP URL>, replacing <UP URL> with your environment’s URL

Update Role Management

Update Role Management in UCMS as follows:

1. Grant Read and Modify privileges to screens / functionalities to the operator role

   1. Configuration: Verification Server List

   2. Configuration: Verification Servers - Create/Edit Jumio Verification Server

2. Grant Allow access privileges to REST APIs to the UCMS_API role

   1. POST /api/v2/users/{uid}/verification This allows UP or an external system to initiate the Identity Verification process

   2. GET /api/v2/users/{uid}/verification/status This allows UP or an external system to retrieve the Identity Verification status

   3. GET /api/v3/users/IdVerification/reports This allows UP or an external system to display the transaction consumption

Note

These privileges can also be given to a custom API role if you would like to integrate your own tool with Axiad Confirm

Upcoming

API documentation for these APIs will be part of the next Confirm release

3. Grant additional privileges to other actions to the required roles

   1. IdConfirmationStatus This enables the help desk operator to see an additional column in the Unified Portal (UP)with the ID Confirmation status

   2. ConfirmID This enables the help desk operator to initiate an Identity Verification for users, with the “Confirm ID” action in UP

Integrate Identity Provider

Currently, Axiad Confirm supports only Microsoft Entra ID. Connect Entra ID to Axiad Conductor using the integration guides.

Create / Update SCIM User Source

Axiad Confirm uses a few attributes to send emails to users and to define from which country and state they are for default selection of the government-issued ID. In the next release, the onboard date will allow you to automatically send an email to the user on their first day.

1. Create or edit an existing SCIM User Source

2. Add the following as Custom Attributes:

Update Entra ID Attribute Mapping

1. In the Microsoft Entra admin center, navigate to the Axiad Conductor Enterprise application

2. In the Manage menu, click Provision

3. In the Manage menu, click on Attribute mapping (Preview)

4. Click Provision Azure Active Directory Users

5. Click Show advanced options

6. Click Edit attribute list for <Axiad Conductor Enterprise Application>

7. Add the following attributes at the bottom of the page:

8. Save the settings

9. Click Add New Mapping

Required

Only provisioning the country attribute is mandatory, but Axiad recommends provisioning all attributes if possible

Create Verification Server

A verification server is required to connect to the identity verification service used by Axiad Confirm. Following the configuration steps in the Create a Verification Server guide.

Create / Update Credential Workflow

1. Create or edit a Credential Workflow

2. In the Configure Workflow Steps section, select Confirm Outcome in the left-side menu

3. Select the Identity Provider from the dropdown

4. Click Done

5. Save the configuration

Optional: Update Notification Template

You can modify the content in the emails sent to users during the Axiad Confirm process.

1. In the Axiad Conductor Operator Portal, navigate to Configuration > Notifications > Notification Templates

2. Locate the Mail to user about Identity Verification template and click the Edit icon

3. Make any preferred changes and Save the template