Configuration Guide
Table Of Contents
- ExtremeControl Guest and IoT Manager Configuration
- Extreme Networks® Software License Agreement
- Table of Contents
- About this Document
- New in this Document
- Guest and IoT Manager Overview
- Installing Guest and IoT Manager
- Administering Guest and IoT Manager
- Configuring Onboarding Template
- Creating an Onboarding Template
- Configuring the Common Details
- Configuring the Guest User Account Details
- Configuring Sponsor Approval
- Configuring the Device Record Details
- Configuring Device Type Groups
- Configuring the Account Notification Templates
- Configuring Advanced Details
- Configuring Guest User Provisioning Using Outlook Add-in
- Configuring Guest User Provisioning Using Vouchers
- Configuring Guest User and Device Provisioning Using CSV
- Configuring Device Record Details
- Configuring Zero Touch Guest User Provisioning
- Managing Onboarding Templates
- Configuring Custom Attributes
- Configuring Access Groups
- Creating an Onboarding Template
- Configuring Provisioners
- Configuring Self-Services
- Managing Guest Users
- Managing Devices
- Configuring Guest and Devices
- Using Self-Provisioning Services
- Guest and IoT Manager Add-In for Outlook
- Automated Login of the Guest User using the Login URL
- Troubleshooting and FAQs
- Testing RADIUS Connection Settings
- Restarting Guest and IoT Manager
- Problem: Virtual Appliance Troubleshooting
- Problem: Saving Access Control Engine Settings
- Problem: User Groups / End System Group Not Visible in Guest and IoT Manager
- Problem: Provisioner Cannot Login
- Problem: Guest and IoT Manager Email / SMS Notification Failed
- Problem: Unable to Access Guest and IoT Manager Application URL
- Problem: User and Device Troubleshooting
- Problem: Sponsor List is Not Available
- Problem: Modification in Network Interface settings does not reflect post dep...
- Problem: Outlook Add-in Issues
- Problem: Service Unavailable in Browser
- Problem: Time Zone Issues for Schedule Tasks
- Problem: Users/Devices are not getting cleaned up for Housekeeping Tasks
- Problem: Unable to Access GIM UI
- Problem: LDAP Provisioner login fails
- Problem: LDAP Sponsors are not populating in the Self-Service Page
- Problem: Server Error during bulk creation
- Problem: Unable to Renew Password
- Problem: Guest User account is not created post sending SMS
- Problem: Login URL redirects to Captive Portal
- Problem: “Server Error. Please contact Administrator Error message on clickin...
- Problem: FQDN not being used in URLs
- Problem: Unable to Customize Provisioner Login page
- Problem: Login failed. Invalid credentials/Account Expired” message on clicki...
- Problem: Outlook Add-in throws Security Exception post enabling FQDN
- Command Line Interface
Managing Access Control Engine
81 of 291
Certificate
File
Adds a new Root Certificate for the application. The certificate file
must contain PEM-encoded certificate.
Make sure that the certificate does not have a password
associated with it. The certificate encoding format must be
any one of the following format.
Note:
l DER encoded binary X.509 file containing the
certificate.
l Base64 encoded file containing both the
certificate and the private key.
Alias for
this
certificate
Configures a short unique string to identify the key entry of the
Root Certificate in the keystore.
You can use any name; Access Control Engine uses this
Alias name as a key to identify the certificate in the
keystore. All the installed certificate resides in the Guest
and IoT Manager keystore.
Important:
Do not confuse the Guest and IoT Manager keystore
with the browser keystore and the certificates that
secure HTTPS browser sessions.
Viewing License Status
When you deploy Guest and IoT Manager for the first time, ensure that a valid
Guest and IoT Manager license is added and enforced in Extreme Management
Center so that Access Control Engine details can be configured in Guest and IoT
Manager. For more information, see Configuring Engine Details.
If the license is expired:
l License status is displayed as Not Installed / Expired.
l Provisioner users are logged out including Outlook Provisioner and all the
configured self-services become non-operational.
l Valid new license needs to be added again to function.