Instance Configuration - Cisco WAP121 Administration Manual

Captive Portal

Instance Configuration

STEP 3
Instance Configuration
STEP 1
STEP 2
STEP 3
STEP 4
STEP 5
Cisco Small Business WAP121 and WAP321 Wireless-N Access Point with PoE
Click Save. The changes are saved to the Running Configuration and to the Startup
Configuration.
You can create up to two Captive Portal instances; each CP instance is a defined
set of instance parameters. Instances can be associated with one or more VAPs.
Different instances can be configured to respond differently to users as they
attempt to access the associated VAP.
To create a CP instance and configure its settings:
Click Captive Portal > Instance Configuration in the navigation window.
Ensure that Create is selected from the Captive Port Instances list.
Enter an Instance Name from 1 to 32 alphanumeric characters and click Save.
Select the instance name from the Captive Port Instances list.
The Captive Portal Instance Parameters fields redisplay, with additional options.
Configure the parameters:
• Instance ID—The instance ID. This field is non-configurable.
• Administrative Mode—Enables and disables the CP instance.
• Protocol—Specifies HTTP or HTTPs as the protocol for the CP instance to
use during the verification process.
- HTTP—Does not use encryption during verification.
- HTTPS—Uses the Secure Sockets Layer (SSL), which requires a
certificate to provide encryption.
The certificate is presented to the user at connection time.
• Verification—The authentication method for CP to use to verify clients:
- Guest—The user does not need to be authenticated by a database.
- Local—The WAP device uses a local database to authenticated users.
9
141