You can configure DualShield to automatically deploy a MobileID token and client by sending a download link to the user.
Automatic Token/Client deployment can be selected by setting the following MobileID policy setting;
The Token/Client Deployment policy setting may be set one of two ways;
- Automatically push
DualShield will automatically send the MobileID download link via the specified Message Channel.
If the Token Authorisation Code is required and its policy is set to automatically send Authorisation Code, then the Authorisation Code will also be sent in the same message.
To complete automatic provisioning of clients you will also need to configure the Message Channel fields "Primary Delivery Channel:" and "Secondary Delivery Channel:"
DualShield will not send out a download link to the user (the user will need to find and download the MobileID from app stores).
Both the Primary and Secondary Delivery Channel policy setting have four possible settings;
Message sent to the User's mobile device as a text message.
Message sent to the User's email account.
Message sent to the User's Twitter account.
Message sent to the User's landline.
Instead of manually provision a MobileID to an individual user, you can also deploy a MobileID to all users in a domain, group or unit in a single step. Deploying a MobileID means provisioning both MobileID token and client. The DualShield server will first create a MobileID token in the user account of every user. Then, it will send the MobileID client and/or token download link to every user if the MobileID’s provisioning policy is set to automatic provisioning.
To deploy a MobileID token to all users in a domain/unit/group, navigate to the domain/unit/group in the management console and click its context menu.
Select "Provision Tokens"
Select the type of token product, i.e. MobileID, and press "Provision" button.