Configuration Guide

Prerequisite for Provisioner Function
187 of 291
Configuring Provisioners
This module is intended for Guest and IoT Manager Administrator to perform
operations on Provisioner accounts that are stored in the Access Control Engine
local password repository. A Provisioner is a member of the organization whose
account is stored either in the Access Control Engine or in LDAP. These
internally stored Provisioners are referred as Internal Provisioners.
If the Administrator desires to create Guest User accounts to test policies, it is
essential to have a Provisioner account. Administrator can only set up rules to
place the Guest Users in the appropriate Onboarding Template and not modify
the Guest Users. For more information, see Configuring Advanced Details.
Prerequisite for Provisioner Function
The Administrator must ensure that the following criterion is met before the
Provisioners start functioning.
l Provisioner Accounts: Each provisioner must have a Provisioner Account
stored in Access Control Engine or mapped via Access Control Engine to
your LDAP store.
l Access to the Provisioner Application: Each provisioner must be able to
connect to the Provisioner Application via the web browser.
l Connection to an Access Control Engine: The Guest and IoT Manager
Application must have connectivity to the Access Control Engine in order
to save and retrieve guest data.
l Configurations: The Access Control Engine must have the Single
Membership Access Group and Multiple Memberships Access Groups that
form the set of assignable access constraints for Guest Users.
l Notification Settings: The Guest and IoT Manager Application must have
configuration to send Email and SMS notifications to the Guest Users. For
more information, see Enabling E-mail Notification and Configuring SMS
Gateway / Provider.
Note: