Configuration Guide

Managing Sponsor Actions
246 of 291
The view functionality is available only if the following conditions are
met:
l If a valid Email ID is present for the Sponsor.
l LDAP Sponsor Username must be mentioned along with the
complete domain. Though Guest and IoT Manager-LDAP
authentication is not case sensitive, the Sponsor view functionality
is case sensitive. For example, if the Provisioner Username in LDAP
is <<name>> and the domain is test.local, then the Sponsor
managing Guest Users view works only if the Provisioner logs in as
<<name>>@test.local.
3. Select the required user accounts and click Approve to approve the access.
The Approve screen is displayed. You can include a message that needs to
be sent as part of the approval email.
4. Select the required user accounts and click Deny/Lock to deny the access.
The Deny / Lock screen is displayed. You can include a message that needs
to be sent as part of the denial email.
5. Select the required user accounts and click Extend Expiration to extend the duration
of Guest User account.
The Extend Expiration screen is displayed and enables you to extend the
validity of Guest User(s) account. The validity is extended based on the
duration specified during the creation.
The duration of each selected Guest User is calculated as:
DURATION = END_TIME – START_TIME
Then the account is modified to:
START_TIME = CURRENT_TIME
END_TIME = START_TIME + DURATION
Extend Expiration Example:
Consider two Guest Users, User 1 valid for a duration of one month and User
2 is valid for a duration of two months, both are expiring tomorrow and the