Published On: December 2ⁿᵈ, 2019 20:37

Cisco Identity Services Engine Administrator Guide, Release 2.7

Cisco ISE Guest Services

Cisco Identity Services Engine (ISE) guest services enable you to provide secure network access to guests such as visitors, contractors, consultants, and customers. You can support guests with base Cisco ISE licenses, and you can choose from several deployment options depending on your company’s infrastructure and feature requirements.

Cisco ISE provides web-based and mobile portals to provide on-boarding for guests and employees to your company’s network and internal resources and services.

From the Admin portal, you can create and edit guest and sponsor portals, configure guest access privileges by defining their guest type, and assign sponsor privileges for creating and managing guest accounts.

ISE Community Resource

For the complete list of ISE Community Resources for ISE Guest and Web Authentication, see ISE Guest Access - ISE Guest and Web Authentication.

End-User Guest and Sponsor Portals in Distributed Environment

Cisco ISE end-user web portals depend on the Administration, Policy Services, and Monitoring personas to provide configuration, session support, and reporting.

  • Administration Node—Configuration changes that you make to users, devices, and end-user portals are written to the Administration node.

  • Policy Services Node—The end-user portals run on a Policy Services Node, which handles all session traffic, including: network access, client provisioning, guest services, posture, and profiling. If a Policy Service Node is part of a node group, and one node fails, the other nodes detect the failure and reset any pending sessions.

  • Monitoring Node—The Monitoring node collects, aggregates, and reports data about the end-user and device activity on the My Devices, Sponsor, and Guest portals. If the primary Monitoring node fails, the secondary Monitoring node automatically becomes the primary Monitoring node.

Guest and Sponsor Accounts

  • Guest Accounts—Guests typically represent authorized visitors, contractors, customers, or other users who require temporary access to your network. You can also use guest accounts for employees if you prefer to use one of the guest deployment scenarios to allow employees to access the network. You can access the Sponsor portal to view guest accounts created by a sponsor and by self-registering guests.

  • Sponsor Accounts—Use the Sponsor portal to create temporary accounts for authorized visitors to securely access your corporate network or the Internet. After creating the guest accounts, you also can use the Sponsor portal to manage these accounts and provide account details to the guests.

Guest accounts can be created by:

  • Sponsors—On the Admin portal, you can define the access privileges and feature support for sponsors, who can access the Sponsor portal to create and manage guest accounts.

  • Guests—Guests can also create their own accounts by registering themselves on the Self-Registered Guest portal. Based on the portal configuration, these self-registering guests may need sponsor approval before they receive their login credentials.

    Guests can also choose to access the network using the Hotspot Guest portal, which does not require the creation of guest accounts and login credentials, such as username and password.

  • Employees—Employees who are included in identity stores (such as Active Directory, LDAP, Internal Users) can also gain access through the credentialed Guest portals (Sponsored-Guest and Self-Registered Guest portals), if configured.

After their guest accounts are created, guests can use the Sponsored-Guest portal to log in and gain access to the network.

Guest Types and User Identity Groups

Each guest account must be associated with a guest type. Guest types allow a sponsor to assign different levels of access and different network connection times to a guest account. These guest types are associated with particular network access policies. Cisco ISE includes these default guest types:

  • Contractor—Users who need access to the network for an extended amount of time, up to a year.

  • Daily—Guests who need access to the resources on the network for just 1 to 5 days.

  • Weekly—Users who need access to the network for a couple of weeks.

When creating guest accounts, certain sponsor groups can be restricted to using specific guest types. Members of such a group can create guests with only the features specified for their guest type. For instance, the sponsor group, ALL_ACCOUNTS, can be set up to use only the Contractor guest type, and the sponsor groups, OWN_ACCOUNTS and GROUP_ACCOUNTS, can be set up to use Daily and Weekly guest types. Also, since self-registering guests using the Self-Registered Guest portal typically need access for just a day, you can assign them the Daily guest type.

The guest type defines the user identity group for a guest.

For more information, see:

Create or Edit a Guest Type

Besides creating new guest types, you can edit the default Guest Types' default access privileges and settings. The changes that you make are applied to the existing Guest accounts that were created using this Guest Type. Guest users who are logged in will not see these changes until they log out and log in again. You can also duplicate a Guest Type to create additional Guest Types with the same access privileges.

For an existing guest account, attributes are configured for that account by the Guest Type.

If you make changes to a Guest Type, active Guest accounts will take on all the attributes of the updated Guest Type, including the default access times, dates, and duration, which can then be edited. In addition, the custom fields from the original Guest Type are copied to the updated Guest Type.

Each Guest Type has a name, description, and a list of sponsor groups that can create guest accounts with this guest type. You can designate some guest types as follows: use just for self-registering guests, or do not use to create Guest accounts (by any sponsor group).

Procedure

Fill in the following fields.

  • Guest type name—Provide a name (from 1 to 256 characters) that distinguishes this Guest Type from the other Guest Types.

  • Description—Provide additional information (maximum of 2000 characters) about the recommended use of this Guest Type, for example, Use for self-registering Guests. Do not use for Guest account creation, and so forth.

  • Language File—This field allows you to export and import the language file, which contains content for email subject, email message, and SMS messages in all supported languages. These languages and content are used in notifications about an expired account, and are sent to guests who are assigned to this guest type. If you are creating a new guest type, this feature is disabled until after you save the guest type. For more information about editing the lanaguage file, see Portal Language Customization.

  • Collect Additional Data—Click the Custom Fields... button to select which custom fields to use to collect additional data from guests using this Guest Type.

    To manage custom fields, choose Work Centers > Guest Access > Settings > Custom Fields.

  • Maximum Access Time

    • Account duration starts—If you select From first login, the account start time starts when the guest user first logs in to the guest portal, and the end time equals the configured duration time. If the guest user never logs in, the account remains in the Awaiting first login state until the guest account purge policy removes the account.

      Values are from 1 to 999 days, hours, or minutes.

      A self-registered user's account starts when they create and log on to their account.

      If you select From sponsor-specified date, enter the maximum number of days, hours, or minutes that Guests of this Guest Type can access and stay connected to the network.

      If you change these settings, your changes will not apply to existing Guest accounts that were created using this Guest Type.

    • Maximum account duration—Enter the number of days, hours, or minutes that guests assigned to this guest type can log on.

      Note 

      The account purge policy checks for expired guest accounts, and sends expiration notification. This policy runs every 20 minutes, so if you set the account duration to less than 20 mins, it is possible that expiration notices may not be sent out before the account is purged.

      You can specify the duration time and the days of the week when access is provided to the guests of this Guest Type by using the Allow access only on these days and times option.

      • The days of the week that you select limits access to the dates that are selectable in the Sponsor's calendar.

      • Maximum account duration is enforced in the sponsor portal, when the Sponsor picks duration and dates.

    The settings you make here for access time affect the time settings that are available on the sponsor portal when creating a guest account. For more information, see Configuring the Time Settings Available to Sponsors.

  • Logon Options

    • Maximum simultaneous logins—Enter the maximum number of user sessions that users assinged to this Guest Type can have running concurrently.

    • When guest exceeds limit—When you select Maximum simultaneous logins, you must also select the action to take when a user connects after the maximum number of log ins is reached.

      • Disconnect the oldest connection

      • Disconnect the newest connection—Optionally select Redirect user to a portal page showing an error message: An error message is displayed for a configurable amount of time, then the session is disconnected, and the user is redirected to the Guest portal. The error page's content is configured on the Portal Page Customization dialog, on the Messages > Error Messages page.

    • Maximum devices guests can register—Enter the maximum number of devices that can be registered to each Guest. You can set the limit to a number lower than what is already registered for the Guests of this Guest Type. This only affects newly created Guest accounts. When a new device is added, and the maximum is reached, the oldest device is disconnected.

    • Endpoint identity group for guest device registration—Choose an endpoint identity group to assign to guest devices. Cisco ISE provides the GuestEndpoints endpoint identity group to use as a default. You can also create more endpoint identity groups if you choose to not use the default.

    • Allow guest to bypass the Guest portal—Allows users to bypass the credentialed guest-type captive portal (web authentication page), and access the network by providing credentials to wired and wireless (dot1x) supplicants or VPN clients. Guest accounts change to the Active state, bypassing the Awaiting Initial Login state and the AUP page, even if the AUP is required.

      If you do not enable this setting, users must first log in through the credentialed Guest captive portal before they are able to access other parts of the network.

  • Account Expiration Notification

    • Send account expiration notification __ days before account expires—Send a notification to Guests before their account expires and specify how many days, hours, or minutes before the expiration.

    • View messages in—Specify the language to use when displaying email or SMS notifications as you set them up.

    • Email—Send account expiration notices by email.

    • Use customization from—Apply the same customizations that you configured for the selected portal to this Guest Type's account expiration emails.

    • Copy text from—Reuse email text that you created for another Guest Type's account expiration email.

    • Send test email to me at

    • SMS—Send account expiration notices by SMS.

      The settings that follow for SMS are the same as for email notifications, except that you choose an SMS gateway for Send test SMS to me.

  • Sponsor Groups—Specify the sponsor groups whose members can create a guest account using this guest type. Delete the sponsor groups that you do not want to have access to this guest type.


What to do next
  • Create or modify sponsor groups to use this guest type. For more information, see Sponsor Groups.

  • If appropriate, assign this guest type to self-registering guests in the Self-Registered Guest portal. For more information, see Create a Self-Registered Guest Portal.

Disable a Guest Type

You cannot delete the last remaining guest type or guest types that are being used by guest accounts. If you want to delete a guest type that is in use, first ensure that it is no longer available for use. Disabling a guest type does not affect guest accounts that were created with that guest type.

The following steps explain how to prepare for and disable a target guest type.

Procedure

Step 1

Identify the sponsor groups that allow the sponsor to create guests using the target guest type. Choose Work CentersGuest AccessPortals and ComponentsSponsor Groups, and open each sponsor group and examine the This sponsor group can create accounts using these guest types list.

Step 2

Identify the Self-Registered portals that assign the target guest type. Choose Work Centers > Guest Access > Portals and Components > Guest Portals. Open each Self-Registered Guest portal. If the portal is using the specific guest type, expand Portal Settings, and change the assigned guest type in the field Employees using this portal as guests inherit login options from:.

Step 3

Open the guest type you wish to delete, and delete all sponsor groups that you identified in the previous steps. This action effectively prevents all sponsors from using creating a new guest account with this guest type. Choose Work Centers > Guest Access > Portals and Components > Guest Type.


That's it. You can't actually delete the guest type. Make sure you don't use in any portals in the future.

Configure Maximum Simultaneous Logins for Endpoint Users

You can configure the maximum number of simultaneous logins that are allowed for a guest.

When the user logs in to a guest portal, and is successfully authenticated, that user's number of existing logins is checked to see if the user has already reached the maximum number of logins. If so, the Guest user is redirected to an error page. An error page is displayed, and the session is stopped. If that user tries to access the internet again, the user's connection is redirected to the guest portal's login page.

Before you begin

Make sure that the authorization profile that you are using in the authorization policy for this portal has Access Type set to Access_Accept. If Access Type is set to Access_Reject, then maximum simultaneous logins is not enforced.

Procedure


Step 1

Choose Work Centers > Guest Access > Portals & Components > Guest Type, and under Login Options:

  1. Check Maximum simultaneous logins. This is already enabled on the default guest types.

  2. Under When guest exceeds limit: , selectDisconnect the newest connection.

  3. CheckRedirect user to a portal page showing an error message, and choose the maximum number of simultaneous logins to allow.

Step 2

Choose Policy > Policy Elements > Results, and create an authorization profile:

  1. Under Common Tasks, check Web Redirection, then:

    • In the first drop-down, choose Centralized Web Auth.

    • Enter the ACL you created as part of the prerequisite.

    • For Value, select the guest portal to be redirected to.

  2. Scroll down in Common Tasks, and checkReauthentication, then:

    • In Timer, enter the amount of time you want the error page to display before redirecting the user to the guest portal.

    • In Maintain Connectivity During Reauthentication, choose Default.

Step 3

Choose Policy > Policy Sets, and create an authorization policy so that when the attribute NetworkAccess.SessionLimitExceeded is true, the user is redirected to the portal.


What to do next

You can customize the text of the error page on the Portal Page Customization tab, in the tab Messages Error Messages by changing the text of the error message key ui_max_login_sessions_exceeded_error.

Schedule When to Purge Expired Guest Accounts

When an active or suspended guest account reaches the end of its account duration (as defined by the sponsor when creating the account), the account expires. When guest accounts expire, the affected guests cannot access the network. Sponsors can extend expired accounts before they are purged. However, after an account is purged, sponsors must create new accounts.

When expired guest accounts are purged, the associated endpoints and reporting and logging information are retained.

Cisco ISE automatically purges expired guest accounts every 15 days, by default. The Date of next purge indicates when the next purge will occur. You can also:
  • Schedule a purge to occur every X days. The first purge will occur in X days at Time of Purge, then purges occur every X days.

  • Schedule a purge on a given day of the week every X weeks. The first purge occurs on the next Day of Week at Time of Purge, then purges occur every configured number of weeks on that day and time. For example, on Monday you set purges to occur on Thursday every 5 weeks. The next purge will be the Thursday of this week, not the Thursday 5 weeks from now.

  • Force a purge to happen immediately by clicking Purge Now.

If the Cisco ISE server is down when the purge is scheduled to run, the purge is not executed. The purge process will run again at the next scheduled purge time, assuming the server is operational at that time.

Procedure


Step 1

Choose Work Centers > Guest Access > Settings > Guest Account Purge Policy.

Step 2

Choose one of these options:

  • Click Purge Now to immediately purge the expired guest account records.
  • Check Schedule purge of expired guest accounts to schedule a purge.
    Note 

    After each purge is completed, the Date of next purge is reset to the next scheduled purge.

Step 3

Specify after how many days of inactivity to purge user-specific portal records maintained in the Cisco ISE database for LDAP and Active Directory users.

Step 4

Specify the number of days of inactivity to expire users in Expire portal-user information after. This setting prevents LDAP and Active Directory accounts that were never used from staying in the ISE database indefinitely.

Step 5

Click Save. If you do not want to save any updates you made to the settings, click Reset to revert to the last saved values.


Add Custom Fields for Guest Account Creation

When providing guest access, you may want to collect information from your guests beyond just their names, email addresses, and phone numbers. Cisco ISE provides custom fields that you can use to collect additional information about guests that is specific to your company’s needs. You can associate the custom fields with guest types and with the Self-Registered Guest and Sponsor portals. Cisco ISE does not provide any default custom fields.

Procedure


Step 1

To add, edit, or delete custom fields for all Guest and Sponsor portals, choose Guest Access > Settings > Custom Fields.

Step 2

Enter the Custom Field Name, pick a Data Type from the drop-down list, and enter Tip Text to help provide additional information about the custom field. For instance, if you enter Date of Birth, pick Date-MDY, and enter a tip for the date format as MM/DD/YYYY.

Step 3

Click Add.

The custom field appears in the list in alphabetical order or in the context of the sorted order.

Step 4

Click Save. If you do not want to save any updates you made to the settings, click Reset to revert to the last saved values.

Note 

If you delete a custom field, it will no longer be available for selection in the Custom Fields list for guest types and in the Self-Registered Guest and Sponsor portals settings. If the field is being used, Delete will be disabled.


What to do next

You can include the desired custom fields:

  • When defining a guest type so that accounts created with that guest type will include this information. See Create or Edit a Guest Type.

  • When configuring the Sponsor portal for sponsors to use when creating guest accounts. See .
  • When requesting information from self-registering guests using a Self-Registered Guest portal. See Create a Self-Registered Guest Portal.

Specify Email Addresses and SMTP Servers for Email Notifications

Cisco ISE allows you to send emails to sponsors and guests, notifying them of information and instructions. You can configure SMTP servers to deliver these email notifications. You can also specify the email address from which the notifications will be sent to guests.


Note

Guest notifications require an UTF-8 compatible e-mail client.

HTML-capable e-mail client (with functionality enabled) is needed to use the single click sponsor approval feature.


Procedure


Step 1

To specify email settings and configure SMTP servers for all Guest and Sponsor portals, choose Work Centers > Guest Access > Settings > Guest Email Settings.

Step 2

Enable email notifications to guests is checked by default. If you disable this setting, guests will not receive email notifications regardless of any other settings you may have enabled while configuring Guest and Sponsor portals.

Step 3

Enter the Default “From” email address that is designated for sending email notifications to guests. For example, donotreply@ yourcompany.com.

Step 4

Do one of the following:

  • Check Send notifications from sponsor's email address (if sponsored) if you want guests to receive notifications from the sponsor who created their accounts. Self-registering guests will receive notifications from the default email address.
  • Check Always send notifications from the default email address if you want guests to receive notifications, regardless of whether they are sponsored and self-registering.
Step 5

Click Save. If you do not want to save any updates you made to the settings, click Reset to revert to the last saved values.


Assign Guest Locations and SSIDs

A Guest Location defines a name for a time zone, and is used by ISE to enforce time-related settings of logged on Guests. Guest Locations are assigned to Guest accounts by Sponsors creating a Guest account, and by self-registering Guests. The default Guest Location is San Jose. If no other Guest Locations are added, all accounts are assigned this Guest Location. You can't delete the San Jose Guest Location unless you create one or more new Locations. Unless all your Guests will be in the same time-zone as San Jose, create at least one Guest Location with the required time-zone.


Note

Guest access times are based on the Guest Location's time zone. A Guest user may not be able to login if the Guest Location's time zone doesn't match the system time zone. In this case, the Guest user may get an "Authentication Failed" error. You might see the "Guest active time period not yet started" error message in the debug report. As a workaround, you can adjust the Guest access start time to match the local time zone of the Guest user by using the Manage Accounts option.

The SSIDs you add here are available to Sponsor Portals, so Sponsors can tell the Guest which SSID to connect to.

You can't delete a Guest Location or a SSID if it is configured in a Sponsor portal or assigned to a Guest account.

Procedure


Step 1

To add, edit or delete Guest Locations and SSIDs for Guest and Sponsor portals, choose Work Centers > Portals & Components > Settings > Guest Locations and SSIDs.

Step 2

For Guest Locations:

  1. For each time-zone that you need to support, enter a Location name and pick a Time zone from the drop-down list.

  2. Click Add.

    Note 
    In a Guest Location, the name of the place, the name of the time zone, and the GMT offset are static; you cannot change them. The GMT offset does not change with daylight savings time changes. The GMT offsets are the opposite of what is shown in the list. For example, Etc/GMT+3 is actually GMT-3.
    Note 
    For From First-login guest type, ensure that you configure a Guest Location (time zone) only if you intend to configure the access time restrictions in the Work Centers > Guest Access > Portals & Components > Guest Types page.
Step 3

For Guest SSIDs:

  1. Enter the SSID names of the networks that will be available for guests to use at the Guest Locations.

  2. Click Add.

Step 4

Click Save. To revert to the last saved values, click Reset.


What to do next

If you added a new Guest Location or SSID, you can:

  • Provide the SSIDs for Sponsors to use when creating Guest accounts. See Portal Settings for Sponsor Portals.

  • Add the Guest Locations to Sponsor Groups, so Sponsors assigned to that group can use them when creating guest accounts. See Configure Sponsor Groups.

  • Assign the Guest Locations available to self-registering guests using a Self-Registered Guest portal. See Create a Self-Registered Guest Portal.

  • For existing guest accounts, edit them manually to add SSIDs or Locations.

Rules for Guest Password Policies

Cisco ISE has the following built-in rules for guest passwords:
  • The Guest password policy applies to sponsor portals, self registered portals, accounts uploaded in a CSV file, passwords created using the ERS API, and user created passwords.

  • Changes to the guest password policy do not affect existing accounts, until the guests passwords have expired and need to be changed.

  • Passwords are case sensitive.

  • The special characters <, >, /, space, comma and % cannot be used.

  • Minimum length and minimum required characters apply to all passwords.

  • Passwords cannot match usernames.

  • New passwords cannot match current passwords.

  • Guests do not receive notifications prior to password expiration, unlike guest account expiration. When guest passwords expire, either sponsors can reset the password to a random password or guests can log in using their current login credentials and then change their password.


Note

The guest default username is four alpabetic and password is four numeric characters. Short, easy to remember usernames and passwords are adequate for short-term guests. You can change the username and password length in ISE, if you desire.


Set the Guest Password Policy and Expiration

You can define a password policy for all Guest portals. A Guest password policy determines how the password is generated for all guest accounts. A password can be a mixture of alphabetic, numeric, or special characters. You can also set the number of days after which guest passwords will expire, requiring guests to reset their passwords.

The Guest password policy applies to sponsor portals, self registered portals, accounts uploaded in a CSV file, passwords created using the ERS API, and user created passwords.

Procedure


Step 1

Choose Guest Access > Settings > Guest Password Policy.

Step 2

Enter the Minimum password length (in characters) for the guest passwords.

Step 3

Specify the characters from each character set that can be used by guests to create passwords.

Choose one of the following options under Allowed Characters and Minimums to specify the password policy for guests:
  • Use all the characters from each character set.
  • To prevent the use of certain characters, choose Custom from the drop-down menu, and delete these characters from the predefined and complete sets.
Step 4

Enter the minimum number of characters to use from each set.

The total number of required characters across the four character sets should not exceed the overall Minimum password length.
Step 5

Choose one of the following options under Password Expiration:

  • Specify the frequency (in days) when guests have to change their passwords after they first log in. If the guests do not reset their passwords before they expire, the next time they log in to the network using their original login credentials, they are prompted to change their passwords.
  • Set the passwords to never expire.
Step 6

Click Save. If you do not want to save any updates you made to the settings, click Reset to revert to the last saved values.


What to do next

You should customize the error messages that are related to the password policy to provide the password requirements.

  1. Choose Guest Access > Portals & Components > Sponsored-Guest Portals or Self-Registered Guest Portals > Edit > Portal Page Customization > Error Messages.

  2. Search for the keyword “policy.”

Rules for Guest Username Policies

Cisco ISE has the following built-in rules for guest username policies:
  • Changes to the guest username policy do not affect existing accounts, until the guest accounts have expired and need to be changed.

  • The special characters <, >, /, space, comma and % cannot be used.

  • Minimum length and minimum required characters apply to all system-generated usernames, including usernames based on email addresses.

  • Passwords cannot match usernames.

Set the Guest Username Policy

You can configure rules for how guest usernames are created. A generated username can be created based on the email address, or based on the first name and last name of the guest. The Sponsor can also create a random number of guest accounts to save time when creating multiple guests, or when guest names and email addresses are not available. Randomly generated guest usernames consist of a mixture of alphabetic, numeric, and special characters. These settings affect all guests.

Procedure


Step 1

To define the guest username policies for all Guest and Sponsor portals, choose Work Centers > Portals & Components > Settings > Guest Username Policy.

Step 2

Enter the Minimum username length (in characters) for the guest usernames.

Step 3

Choose one of the options under Username Criteria for Known Guests to specify the policy for creating usernames for known guests.

Step 4

Choose one of the following options under Characters Allowed in Randomly-Generated Usernames to specify the policy for creating random usernames for guests:

  • Use all characters from each character set.
  • To prevent the use of certain characters, choose Custom from the drop-down menu, and delete these characters from the predefined and complete sets.
Step 5

Enter the minimum number of characters to use from each set.

The total number of characters from the three character sets should not exceed the number specified in Minimum username length.
Step 6

Click Save. If you do not want to save any updates you made to the settings, click Reset to revert to the last saved values.


What to do next

You should customize the error messages that are related to the username policy to provide the username requirements.

  1. Choose Work Centers > Guest Access > Portals & Components > Sponsored-Guest Portals, Self-Registered Guest Portals, Sponsor Portals, or My Devices Portals > Edit > Portal Page Customization > Error Messages.

  2. Search for the keyword “policy.”

SMS Providers and Services

SMS services send SMS notifications to guests that are using credentialed Guest portals. If you plan to send SMS messages, enable this service. . Whenever possible, configure and provide free SMS service providers to lower your company's expenses.

Cisco ISE supports a variety of cellular service providers that provide free SMS services to their own subscribers. You can use these providers without a service contract and without configuring their account credentials in Cisco ISE. These include ATT, Orange, Sprint, T-Mobile, and Verizon.

You can also add other cellular service providers that offer free SMS services or a global SMS service provider, such as a Click-A-Tell. The default global SMS service provider requires a service contract and you must configure their account credentials in Cisco ISE.

  • If self-registering guests pick their free SMS service provider on the Self-Registration form, SMS notifications with their login credentials are sent to them free of cost. If they do not pick an SMS service provider, then the default global SMS service provider that is contracted by your company sends the SMS notifications.

  • To allow sponsors to send SMS notifications to guests whose accounts they created, customize the sponsor portal and select all the appropriate SMS service providers that are available. If you do not select any SMS service providers for the Sponsor portal, the default global SMS service provider that is contracted by your company provides the SMS services.

SMS providers are configured as SMS Gateways in ISE. Email from ISE is converted to SMS by the SMS gateway. The SMS gateway can be behind a proxy server.

Configure SMS Gateways to Send SMS Notifications to Guests

You must set up SMS gateways in Cisco ISE to enable:

  • Sponsors to manually send SMS notifications to guests with their login credentials and password reset instructions.

  • Guests to automatically receive SMS notifications with their login credentials after they successfully register themselves.

  • Guests to automatically receive SMS notifications with actions to take before their guest accounts expire.

When entering information in the fields, you should update all text within [ ], such as [USERNAME], [PASSWORD], [PROVIDER_ID], etc., with information specific to your SMS provider's account.

Before you begin

Configure a default SMTP server to use for the SMS Email Gateway option.

Procedure

Step 1

Choose Administration > System > Settings > SMS Gateway.

Step 2

Click Add.

Step 3

Use the following tables to configure the SMS gateway:

Table 1. SMS Gateway Settings for SMS Email Gateway
Field Usage Guidelines

SMS Gateway Provider Domain

Enter the provider domain, which is used as the host portion and the guest account's mobile number as the user portion of the email address to send the message to the provider's SMS/MMS gateway.

Provider account address

(Optional)

Enter the account address, which is used as the FROM address (typically the account address) for the email and overrides the Default Email Address global setting in Guest Access > Settings.

SMTP API destination address

(Optional)

Enter the SMTP API Destination Address, if you are using an SMTP SMS API that requires a specific account recipient address, such as Clickatell SMTP API.

This is used as the TO address for the email and the guest account's mobile number is substituted into the message's body template.

SMTP API body template

(Optional)

Enter the SMTP API Body Template, if you are using an SMTP SMS API that requires a specific email body template for sending the SMS, such as Clicketell SMTP API.

The supported dynamic substitutions are $mobilenumber$, $timestamp$ (of format $YYYYMMDDHHHMISSmimi$), and $message$. You can use $timestamp$$mobilenumber$ for SMS gateways that require a unique idenitifier in the URL.

The navigation path for these settings is Guest Access > Settings > SMS Gateway.
Use these settings to configure sending SMS messages to guests and sponsors via an HTTP API (GET or POST method).

Table 2. SMS Gateway Settings for SMS HTTP API
Field Usage Guidelines

URL

Enter the URL for the API.

This field is not URL encoded. The guest account's mobile number is substituted into the URL. The supported dynamic substitutions are $mobilenumber$ and $message$.

If you are using HTTPS with the HTTP API, include HTTPS in the URL string and upload your provider's trusted certificates into Cisco ISE. Choose Administration > System > Certificates > Trusted Certificates.

Data (Url encoded portion)

Enter the Data (Url encoded portion) for the GET or POST request.

This field is URL encoded. If using the default GET method, the data is appended to the URL specified above.

Use HTTP POST method for data portion

If using the POST method, check this option.

The data specified above is used as the content of the POST request.

HTTP POST data content type

If using the POST method, specify the content type such as "plain/text" or "application/xml".

HTTPS Username

HTTPS Password

HTTPS Host name

HTTPS Port number

Enter this information.

Step 4

Check Break up long message into multiple parts to enable Cisco ISE to divide messages that exceed 140 bytes into multiple messages.

Most SMS providers divide long SMS messages into multiple parts automatically. MMS messages can be longer than SMS messages.
Step 5

Click Submit.


What to do next

If you configured a new SMS gateway, you can:

Social Login for Self-Registered Guests

Guests can select a social media provider as a way to provide credentials as a self-registered guest, instead of entering username and password in the guest portal. To enable this, you configure a social media site as an external identity source, and configure a portal that allows users to use that external identity (social media provider). Additional information about social media login for ISE can be found here: https://community.cisco.com/t5/security-documents/how-to-configure-amp-use-a-facebook-social-media-login-on-ise/ta-p/3609532

After authenticating with social media, guests can edit the information retrieved from the social media site. Even though social media credentials are used, the social media site does not know that the user has used that site's information to log in. ISE still uses the information retrieved from the Social Media site internally for future tracking.

You can configure the guest portal to prevent users from changing the information retrieved from the social media site, or even suppress display of the registration form.

Social Login Guest Flow

Login flow varies, depending on how you configure the Portal Settings. You can configure social media login without user registration, with user registration, or with user registration and sponsor approval.

  1. User connects to the self-registered portal, chooses to log in using social media. If you configured an access code, the user must also enter the access code on the login page.

  2. The user is redirected to the social media site for authentication. The user must approve use of their social media site's basic profile information.

  3. If the login to the social media site is successful, ISE retrieves additional information about the user from the social media site. ISE uses the social media information to log the user on.

  4. After login, the user may have to accept the AUP, depending on configuration.

  5. The next action in the login flow depends on the configuration:

    • Without registration—Registration is done behind the scenes. Facebook provides a token for the user's device to ISE for login.

    • With registration—The user is instructed to complete a registration form that has been prepopulated with information from the social media providers. This allows the user to correct and add missing information, and submit updated information for login. If you configured a registration code in the Registration Form Settings, then they also must enter the registration code.

    • With registration and sponsor approval—In addition to allowing the user to update the social media-provided information, the user is informed that they must wait for sponsor approval. The sponsor receives an email requesting approval or denial of the account. If the sponsor approves the account, ISE emails the user that they have access. The user connects the guest portal, and is automatically logged in with social media token.

  6. Registration is successful. The user is directed to the option configured in After submitting the guest form for self-registration, direct guest to on Registration Form Settings. The user's account is added to the endpoint identity group configured for the portal's guest type.

  7. The user has access until the guest account expires, or the user disconnects from the network.

    If the account expired, the only way to allow the user to log in is to reactivate the account, or to delete it. The user must go through the login flow again.

    If a user disconnects from the network, and reconnects, the action ISE takes depends on the authorization rules. If the user hits an authorization similar to:
    rule if guestendpoint then permit access
    
    and the user is still in the endpoint group, then the user is redirected to the logon page. If a user still has a valid token, they are automatically logged in. If not, then they must go through registration again.

    If the user is no longer in the endpoint group, then they are redirected to the guest page to go through registration.

Social Login Account Duration

Account re-authorization varies by connection method:

  • For 802.1x, the default authorization rule
    if guestendpoint then permit access
    
    enables a guest to reconnect if their device falls asleep, or if they roam to another building. When they reconnect, they are redirected back to guest page which either does auto login with a token, or starts registration again.
  • For MAB, every time the user reconnects, they are redirected to the guest portal, and have to click the social media again. If ISE still has a token for that user's account (guest account hasn't expired), then the flow goes to log in success immediately, without having to connect with the social media provider.

    To prevent every reconnect redirecting to another social login, you can configure an authorization rule that remembers the device, and permits access until the account expires. When the account expires, it is removed from the endpoint group, and the flow is redirected back to the rule for guest redirect. For example:

    if wireless_mab and guest endpoint then permit access
    
    if wireless_mab then redirect to self-registration social media portal
    

Reporting and User Tracking

ISE Live Logs and Facebook

  • Authentication Identity Store—This is the name of the application you created in your social media app for ISE.

  • Facebook username—This is the username reported by Facebook. If you allow the user to change their username during registration, the name reported by ISE is the social media username.

  • SocialMediaIdentifier—This is
    https://facebook.com/<number>
    
    where number identifies the social media user.

ISE Reports—The Guest username is the user's name on the social media site.

Facebook Analytics—You can see who is using your guest network through Facebook social logon by using analytics from Facebook.

Wireless and Facebook—The User Name on the Wireless controller is the unique Facebook ID, the same as the SocialMediaIdentifier on the Live Logs. To see the setting in the Wireless UI, navigate to Monitor > Clients > Detail, and look at the User Name field.

Block a Social Media-Authenticated Guest

You can create an authorization rule to block an individual social media user. This can be useful when using Facebook for authentication, when the token has not expired. The following example shows a Wi-Fi-connected guest user blocked by using their Facebook User Name.

For information about configuring Social Login for ISE, see Configuring Social Login.

Configuring Social Login

Before you begin

Configure the social media site so that ISE can connect to it. Only Facebook is supported currently.

Make sure the following HTTPS 443 URLs are open through your NADs so ISE can access Facebook:
facebook.co
akamaihd.net
akamai.co
fbcdn.net


Note

The social login URL for Facebook is HTTPS. Not all NADs support redirection to a HTTPS URL. See https://communities.cisco.com/thread/79494?start=0&tstart=0&mobileredirect=true.
Procedure

Step 1

On Facebook, create a Facebook application:

  1. Log on to https://developers.facebook.com and sign up as a developer.

  2. Select Apps in the header and select Add a New App.

Step 2

Add a new Product, Facebook Login, of type Web. Click Settings, and set:

  • Client OAuth Login: NO

  • Web OAuth Login: YES

  • Force Web OAuth Reauthentication: NO

  • Embedded Browser OAuth Login: NO

  • Valid OAuth redirect URIs: add the automated redirect URLs from the ISE

  • Login from Devices: NO

  1. Save

Step 3

Click App Review, and select Yes on Your app is currently live and available to the public.

Step 4

In ISE, navigate to Administration > Identity Management > External Identity Sources > Social Login, and click Add to create a new social login external identity source.

  • Type—Select the type of Social Login provider. Facebook is currently the only option.

  • App ID—Enter the App ID from the Facebook application.

  • App Secret—Enter the App Secret from the Facebook application.

Step 5

In ISE, enable Social Media Login in a self-registered portal. On the portal page, navigate to Portal & Page Settings > Login Page Settings, check Allow Social Login, which causes more settings to display:

  • Show registration form after social login—This allows the user to change the information provided by Facebook.

  • Require guests to be approved—This informs the user that a sponsor must approve their account, and will send them credentials for login.

Step 6

Navigate to Administration > External Identity Sources, select the Facebook Login page, and edit your Facebook external identity source.

This creates redirect URIs, which you add to to the Facebook application.
Step 7

In Facebook, add the URIs from the previous step to your Facebook application.


What to do next

In Facebook, you can display data about your app, which shows the guest activity with the Facebook Social Login.

Guest Portals

When people visiting your company wish to use your company’s network to access the internet, or resources and services on your network, you can provide them network access through a Guest portal. Employees can use these Guest portals to access your company’s network, if configured.

There are three default Guest portals:

  • Hotspot Guest portal—Network access is granted without requiring any credentials. Usually, an Acceptance of User Policy (AUP) must be accepted before network access is granted.

  • Sponsored-Guest portal—Network access is granted by a sponsor who creates accounts for guests, and provides the Guest with login credentials.

  • Self-Registered Guest portal—Guests can create their own accounts credentials, and may need sponsor approval before they are granted network access.

Cisco ISE can host multiple Guest portals, including a predefined set of default portals.

The default portal themes have standard Cisco branding that you can customize through the Admin portal.

Wireless setup has its own default theme (CSS) and you are able to modify some basic settings such as logo, banner, background image, coloring and fonts. In ISE, you can also choose to further customize your portal by changing more settings and go into advanced customizations.

Credentials for Guest Portals

Cisco ISE provides secured network access by requiring guests to log in using various types of credentials. You can require that guests log in using one or a combination of these credentials.

  • Username—Required. Applies to all guests using end-user portals (except Hotspot Guest portals) and is derived from the username policy. The username policy applies only to system-generated usernames and not to usernames specified using the Guest API programming interface or the self-registering process. You can configure the policy settings that apply to usernames at Work Centers > Guest Access > Settings > Guest Username Policy. Guests can be notified of their username in an email, SMS, or in printed form.

  • Password—Required. Applies to all guests using end-user portals (except Hotspot Guest portals) and is derived from the password policy. You can configure the policy settings that apply to passwords at Work Centers > Guest Access > Settings > Guest Password Policy. Guests can be notified of their password in an email, SMS, or in printed form.

  • Access code—Optional. Applies to guests using the Hotspot Guest and Credentialed Guest portals. An access code is primarily a locally known code that is given to physically present guests (either visually via a whiteboard or verbally by a lobby ambassador). It would not be known and used by someone outside the premises to gain access to the network. If the Access code setting is enabled:

    • Sponsored guests are prompted to enter it on the Login page (along with a username and password).

    • Guests using the Hotspot Guest portal are prompted to enter it on the Acceptable Use Policy (AUP) page.

  • Registration code—Optional. Applies to self-registering guests and is similar to an access code in how it is provided to the self-registering guests. If the Registration code setting is enabled, self-registering guests are prompted to enter it on the Self-Registration form.

The username and password can be provided by a sponsor at your company (for sponsored guests), or a Credentialed Guest portal can be configured to allow guests to register themselves to obtain these credentials.

Guest Access with Hotspot Guest Portals

Cisco ISE provides network access functionality that includes “hotspots,” which are access points that guests can use to access the Internet without requiring credentials to log in. When guests connect to the hotspot network with a computer or any device with a web browser and attempt to connect to a website, they are automatically redirected to a Hotspot Guest portal. Both wired and wireless (Wi-Fi) connections are supported with this functionality.

The Hotspot Guest portal is an alternative Guest portal that allows you to provide network access without requiring guests to have usernames and passwords and alleviates the need to manage guest accounts. Instead, Cisco ISE works together with the network access device (NAD) and Device Registration Web Authentication (Device Registration WebAuth) to grant network access directly to the guest devices. Sometimes, guests may be required to log in with an access code. Typically, this is a code that is locally provided to guests who are physically present on a company’s premises.

If you support the Hotspot Guest portal:

  • Based on the Hotspot Guest portal configuration and settings, guests are granted access to the network if the guest access conditions are met.

  • Cisco ISE provides you with a default guest identity group, GuestEndpoints, which enables you to cohesively track guest devices.

Guest Access with Credentialed Guest Portals

You can use a credentialed Guest portal to identify and authorize temporary access for external users to internal networks and services, as well as to the Internet. Sponsors can create temporary usernames and passwords for authorized visitors who can access the network by entering these credentials in the portal's Login page.

You can set up a credentialed Guest portal so that guests can log in using a username and password that is obtained:

  • From a sponsor. In this guest flow, guests are greeted by a sponsor, such as a lobby ambassador, when they enter company premises and are set up with individual guest accounts.

  • After they register themselves, using an optional registration code or access code. In this guest flow, guests are able to access the Internet without any human interaction and Cisco ISE ensures that these guests have unique identifiers that can be used for compliance.

  • After they register themselves, using an optional registration code or access code, but only after the request for a guest account is approved by a sponsor. In this guest flow, guests are provided access to the network, but only after an additional level of screening is done.

You can also force the user to enter a new password when logging in.

Cisco ISE enables you to create multiple credentialed Guest portals, which you can use to allow guest access based on different criteria. For example, you might have a portal for monthly contractors that is separate from the portal used for daily visitors.

Employee Access with Credentialed Guest Portals

Employees can also access the network using Credentialed Guest Portals by signing in using their employee credentials, as long as their credentials can be accessed by the identity source sequence configured for that portal.

Guest Device Compliance

When guests and non-guests access the network through credentialed Guest portals, you can check their devices for compliance before they are allowed to gain access. You can route them to a Client Provisioning page and require them to first download the posture agent that checks their posture profile and verifies if their device is compliant. You can do this by enabling the option in the Guest Device Compliance Settings in a credentialed Guest portal, which displays the Client Provisioning page as part of the guest flow.

The Client Provisioning service provides posture assessments and remediations for guests. The Client Provisioning portal is available only with a Central Web Authorization (CWA) guest deployment. The guest login flow performs a CWA, and the credentialed Guest portal is redirected to the Client Provisioning portal after performing acceptable-use-policy and change-password checks. The posture subsystem performs a Change of Authorization (CoA) on the network access device to reauthenticate the client connection once the posture has been assessed.

Guest Portals Configuration Tasks

You can use a default portal and its default settings such as certificates, endpoint identity group, identity source sequence, portal themes, images, and other details provided by Cisco ISE. If you do not want to use the default settings, you should create a new portal or edit an existing one to meet your needs. You can duplicate a portal if you want to create multiple portals with the same settings.

After creating a new portal or editing a default one, you must authorize the portal for use. Once you authorize a portal for use, any subsequent configuration changes you make are effective immediately.

If you choose to delete a portal, you must first delete any authorization policy rules and authorization profiles associated with it or modify them to use another portal.

Use this table for the tasks related to configuring the different Guest portals.

Task Hotspot Guest Portal Sponsored-Guest Portal Self-Registered Guest Portal

Enable Policy Services

Required

Required

Required

Add Certificates for Guest Portals

Required

Required

Required

Create External Identity Sources

Not applicable

Required

Required

Create Identity Source Sequences

Not applicable

Required

Required

Create Endpoint Identity Groups

Create Endpoint Identity Groups (see the Create Endpoint Identity Groups section in )

Required

Not required (defined by guest type)

Not required (defined by guest type)

Create a Hotspot Guest Portal

Required

Not applicable

Not applicable

Create a Sponsored-Guest Portal

Not applicable

Required

Not applicable

Create a Self-Registered Guest Portal

Not applicable

Not applicable

Required

Authorize Portals

Required

Required

Required

Customize Guest Portals

Optional

Optional

Optional

Enable Policy Services

To support the Cisco ISE end-user web portals, you must enable portal-policy services on the node on which you want to host them.

Procedure

Step 1

Choose Administration > System > Deployment

Step 2

Click the node and click Edit.

Step 3

On the General Settings tab, check Policy Service.

Step 4

Check the Enable Session Services option.

Step 5

Click Save.


Add Certificates for Guest Portals

If you do not want to use the default certificates, you can add a valid certificate and assign it to a certificate group tag. The default certificate group tag used for all end-user web portals is Default Portal Certificate Group.

Procedure

Step 1

Chose Administration > System > Certificates > System Certificates.

Step 2

Add a system certificate and assign it to a certificate group tag that you want to use for the portal.

This certificate group tag will be available to select during portal creation or editing.
Step 3

Choose Work Centers > Guest Access > Portals & Components > Guest Portals > Create or Edit > Portal Settings.

Step 4

Select the specific certificate group tag from the Certificate group tag drop-down list that is associated with the newly added certificate.


Create External Identity Sources

Cisco ISE can connect with external identity sources such as Active Directory, LDAP, RADIUS Token, and RSA SecurID servers to obtain user information for authentication and authorization. External identity sources also include certificate authentication profiles that you need for certificate-based authentications.


Note

To work with passive identity services, which enable you to receive and share authenticated user identities, see Additional Passive Identity Service Providers.


Procedure

Step 1

Choose Administration > Identity Management > External Identity Sources.

Step 2

Choose one of these options:


Configure Guest Portals to Redirect to SAML IDP Portals for Authentication

You can configure a Guest portal to allow users to be redirected to a SAML IDP portal for authentication.

Configuring the setting Allow the following identity-provider guest portal to be used for login in a guest portal (self-registered or Sponsored Guest) enables a new login area in that portal. If a user selects that login option, they are redirected to the alternate identity portal (which they don't see), and then to the SAML IDP logon portal for authentication.

For example, the Guest portal could have a link for employee login. Instead of logging in on the existing portal, the user clicks the employee logon link, and is redirected to the SAML IDP single-signon portal. The employee is either reconnected using the token from the last logon with this SAML IDP, or logs in on that SAML site. That allows the same portal to handle both guests and employees from a single SSID.

The following steps show how to configure a Guest portal that calls another portal which is configured to use a SAML IDP for authentication.

Procedure

Step 1

Configure an external identity source. See SAMLv2 Identity Provider as an External Identity Source for more details.

Step 2

Create a guest portal for the SAML provider. Set the Authentication method in Portal Settings to the SAML provider. The user will not see this portal, it is just a placeholder to direct the user to the SAML IDP logon page. Other portals can be configured to redirect to this sub-portal, as described next.

Step 3

Create a guest portal with the option to redirect to the guest portal for the SAML provider portal that you just created. This is the main portal, which will redirect to the sub-portal.

You may want to customize the look of this portal to make it look like the SAML provider.

  1. On the Login Page Settings page of the main portal, check Allow the following identity-provider guest portal to be used for login.

  2. Select the guest portal that you configured to use with the SAML provider.


Create Identity Source Sequences

Before you begin

Ensure that you have configured your external identity sources in Cisco ISE.

To perform the following task, you must be a Super Admin or System Admin.

For allowing guest users to authenticate through Local WebAuth, you must configure both the Guest Portal authentication source and the identity source sequence to contain the same identity stores.

Procedure

Step 1

Choose Administration > Identity Management > Identity Source Sequences > Add.

Step 2

Enter a name for the identity source sequence. You can also enter an optional description.

Step 3

Check the Select Certificate Authentication Profile check box and choose a certificate authentication profile for certificate-based authentication.

Step 4

Choose the database or databases that you want to include in the identity source sequence in the Selected List box.

Step 5

Rearrange the databases in the Selected list in the order in which you want Cisco ISE to search the databases.

Step 6

Choose one of the following options in the Advanced Search List area:

  • Do not access other stores in the sequence and set the AuthenticationStatus attribute to ProcessError —If you want Cisco ISE to discontinue the search, if the user is not found in the first selected identity source.

  • Treat as if the user was not found and proceed to the next store in the sequence —If you want Cisco ISE to continue searching the other selected identity sources in sequence, if the user is not found in the first selected identity source.

    While processing a request, Cisco ISE searches these identity sources in sequence. Ensure that you have the identity sources in the Selected list box listed in the order in which you want Cisco ISE to search them.

Step 7

Click Submit to create the identity source sequence that you can then use in policies.


Create Endpoint Identity Groups

Cisco ISE groups endpoints that it discovers in to the corresponding endpoint identity groups. Cisco ISE comes with several system-defined endpoint identity groups. You can also create additional endpoint identity groups from the Endpoint Identity Groups page. You can edit or delete the endpoint identity groups that you have created. You can only edit the description of the system-defined endpoint identity groups; you cannot edit the name of these groups or delete them.

Procedure

Step 1

Choose Administration > Identity Management > Groups > Endpoint Identity Groups.

Step 2

Click Add.

Step 3

Enter the name for the endpoint identity group that you want to create (do not include spaces in the name of the endpoint identity group).

Step 4

Enter the description for the endpoint identity group that you want to create.

Step 5

Click the Parent Group drop-down list to choose an endpoint identity group to which you want to associate the newly created endpoint identity group.

Step 6

Click Submit.


Create a Hotspot Guest Portal

You can provide a Hotspot Guest portal to enable guests to connect to your network without requiring a username and password to log in. An access code can be required to log in.

You can create a new Hotspot Guest portal, or you can edit or duplicate an existing one. You can delete any Hotspot Guest portal, including the default portal provided by Cisco ISE.

Any changes that you make to the Page Settings on the Portal Behavior and Flow Settings tab are reflected in the graphical flow in the Guest Flow diagram. If you enable a page, such as the AUP page, it appears in the flow and the guest will experience it in the portal. If you disable it, it is removed from the flow and the next enabled page displays for the guest.

All the Page Settings, except the Authentication Success Settings, are optional.

Before you begin
  • Ensure that you have the required certificates and endpoint identity groups configured for use with this portal.

  • Ensure that the WLC that guests connect to for the Hotspot portal is supported by ISE. See the Identity Services Engine Network Component Compatibility guide for your version of ISE .

Procedure

Step 1

Choose Work Centers > Guest Access > Portals & Components > Guest Portals > Create, Edit or Duplicate.

Step 2

If creating a new portal, in the Create Guest Portal dialog box, select Hotspot Guest Portal as the portal type and click Continue.

Step 3

Provide a unique Portal Name and a Description for the portal.

Ensure that the portal name that you use here is not used for any other end-user portals.
Step 4

Use the Language File drop-down menu to export and import language files to use with the portal.

Step 5

Update the default values for ports, Ethernet interfaces, certificate group tags, endpoint identity groups, and so on in Portal Settings, and define behavior that applies to the overall portal.

Step 6

Update the following settings, which apply to each of the specific pages:

  • Acceptable Use Policy (AUP) Page Settings—Require guests to accept an acceptable use policy.
  • Post-Access Banner Page Settings—Inform guests of their access status and any other additional actions, if required.
  • VLAN DHCP Release Page Settings—Release the guest device IP address from the guest VLAN and renew it to access another VLAN on the network.
  • Authentication Success Settings—Specify what guests should see once they are authenticated.
  • Support Information Page Settings—Help guests provide information that the Help Desk can use to troubleshoot network access issues.
Step 7

Click Save. A system-generated URL displays as the Portal test URL, which you can use to access the portal and test it.


What to do next

You must authorize the portal in order to use it. You can also customize your portal either before or after you authorize it for use.

Create a Sponsored-Guest Portal

You can provide a Sponsored-Guest portal to enable designated sponsors to grant access to guests.

You can create a new Sponsored-Guest portal, or you can edit or duplicate an existing one. You can delete any Sponsored-Guest portal, including the default portal provided by Cisco ISE.

Any changes that you make to the Page Settings on the Portal Behavior and Flow Settings tab are reflected in the graphical flow in the Guest Flow diagram. If you enable a page, such as the AUP page, it appears in the flow and the guest will experience it in the portal. If you disable it, it is removed from the flow and the next enabled page displays for the guest.

All these page settings enable you to display an Acceptable Use Policy (AUP) for a guest and require its acceptance:

  • Login Page Settings

  • Acceptable Use Policy (AUP) Page Settings

  • BYOD Settings

Before you begin

Ensure that you have the required certificates, external identity sources, and identity source sequences configured for use with this portal.

Procedure

Step 1

Choose Work Centers > Guest Access > Portals & Components > Guest Portals > Create, Edit or Duplicate.

Step 2

If creating a new portal, in the Create Guest Portal dialog box, select Sponsored-Guest Portal as the portal type and click Continue.

Step 3

Provide a unique Portal Name and a Description for the portal.

Ensure that the portal name that you use here is not used for any other end-user portals.
Step 4

Use the Language File drop-down menu to export and import language files to use with the portal.

Step 5

Update the default values for ports, Ethernet interfaces, certificate group tags, identity source sequences, authentication method, and so on in Portal Settings, and define behavior that applies to the overall portal.

Step 6

Update the following settings, which apply to each of the specific pages:

  • Login Page Settings—Specify guest credential and login guidelines. If you select the Allow guests to create their accounts option, users will be able to create their own guest accounts. If this option is not selected, sponsors will be required to create guest accounts.
    Note 

    Login Page Settings option will be disabled if you have selected an identity provider (IdP) in the Authentication Method field.

  • Acceptable Use Policy (AUP) Page Settings—Add a separate AUP page and define the acceptable use policy behavior for guests, including employees who use the credentialed Guest portals.
  • Employee Change Password Settings—Require guests to change their password after the first time they log in.
  • Guest Device Registration Settings—Select whether Cisco ISE automatically registers guest devices or displays a page where guests can manually register their devices.
  • BYOD Settings—Let employees use their personal devices to access the network.
  • Post-Login Banner Page Settings—Notify guests of additional information before they are granted network access.
  • Guest Device Compliance Settings—Route guests to the Client Provisioning page and require them to first download the posture agent.
  • VLAN DHCP Release Page Settings—Release the guest device IP address from the guest VLAN and renew it to access another VLAN on the network.
  • Authentication Success Settings—Specify what guests should see once they are authenticated.
  • Support Information Page Settings—Help guests provide information that the Help Desk can use to troubleshoot network access issues.
Step 7

Click Save. A system-generated URL displays as the Portal test URL, which you can use to access the portal and test it.


What to do next

Note

The test portal does not support RADIUS sessions, so you won't see the entire portal flow for all portals. BYOD and Client Provisioning are examples of portals that depend on RADIUS sessions. For example, a redirect to an external URL will not work.

You must authorize the portal in order to use it. You can also customize your portal either before or after you authorize it for use.

Create a Self-Registered Guest Portal

You can provide a Self-Registered Guest portal to enable guests to register themselves and create their own accounts so they can access the network. You can still require that these accounts be approved by a sponsor before access is granted.

You can create a new Self-Registered Guest portal, or you can edit or duplicate an existing one. You can delete any Self-Registered Guest portal, including the default portal provided by Cisco ISE.

Any changes that you make to the Page Settings on the Portal Behavior and Flow Settings tab are reflected in the graphical flow in the Guest Flow diagram. If you enable a page, such as the AUP page, it appears in the flow and the guest will experience it in the portal. If you disable it, it is removed from the flow and the next enabled page displays for the guest.

All these page settings enable you to display an Acceptable Use Policy (AUP) for a guest and require its acceptance:

  • Login Page Settings

  • Self-Registration Page Settings

  • Self-Registration Success Page Settings

  • Acceptable Use Policy (AUP) Page Settings

  • BYOD Settings

Before you begin

Ensure that you have configured the required certificates, external identity sources, and identity source sequences for this portal.

Procedure

Step 1

Choose Work Centers > Guest Access > Portals & Components > Guest Portals > Create, Edit or Duplicate..

Step 2

If creating a new portal, in the Create Guest Portal dialog box, select Self-Registered Guest Portal as the portal type and click Continue.

Step 3

Provide a unique Portal Name and a Description for the portal.

Ensure that the portal name that you use here is not used for any other end-user portals.
Step 4

Use the Language File drop-down menu to export and import language files to use with the portal.

Step 5

In Portal Settings, update the default values for ports, Ethernet interfaces, certificate group tags, identity source sequences, authentication method,, and other settings that define behavior of this portal.

For more information about Portal Settings fields, see Portal Settings for Credentialed Guest Portals.
Step 6

Update the following settings, which apply to each of the specific pages:

  • Login Page Settings—Specify guest credential and login guidelines. For more information, see Login Page Settings for Credentialed Guest Portals.
  • Self-Registration Page Settings—Specify the information self-registering guests will read and should enter on the Self-Registration form, in addition to the guest experience after they have submitted the form.
  • Acceptable Use Policy (AUP) Page Settings—Add a separate AUP page and define the acceptable use policy behavior for guests, including employees who use the credentialed Guest portals. For more information, see Acceptable Use Policy (AUP) Page Settings for Credentialed Guest Portals.
  • Employee Change Password Settings—Require guests to change their password after the first time they log in.
  • Guest Device Registration Settings—Select whether Cisco ISE automatically registers guest devices or displays a page where guests can manually register their devices.
  • BYOD Settings—Let employees use their personal devices to access the network. For more information, see BYOD Settings for Credentialed Guest Portals. For more information, see BYOD Settings for Credentialed Guest Portals.
  • Post-Login Banner Page Settings—Display additional information after the user successfully logs in, and before they are granted network access.
  • Guest Device Compliance Settings—Redirects guests to the Client Provisioning page for posture assessment. For more information, see Guest Device Compliance Settings for Credentialed Guest Portals.
  • VLAN DHCP Release Page Settings—Release the guest device IP address from the guest VLAN and renew it to access another VLAN on the network. For more information, see BYOD Settings for Credentialed Guest Portals.
  • Authentication Success Settings—Specify where to direct guests after they are authenticated. If you redirect a Guest to an external URL after authentication, there may be a delay while the URL address is resolved and the session is redirected. For more information, see Authentication Success Settings for Guest Portals.
  • Support Information Page Settings—Help guests provide information that the Help Desk can use to troubleshoot network access issues.
Step 7

Click Save. A system-generated URL displays as the Portal test URL, which you can use to access the portal and test it.


What to do next

Note

The test portal does not support RADIUS sessions, so you won't see the entire portal flow for all portals. BYOD and Client Provisioning are examples of portals that depend on RADIUS sessions. For example, a redirect to an external URL will not work.

You must authorize the portal in order to use it. You can also customize your portal either before or after you authorize it for use.

Self-Registered Account Approval by a Sponsor

When you configure a registered guest to require approval of their account, ISE sends an email to the approver to approve the account. The approver can either be the person being visited, or a sponsor user.

When the approver is a sponsor, you can configure the email to include links that deny or approve the account. The approval link contains a token, which ties the approval to the sponsor's email address. You can require the sponsor to authenticate, which ignores the token. The token can also time out, which requires the sponsor to authenticate before approving the account.

You configure account approval options on the Self-Registration Portal's Registration Form Settings. This feature is also referred to as single-click sponsor approval.

When the sponsor opens the email, and clicks the approve link, the action varies depending on configuration of the approver.

If Email approval request to is confiurged as:

  • person being visited

    • And the guest account does not require authentication: a single click approves the account.

    • And the guest account does require authentication: the sponsor is directed to a special page on the sponsor portal, where the sponsor must enter their credentials before they can approve the account.

  • Sponsor email addresses listed below: Cisco ISE sends emails to all the provided email addresses. When one of those sponsors clicks the approve or deny link, they are directed to their sponsor portal. That sponsor enters their credentials, and are verified. If the sponsor group that they belong to allows them to approve the guest account, they can approve the account. If credentials fail, then Cisco ISE tells the sponsor to log on to the sponsor portal, and approve the account manually.

Considerations
  • If your are upgrading or restoring the database from previous version of Cisco ISE, you must manually insert approve or deny links. After you have configured the self-registration portal to require guests to be approved:

    Open the Self-Registered guest portal and choose the Portal Page Customization tab. Scroll down and choose the Approval Request Email page. Click Insert Approve/Deny Links in the Email Body parts of that page.

  • Only Sponsor portals that authenticate with Active Directory and LDAP are supported. This means that the sponsor must be an Active Directory or LDAP user.

  • The sponsor group that the sponsor maps to must contain the Active Directory group that the sponsor belongs to.

  • If you chose person being visited, the contents of that field, which the self-registering guest provides, must be the email address of a sponsor. We recommend that you customize that Self-Registered portal to change that field name to "email address of the Sponsor", or something similar. You could create a new field to capture who the guest is visiting, if necessary. When the user clicks the Register button, Cisco ISE verifies that the person being visited is a valid sponsor, and has an email address. If Cisco ISE can't find an email address for that sponsor in the identity source, then ISE displays an error message, and self-registration fails.

  • When a list of sponsors is configured, the customization from the first portal is used, even if that is not the portal that the sponsor logs on to.

  • The sponsor must use an HTM-capable email client to use the approve and deny links .

  • If the email address for the sponsor is not for a valid sponsor, the approval email is not sent.

For more information about single-click sponsor approval, see the Cisco ISE Community posting ISE Single Click Sponsor Approval FAQ. The Community document also has a link to a video that steps through the entire process. If the video does not run, please try another browser.

Configuring Account Approval Email Links
You can require that a self-registered guest is approved before gaining access to the network. Cisco ISE uses the email address of the person being visited to notify the approver. The approver is either the person being visitited, or a sponsor. For more information about approval, see Self-Registered Account Approval by a Sponsor.
Procedure

Step 1

Navigate to Work Centers > Guest > Configure > Guest Portals, and select the self-registered portal that you want to configure for email account approval links.

Step 2

Expand the Self-Registration Page Settings tab.

Step 3

3. Check Require self-registered guests to be approved. This causes the Approve/Deny Link Settings section to appear at the bottom of the tab area. It also populates the email configuration of the Approval Request Email with approve and deny links.

All the possible fields that appear when you select Self-Registration Page Settings follow.

  • Require self-registered guests to be approved—Specify that the self-registering guests using this portal require approval from a sponsor before receiving their guest credentials. Clicking this option displays more options for how sponsors approve a self-registered guest.

    • Allow guests to login automatically from self-registration after sponsor's approval: A self-registered guest will be logged in automatically after sponsor approval.

    • Email approval request to—If you select:

      • sponsor email addresses listed below, enter one or more email addresses of sponsors designated as approvers, or a mailer, to which ALL guest approval requests should be sent. If the email address is not valid, approval fails.

      • person being visited, then the field Require sponsor to provide credentials for authentication is displayed, and the Required option in Fields to include is enabled (if it was previously disabled). These fields are displayed on the Self-Registration form requesting this information from the self-registering guests. If the email address is not valid, approval fails.

    • Approve/Deny Link Settings—This section allows you to configure:

      • Links are valid for—You can set an expiration period for the account approval links.

      • Require sponsor to provide credentials for authentication—Check this to force the sponsor to enter credentials to approve the account, even if it is not required by the configuration in this section. This field is only visible if Require self-registered guests to be approved is set to person being visited.

      • Sponsor is matched to a Sponsor Portal to verify approval privileges—Click Details > to select the portals that are searched to verify that the sponsor is a valid system user, a member of a sponsor group, and that the members of that group have authority to approve the account. Each sponsor portal has an identity source sequence, which is used to identify the sponsor. Portals are used in the order they are listed. The first portal in the list determines the style and customization used in the sponsor portal.


Authorize Portals

When you authorize a portal, you are setting up the network authorization profiles and rules for network access.
Before you begin

You must create a portal before you can authorize it.

Procedure

Step 1

Set up a special authorization profile for the portal.

Step 2

Create an authorization policy rule for the profile.


Create Authorization Profiles

Each portal requires that you set up a special authorization profile for it.

Before you begin

If you do not plan to use a default portal, you must first create the portal so you can associate the portal name with the authorization profile.

Procedure

Step 1

Choose Policy > Policy Elements > Results > Authorization > Authorization Profiles.

Step 2

Create an authorization profile using the name of the portal that you want to authorize for use.


What to do next

You should create a portal authorization policy rule that uses the newly created authorization profile.

Create Authorization Policy Rules for Hotspot and MDM Portals

To configure the redirection URL for a portal to use when responding to the users' (guests, sponsors, employees) access requests, define an authorization policy rule for that portal.

The url-redirect takes the following form based on the portal type, where:

ip:port = the IP address and port number

PortalID = the unique portal name

For a Hotspot Guest portal: https://ip:port/guestportal/gateway?sessionID=SessionIdValue&portal=PortalID&action=cwa&type=drw

For a Mobile Device Management (MDM) portal: https://ip:port/mdmportal/gateway?sessionID=SessionIdValue&portal=PortalID&action=mdm

Procedure

Step 1

Choose Policy > Policy Sets to create a new authorization policy rule under Standard policies.

Step 2

For Conditions, select an endpoint identity group that you want to use for the portal validation. For example, for the Hotspot Guest portal, select the default GuestEndpoints endpoint identity group and, for the MDM portal, select the default RegisteredDevices endpoint identity group.

Note 
Because the Hotspot Guest portal only issues a Termination CoA, do not use Network Access:UseCase EQUALS Guest Flow as one of the validation conditions in the Guest authorization policy. Instead, match the Identity Group that the endpoint belongs to for validation. For example,
  • If "GuestEndpoint" + Wireless MAB then Permit Access

  • If Wireless MAB then HotSpot Redirect

Step 3

For Permissions, select the portal authorization profile that you created.


Customize Guest Portals

You can customize the portal appearance and user (guests, sponsors, or employees as applicable) experience by customizing the portal themes, changing UI elements on the portal pages, and editing error messages and notifications that display to the users. For more information about customizing portals, see Customization of End-User Web Portals.

Configure Periodic AUP Acceptance

Procedure


Browse to Policy > Policy Sets, and create a new authorization rule at the top of the list that redirects the Guest user to a credentialed portal when the AUP period has expired. Use conditions to compare LastAUPAcceptanceHours against the desired maximum hours, for example, LastAUPAcceptanceHours > 8 . You can check for a range of hours from 1 to 999.


What to do next

To verify that the endpoint has received the AUP settings:

  1. Choose Administration > Identities > Endpoints.

  2. Click an endpoint to verify that the endpoint has the time that the AUP was last accepted (AUPAcceptedTime).

Forcing Periodic AUP

You can force a user to accept the AUP by using LastAUPAcceptance in a policy.

If LastAUPAcceptance >= 24: Hotspot Redirect
If LastAUPacceptance < 24: PermitAccess
If Wireless_MAB: Hotspot Redirect

This example shows how to force AUP on a hotspot portal every 24 hours.

  1. If the user accepted AUP more than 24 hours ago, then the must accept AUP (start over).

  2. If the user accepted AUP less than 24 hours ago, continue the session.

  3. On the first access to the network (MAB), they must accept AUP.

The same rules can be used with a credentialed portal, as long as you enable AUP for that portal.

Guest Remember Me

"Remember me" means that ISE shows a guest's username instead of MAC address in reports and logs.

When a guest first authenticates, the MAC address of their device is save in the endpoint group, and the username is used in reports. If the user disconnects, and then reconnects to the network, the MAC address is already in the endpoint group, so the user does not have to log back in again (authenticate). In this case, the username is not available, so the MAC address is used in reporting and logs.

Starting with ISE 2.3, ISE keeps the portal user ID, and uses it in some reporting, depending on the release.

  • ISE 2.3 implemented this feature, but you can't turn it off.

  • ISE 2.4 added the ability to turn off this feature in Guest > Settings > Logging. It is turned on by default on new installations, and disabled for upgrades and restores of previous releases.

For more information about Remember Me logging issues, see the following ISE community posting: ISE 2.3+ Remember Me guest using guest endpoint group logging display.

For more information about configuring remember me, see the ISE Guest Access Deployment guide: https://communities.cisco.com/docs/DOC-77590

For more information about which reporting methods are supported in each release, see the release notes for that release.

Sponsor Portals

The Sponsor portal is one of the primary components of Cisco ISE guest services. Using the Sponsor portal, sponsors can create and manage temporary accounts for authorized visitors to securely access the corporate network or the Internet. After creating a guest account, sponsors also can use the Sponsor portal to provide account details to the guest by printing, emailing, or texting. Before providing self-registering guests access to the company network, sponsors may be requested via email to approve their guests’ accounts.

Managing Guest Accounts on the Sponsor Portal

Sponsor Portal Log on Flow

A sponsor group specifies a set of permissions that are assigned to a sponsor user. When a sponsor logs in to a sponsor portal:

  1. ISE verifies the sponsor’s credentials.

  2. If the sponsor authenticates successfully, ISE searches all the available sponsor groups to find the sponsor groups that the sponsor belongs to. A sponsor matches or belongs to a sponsor group if both:

    • The sponsor is a member of one of the configured Member Groups.

    • If you are using Other Conditions, all the conditions evaluate to true for that sponsor.

  3. If the sponsor belongs to a sponsor group, then that sponsor gets the permissions from that group. A sponsor can belong to more than one sponsor group, in which case the permissions from those groups are combined. If the sponsor does not belong to any sponsor group, then the login to the sponsor portal fails.

Sponsor groups and their permissions are independent of the sponsor portals. The same algorithm for matching sponsor groups is used, regardless of which sponsor portal the sponsor logs in to.

Using a Sponsor Portal

Use a Sponsor portal to create temporary guest accounts for authorized visitors to securely access your corporate network or the Internet. After creating guest accounts, you can use a Sponsor portal to manage these accounts and to provide account details to the guests.

On a Sponsor portal, the sponsor can create new guest accounts individually, or import a group of users from a file.


Note

An ISE administrator authorized from an external identity store, such as Active Directory, can be part of a Sponsor group. However, internal administrator accounts, for example, the default "admin" account, cannot be part of a Sponsor group.

There are several ways to open a Sponsor portal:

  • In the Administrators console, on the Sponsor Portal configuration page. Click Guest Access > Portals & Components > Sponsor Portals, open a sponsor portal, and click the Portal Test URLlink to the right of the Description field.

  • In a browser, by opening the URL (FQDN) configured in the sponsor portal's Portal Settings page, which must be defined in your DNS server.

What to do Next

For information abouit how to use the Sponsor portal, see the Sponsor Portal User Guide for your version of ISE https://www.cisco.com/c/en/us/support/security/identity-services-engine/products-installation-guides-list.html.

Managing Sponsor Accounts

A sponsor user is an employee or contractor of your organization who creates and manages guest-user accounts through the sponsor portal. Cisco ISE authenticates sponsors through a local database, or through external Lightweight Directory Access Protocol (LDAP), Microsoft Active Directory, or SAML identity stores. If you are not using an external source, you must create internal user accounts for sponsors.

Sponsor Groups

Sponsor groups control the permissions given to a sponsor when using any Sponsor portal. If a sponsor is a member of a sponsor group, then the sponsor receives the permissions defined in the group.

A sponsor is considered to be a member of a sponsor group if both of the following are true:

  1. The sponsor belongs to at least one of the Member Groups defined in the sponsor group. A Member Group can be a User Identity Group, or a group selected from an external identity source, such as Active Directory.

  2. The sponsor satisfies all of the Other Conditions specified in the sponsor group. The Other Conditions, which are optional, are conditions defined on dictionary attributes. These conditions are similar in behavior to those used in an Authorization Policy.

A sponsor can be a member of more than one sponsor group. If so, the sponsor receives the combined permissions from all of those groups, as follows:

  • An individual permission such as "Delete guests' accounts" is granted if it is enabled in any of the groups.

  • The sponsor can create guests using the Guest Types in any of the groups.

  • The sponsor can create guests at the locations in any of the groups.

  • For a numeric value such as a batch size limit, the largest value from the groups is used.

If a sponsor is not a member of any sponsor group, then the sponsor is not permitted to log in to any sponsor portal.

  • ALL_ACCOUNTS—Sponsors can manage all guest accounts.

  • GROUP_ACCOUNTS—Sponsors can manage the guest accounts created by sponsors from the same Sponsor Group.

  • OWN_ACCOUNTS—Sponsors can manage only the Guest accounts that they created.

You can customize the features available to particular sponsor groups to limit or expand the functionality of the Sponsor portal. For example:

Create Sponsor Accounts and Assign to Sponsor Groups

To create internal sponsor user accounts and specify the sponsors who can use the Sponsor portals:

Procedure

Step 1

Choose Administration > Identity Management > Identities > Users. Assign the internal sponsor user account to the appropriate user identity group.

Note 

The default Sponsor Groups have the default Identity Group Guest_Portal_Sequence assigned to them.

Step 2

ChooseWork Centers > Guest Access > Portals & Components > Sponsor Groups > Create, Edit or Duplicate and click Members. Map the sponsor user identity groups to sponsor groups.


What to do next

You can also create additional user identity groups specific to your organization to use with sponsors. Choose Administration > Identity Management > Groups > User Identity Groups.

Configure Sponsor Groups

Cisco provides default sponsor groups. If you do not want to use the default options, you can either create new sponsor groups or edit the default sponsor groups and change the settings. You can also duplicate a sponsor group to create more sponsor groups with the same settings and privileges.

You can disable a sponsor group, which prevents the members of the sponsor group from logging in to the Sponsor portal. You can delete any of the sponsor groups, except the default sponsor groups provided by Cisco ISE.

Procedure

Step 1

ChooseWork Centers > Guest Access > Portals and Components > Sponsor Groups > Create, Edit or Duplicate

Step 2

Enter the Sponsor group name and Description.

Step 3

Match Criteria-The settings in this section determine if a sponsor is a member of this group.

  • Member Groups—Click Members to select one or more user (identity) groups and groups from external identity sources, and add those groups. In order for a user to be a member of this sponsor group, they must belong to at least one of the configured groups.

  • Other conditions—Click Create New Condition to build one or more conditions that a sponsor must match to be included in this sponsor group. You can use authentication attributes from Active Directory, LDAP, SAML, and ODBC identity stores, but not RADIUS Token or RSA SecurID stores. You can also use internal user attributes. Conditions have an attribute, and operator, and a value.

    • To create a condition using the internal dictionary attribute Name, prefix the identity group name with User Identity Groups. For example:

      InternalUser:Name EQUALS bsmith

      This means that only internal users with the Name "bsmith" can belong to this sponsor group.

    • To create a condition using the ExternalGroups attribute of an Active Directory instance, select the AD “Primary Group” for the sponsor users you want to match. For example, AD1:LastName EQUALS Smith is true if the user’s name is Smith.

In addition to matching one or more of the configured member groups, a sponsor must also match all the conditions you create here. If an authenticating sponsor user meets the matching criteria for multiple sponsor groups, then that user is granted permissions as follows:

  • An individual permission, such as Delete guests' accounts is granted if it is enabled in any of the matching groups.

  • The sponsor can create guests using the Guest Types in any of the matching groups.

  • The sponsor can create guests using the Guest Types in any of the matching groups.

  • The sponsor can create guests at the locations in any of the matching groups.

  • For a numeric value such as a batch size limit, the largest value from the matching groups is used.

You can create Matching Criteria that contain Member Groups only, or Other Conditions only. If you only specify Other Conditions, then membership of a sponsor in the sponsor group is determined solely by matching dictionary attributes.

Step 4

To specify which guest types that sponsors based on this sponsor group can create, click inside the box under This sponsor group can create accounts using these guest types, and select one or more guest types.

You can create more guest types to assign to this sponsor group by clicking the link under Create Guest Types at. After you create a new guest type, save, close, and reopen the sponsor group before you can select that new guest type.

Step 5

Use Select the locations that guests will be visiting to specify the locations (used to set the guest time zones) that sponsors in this sponsor group can choose from when creating guest accounts.

You can add more locations to choose from by clicking the link under Configure guest locations at and adding guest locations. After you create a new guest location, save, close, and reopen the sponsor group before you can select that new guest location.

This does not restrict guests from logging in from other locations.

Step 6

Under Automatic guest notification, check Automatically email guests upon account creation if email address is available if you want to save your sponsors the step of clicking Notify after creating a user. This causes a window to popup saying that an email was sent. Checking this also adds a header to the sponsor portal that says Guest notifications are sent automatically.

Step 7

Under Sponsor Can Create, configure options that sponsors in this group have for creating guest accounts.

  • Multiple guest accounts assigned to specific guests (Import)—Enable the sponsor to create multiple guest accounts by importing guest details such as first name and last name from a file.

    If this option is enabled, the Import button displays on the Create Accounts page of the Sponsor portal. The Import option is only available on desktop browsers (not mobile), such as Internet Explorer, Firefox, Safari, and so forth

  • Limit to batch of—If this sponsor group is allowed to create multiple accounts simultaneously, specify the number of guest accounts that can be created in a single import operation.

    Although a sponsor can create a maximum of 10,000 accounts, we recommend that you limit the number of accounts you create, due to potential performance issues.

  • Multiple guest accounts to be assigned to any guests (Random)—Enable the sponsor to create multiple random guest accounts as placeholders for guests who are not known as yet, or to create many accounts quickly.

    If this option is enabled, the Random button displays on the Create Accounts page of the Sponsor portal.

  • Default username prefix—Specify a username prefix that sponsors can use when creating multiple random guest accounts. If specified, this prefix appears in the Sponsor Portal when creating random guest accounts. In addition, if Allow sponsor to specify a username prefix is:

    • Enabled—The sponsor can edit the default prefix in the Sponsor portal.

    • Not enabled—The sponsor cannot edit the default prefix in the Sponsor portal.

    If you do not specify a username prefix or allow the sponsor to specify one, then the sponsor will not be able to assign username prefixes in the Sponsor portal.

  • Allow sponsor to specify a username prefix—If this sponsor group is allowed to create multiple accounts simultaneously, specify the number of guest accounts that can be created in a single import operation.

    Although a sponsor can create a maximum of 10,000 accounts, we recommend that you limit the number of accounts you create, due to potential performance issues.

Step 8

Under Sponsor Can Manage, you can restrict which guests accounts the members of this sponsor group can view and manage.

  • Only accounts sponsor has created—Sponsors in this group can view and manage only the guest accounts that they have created, which is based on the Sponsor’s email account.

  • Accounts created by members of this sponsor group—Sponsors in this group can view and manage the guest accounts created by any sponsor in this sponsor group.

  • All guest accounts—Sponsors view and manage all pending guest accounts.

Step 9

Under Sponsor Can, you can provide more privileges related to guest passwords and accounts to the members of this sponsor group.

  • Update guests' contact information (email, Phone Number)—For guest accounts that they can manage, allow the sponsor to change a guest's contact information

  • View/print guests' passwords—When this is checked the sponsor can print passwords for guests. The sponsor can see the passwords for guests on the Manage Accounts page and in the details for a guest. When this is not checked, the sponsor can't print the password, but the user can still get the password through email or SMS, if configured.

  • Send SMS notifications with guests’ credentials—For guest accounts that they can manage, allow the sponsor to send SMS (text) notifications to guests with their account details and login credentials.

  • Reset guest account passwords—For guest accounts that they can manage, allow the sponsor to reset passwords for guests to a random password generated by Cisco ISE.

  • Extend guests’ accounts—For guest accounts that they can manage, allow the sponsor to extend them beyond their expiration date. The sponsor is automatically copied on email notifications sent to guests regarding their account expiration.

  • Delete guests’ accounts—For guest accounts that they can manage, allow the sponsor to delete the accounts, and prevent guests from accessing your company's network.

  • Suspend guests’ accounts—For guest accounts that they can manage, allow the sponsor to suspend their accounts to prevent guests from logging in temporarily.

    This action also issues a Change of Authorization (CoA) Terminate to remove the suspended guests from the network.

    • Require sponsor to provide a reason—Require the sponsor to provide an explanation for suspending the guest accounts.

  • Approve and view requests from self-registering guests—Sponsors who are included in this Sponsor Group can either view all pending account requests from self-registering guests (that require approval), or only the requests where the user entered the Sponsor's email address as the person being visited. This feature requires that the portal used by the Self-registering guest has Require self-registered guests to be approved checked, and the Sponsor's email is listed as the person to contact.

    • Any pending accounts—A sponsor belonging to this group an approve and review accounts that were created by any sponsor.

    • Only pending accounts assigned to this sponsor—A sponsor belonging to this group can only view and approve accounts that they created.

  • Access Cisco ISE guest accounts using the programmatic interface (Guest REST API)—For guest accounts that they can manage, allow the sponsor to access guest accounts using the Guest REST API programming interface.

Step 10

Click Save and then Close.


Configure Account Content for Sponsor Account Creation

You can configure the type of user data that your guests and sponsors must provide to create a new guest account. Some fields are required to identify an ISE account, but you can eliminate other fields, and add your own custom fields.

To configure fields for account creation by Sponsors:

  1. In ISE, choose Work Centers > Guest Access > Portals & Components > Sponsor Portals, and edit your sponsor portal

  2. Select the Portal Page Customization tab.

  3. Scroll down and select Create Account for Known Guests.

  4. On the Preview display on the right, select Settings.

These settings determine which fields display and are required for guest accounts when they are created on the sponsor portal. This configuration applies to Known, Random, and Imported guest types. The template that the sponsor downloads to import new users is created dynamically, so that only the fields set in Known Guests are included.

Import Username and Password for Accounts

Sponsors can import username and password, but those rows are not added to the CSV template when the sponsor downloads it. The sponsor can add those headings. They must be named properly in order for the ISE to recognize the columns:

  • Username—Can be either User Name or UserName.

  • Password—Must be password.

Special Settings for the Sponsor Portal

The following settings are unique to the Create Account for Imported Guests page, on the Portal Page Customization tab, on the Sponsor Portal.

  • Allow sponsor to be copied in Guest Credentials email: If you enable this option, then each email of guest credentials that is sent to a successfully imported guest is also sent to the sponsor. The default is to not send emails to the sponsor.

  • Allow sponsor to receive summary email: When a sponsor imports a list of users, ISE sends one email with a summary of all the imported users. If you uncheck this option, the sponsor gets a separate email for each imported user.

Configure a Sponsor Portal Flow

You can use a default portal and its default settings such as certificates, endpoint identity group, identity source sequence, portal themes, images, and other details provided by Cisco ISE. If you do not want to use the default settings, you should create a new portal or edit an existing one to meet your needs. You can duplicate a portal if you want to create multiple portals with the same settings.

You may want to create multiple sponsor portals if your company has different branding for your corporate office and its retail locations, or if your company has different product brands, or if a city’s offices want different themed portals for the fire, police, and other departments.

These are the tasks related to configuring a Sponsor portal.

Before you begin

Configure or edit existing sponsor groups for your site, as described in Configure Sponsor Groups.

Procedure


Step 1

Enable Policy Services.

Step 2

Add Certificates for Guest Services.

Step 3

Create External Identity Sources.

Step 4

Create Identity Source Sequences.

Step 5

Create a Sponsor Portal.

Step 6

(Optional) Customize Sponsor Portals.


Enable Policy Services

To support the Cisco ISE end-user web portals, you must enable portal-policy services on the node on which you want to host them.

Procedure

Step 1

Choose Administration > System > Deployment

Step 2

Click the node and click Edit.

Step 3

On the General Settings tab, check Policy Service.

Step 4

Check the Enable Session Services option.

Step 5

Click Save.


Add Certificates for Guest Services

If you do not want to use the default certificates, you can add a valid certificate and assign it to a certificate group tag. The default certificate group tag used for all end-user web portals is Default Portal Certificate Group.

Procedure

Step 1

Chose Administration > System > Certificates > System Certificates.

Step 2

Add a system certificate and assign it to a certificate group tag that you want to use for the portal.

This certificate group tag will be available to select during portal creation or editing.
Step 3

Choose Work Centers > Guest Access > Portals & Components > Sponsor Portals > Create or Edit > Portal Settings.

Step 4

Select the specific certificate group tag from the Certificate Group Tag drop-down list that is associated with the newly added certificate.


Create External Identity Sources

Cisco ISE can connect with external identity sources such as Active Directory, LDAP, RADIUS Token, and RSA SecurID servers to obtain user information for authentication and authorization. External identity sources also include certificate authentication profiles that you need for certificate-based authentications.


Note

To work with passive identity services, which enable you to receive and share authenticated user identities, see Additional Passive Identity Service Providers.


Procedure

Step 1

Choose Administration > Identity Management > External Identity Sources.

Step 2

Choose one of these options:


Create Identity Source Sequences

Before you begin

Ensure that you have configured your external identity sources in Cisco ISE.

To perform the following task, you must be a Super Admin or System Admin.

For allowing guest users to authenticate through Local WebAuth, you must configure both the Guest Portal authentication source and the identity source sequence to contain the same identity stores.

Procedure

Step 1

Choose Administration > Identity Management > Identity Source Sequences > Add.

Step 2

Enter a name for the identity source sequence. You can also enter an optional description.

Step 3

Check the Select Certificate Authentication Profile check box and choose a certificate authentication profile for certificate-based authentication.

Step 4

Choose the database or databases that you want to include in the identity source sequence in the Selected List box.

Step 5

Rearrange the databases in the Selected list in the order in which you want Cisco ISE to search the databases.

Step 6

Choose one of the following options in the Advanced Search List area:

  • Do not access other stores in the sequence and set the AuthenticationStatus attribute to ProcessError —If you want Cisco ISE to discontinue the search, if the user is not found in the first selected identity source.

  • Treat as if the user was not found and proceed to the next store in the sequence —If you want Cisco ISE to continue searching the other selected identity sources in sequence, if the user is not found in the first selected identity source.

    While processing a request, Cisco ISE searches these identity sources in sequence. Ensure that you have the identity sources in the Selected list box listed in the order in which you want Cisco ISE to search them.

Step 7

Click Submit to create the identity source sequence that you can then use in policies.


Create a Sponsor Portal

You can provide a Sponsor portal to enable sponsors to create, manage, and approve accounts for guests who want to connect to your network to access the internet and internal resources and services.

Cisco ISE provides you with a default Sponsor portal that you can use without having to create another one. However, you can create a new Sponsor portal, or you can edit or duplicate an existing one. You can delete any of these portals, except the default Sponsor portal.

Any changes that you make to the Page Settings on the Portal Behavior and Flow Settings tab are reflected in the graphical flow in the Sponsor Flow diagram. If you enable a page, such as the AUP page, it appears in the flow and the sponsor will experience it in the portal. If you disable it, it is removed from the flow and the next enabled page displays for the sponsor.

Before you begin

Ensure that you have the required certificates, external identity sources, and identity source sequences configured for use with this portal.

Procedure

Step 1

Configure the Portal Settings page, as described in Portal Settings for Sponsor Portals.

Ensure that the portal name that you use here is not used for any other end-user portals.
Step 2

Configure the Login Settings page , as described in Login Settings for Sponsor Portals.

Step 3

Configure the Acceptable Use Policy (AUP) Page Settings page, as described in Acceptable Use Policy (AUP) Settings for Sponsor Portals .

Step 4

Configure the Sponsor Change Password Settings page, as described in Set the Guest Password Policy and Expiration and in Rules for Guest Password Policies.

Step 5

Configure the Post-Login Banner Page Settings page, as described in Post-Login Banner Settings for Sponsor Portals.

Step 6

Sponsor Portal Application Settings refers you to the Portal Customization tab if you with to customize the portal.

Step 7

Click Save.


Customize Sponsor Portals

You can customize the portal appearance and user experience by customizing the portal themes, changing UI elements on the portal pages, and editing error messages and notifications that display to the users. For more information about customizing portals, see Customization of End-User Web Portals.

Configuring Account Content for Sponsor Account Creation

You can configure the type of user data that your guests and sponsors must provide to create a new guest account. Some fields are required to identify an ISE account, but you can eliminate other fields, and add your own custom fields.

To configure fields for account creation by Sponsors:

  1. In ISE, choose Work Centers > Guest Access > Portals & Components > Sponsor Portals, and edit your sponsor portal.

  2. Select the Portal Page Customization tab.

  3. Scroll down and select Create Account for Known Guests.

    • On the Preview display on the right, select Settings.

    These settings determine which fields display and are required for guest accounts when they are created on the sponsor portal.

This configuration applies to Known, Random, and Imported guest types. The template that the sponsor downloads to import new users is created dynamically, so that only the fields set in Known Guests are included.

Sponsor Import Usernames and Passwords for Accounts

Sponsors can import username and password, but those rows are not added to the template when the sponsor downloads it. The sponsor can add those headings. They must be named properly in order for the ISE to recognize the columns:

  • Username—Can be either User Name or UserName

  • Password—Must be password

Configuring the Time Settings Available to Sponsors

When sponsors create a new guest account, they configure the time that the account is active. You configure the options that are available to the sponsor, to allow them to set the account duration, and the start and end times. These options are configured by guest type. The sponsor sees the results under the heading Access Information.

The Guest Type settings that control sponsor portal account time options are under the heading Maximum Access Time, and are described below:

  • From first login - The sponsor portal shows Duration, and FromFirst Login displays under the field:

    The guest type setting Maximum account duration determines which values the Sponsor can enter for duration.

  • From sponsor-specified date (or date of self-registration, if applicable) - The sponsor can choose between setting the duration as End of business day, or, by unchecking that field, the duration, start and end times.

    The guest type settings to control the duration time and effective dates are under the heading Allow access only on these days and times.

    • The days of the week that you select limits the dates that are selectable in the Sponsor's calendar.

    • Maximum account duration is enforced in the sponsor portal when picking duration and dates.

Kerberos Authentication for the Sponsor Portal

You can configure ISE to use Kerberos to authenticate a sponsor user who is logged onto Windows for access to the sponsor portal. This process uses the Active Directory credentials of the logged in sponsor user in the Kerberos ticket. Kerberos SSO is performed inside the secure tunnel after the browser establishes the SSL connection with ISE.

The following items must be in the same Active Directory domain:

  • Sponsor's PC

  • ISE PSN

  • FQDN configured for this sponsor portal

This requirement is because Microsoft does not support Kerberos SSO with 2-way trusts across Active Directory forests.

The sponsor user must be logged onto Windows.

Kerberos authentication is NOT supported for the Guest portal.

Configuring Kerberos

To enable Kerberos on the Sponsor portal, check the Allow Kerberos SSO check box in the Sponsor Settings and Customization page.

The sponsor's browser must also be configured properly. The following sections explain how to manually configure each browser.

To Manually Configure Firefox

  1. Enter about:config in the address bar.

  2. Ignore warnings that appear, and click to continue.

  3. Search for negotiate in the search bar.

  4. Add the FQDN to network.negotiate-auth.delegation-uris and network.negotiate-auth.trusted-uris. The list of URLs for each attribute is separated by commas.

  5. Close the tab. The browser is ready, no restart is required.

To Manually Configure Internet Explorer

  1. Click the gear on the top right, and select Internet Options.

  2. Click the Security tab.

  3. Select Local Intranet.

  4. Click the Sites button, then the Advanced button.

  5. Add in the string <mydomain>.com, where <mydomain> is a wild card for the Sponsor portal FQDN, or you can enter the FQDN.

  6. Click Close, and then OK.

  7. Click the Advanced tab.

  8. Scroll down to the Security check-boxes, make sure the checkbox Enable Integrated Windows Authentication is enabled.

  9. Restart the computer.

Chrome gets the configuration from Internet Explorer

Troubleshooting
  • Run set user in the command prompt to verify that the machine is tied to proper AD domain.

  • Run klist in the command prompt to see list of cached Kerberos tickets and the hostnames.

  • Look at the SPNEGO token data. The NTLM password-based token string is much shorter than Kerberos token string; the correct token string should not fit on one line.

  • Use Wireshark using the filter kerberos to capture Kerberos request, if it exists.


Note

When the Kerberos SSO option is enabled, the user needs to access the sponsor portal by the node FQDN for Kerberos SSO to function properly. If a portal FQDN is configured for the sponsor portal, when the user connects to the portal FQDN, the user will be redirected to the portal by its node FQDN.


Sponsors Cannot Log In to the Sponsor Portal

Problem
The following error message appears when a sponsor tries to log in to the Sponsor portal:

“Invalid username or password. Please try again.”

Causes
  • The sponsor has entered invalid credentials.

  • The sponsor is not valid because the user record is not present in the database (Internal Users or Active Directory).

  • The sponsor group to which the sponsor belongs is disabled.

  • The Sponsor's user account is not a member of an active/enabled Sponsor Group, which means the Sponsor user's Identity Group is not a member of any Sponsor Group.

  • The sponsor’s internal user account is disabled (suspended).

Solution
  • Verify the user’s credentials.

  • Enable the sponsor group.

  • Reinstate the user account if disabled.

  • Add the sponsor user's Identity Group as a member of a Sponsor Group.

Monitor Guest and Sponsor Activity

Cisco ISE provides various reports and logs that allow you to view endpoint and user management information and guest and sponsor activity. Some of the Cisco ISE 1.2 reports have been deprecated, but the information can be viewed in other reports.

You can run these reports either on demand or on a scheduled basis.

Procedure


Step 1

Choose Operations > Reports.

Step 2

Under the Report Selector, expand the Guest Access Reports and Endpoints and Users selections to view the various guest, sponsor, and endpoint related reports.

Step 3

Select the report and choose the data with which you want to search using the Filters drop-down list.

You can use filters on username, portal name, device name, endpoint identity group and other such data.

Step 4

Select the Time Range during which you want to view the data.

Step 5

Click Run.


Metrics Dashboard

Cisco ISE provides an at-a-glance view of Authenticated Guests and Active Endpoints in the network in a metrics dashboard that appears on the Cisco ISE Home page.

Note

For Hotspot flow, the endpoints are not displayed on the Authenticated Guests dashlet


AUP Acceptance Status Report

The AUP Acceptance Status report displays the acceptance status of the Acceptable Use Policy (AUP) by guests from all the Guest portals. This report is available at: Operations > Reports > Guest Access Reports > AUP Acceptance Status.

You can use the report to track all the accepted and denied AUP connections for a given period of time.

Guest Accounting Report

The Guest Accounting report displays the guest login history for an indicated time period. This report is available at: Operations > Reports > Guest Access Reports > Guest Accounting.

Master Guest Report

The Master Guest report combines data from various reports into a single view enabling you to export data from different reporting sources. You can add more data columns and remove the ones you do not want to view or export. This report is available at Operations > Reports > Guest Access Reports > Master Guest. It now includes information that used to be in the deprecated Guest Activity Report.

This report collects all guest activity and provides details about the websites that guest users visit. You can use this report for security auditing purposes to see when guest users accessed the network and what they did on it. To view the guests’ Internet activity, such as the URLs of the websites that they visited, you must first:

  • Enable the passed authentications logging category. Choose Administration > System > Logging > Logging Categories and select Passed authentications.

  • Enable these options on the firewall used for guest traffic:

    • Inspect HTTP traffic and send data to Cisco ISE Monitoring node. Cisco ISE requires only the IP address and accessed URL for the Guest Activity report; so, limit the data to include just this information, if possible.

    • Send syslogs to Cisco ISE Monitoring node.

Sponsor Login and Audit Report

The Sponsor Login and Audit report is a combined report that tracks:

  • Login activity by the sponsors at the Sponsor portal.

  • Guest-related operations performed by the sponsors in the Sponsor portal.

This report is available at Operations > Reports > Guest Access Reports > Sponsor Login and Audit.

Audit Logging for Guest and Sponsor Portals

During specific actions within the Guest and Sponsor portals, audit log messages are sent to the underlying audit system. By default, these messages appear in the /opt/CSCOcpm/logs/localStore/iseLocalStore.log file.

You can configure these messages to be sent by syslog to the monitoring and troubleshooting system and log collector. The monitoring subsystem presents this information in the appropriate sponsor and device audit logs and guest activity logs.

Guest login flow is logged in the audit logs regardless of whether the guest login has passed or failed.

Guest Access Web Authentication Options

Cisco ISE Guest and Web Authentication Services support several deployment options that enable secure guest access. You can provide wired or wireless guest connectivity using Local or Central Web Authentication and Device Registration Web Authentication.

  • Central Web Authentication (Central WebAuth)—Applies to all Guest portals. Uses Web authentication by a central Cisco ISE RADIUS server for both wired and wireless connection requests. Guests authenticate after by either entering an optional access code on the Hotspot Guest portals, or by entering a username and password on the Credentialed Guest portals.


    Note

    When using redirection to a browser for user credentials (CWA), we do not support users whose browsers open multiple tabs. During redirection, if the browser opens more than one tab, ISE redirects to every tab. The user can log in to the portal, but ISE can't authorize the session, and the user fails to gain access.

    To work around this problem, the user must close all but one tab on their browser.


  • Local Web Authentication (Local WebAuth)—Applies to the Credentialed Guest portals. The guest connects to a switch for a wired connections, or a wireless LAN controller (WLC) for a wireless connection. The network access device (NAD) directs them to web pages for authentication. The guest enters a username and password on the Credentialed Guest portals to authenticate.

  • Device Registration Web Authentication (Device Registration WebAuth)—Applies only to the Hotspot Guest portal. Cisco ISE registers and authorizes the guest device before Web authentication. When guests connect to a wired or wireless NAD, they are directed to the Hotspot Guest portal. Guests get network access without providing credentials (username and password).

ISE Community Resource

For information on how to configure Cisco ISE with Cisco Wireless Controller to provide guest access, see ISE Guest Access Prescriptive Deployment Guide.

Also see the ISE Tech Note ISE Wireless Guest Setup Guide & Wizard.

NAD with Central WebAuth Process

In this scenario, the network access device (NAD) makes a new authorization request to the Cisco ISE RADIUS server from an unknown endpoint connection. The endpoint then receives a url-redirect to Cisco ISE.


Note

webauth-vrf-aware command is supported only in IOS XE 3.7E, IOS 15.2(4)E or later versions. Other switches do not support WebAuth URL redirect in virtual routing and forwarding (VRF) environment. In such cases, as a workaround, you can add a route in the global routing table to leak the traffic back into the VRF.

If the guest device is connected to a NAD, the guest service interaction takes the form of a MAC Authentication Bypass (MAB) request that leads to a Guest portal Central WebAuth login. The following is an outline of the subsequent Central Web Authentication (Central WebAuth) process, which applies to both wireless and wired network access devices.

  1. The guest device connects to the NAD through a hard-wired connection. There is no 802.1X supplicant on the guest device.

  2. An authentication policy with a service type for MAB allows a MAB failure to continue and return a restricted network profile containing a url-redirect for the Central WebAuth user interface.

  3. The NAD is configured to authenticate MAB requests to the Cisco ISE RADIUS server.

  4. The Cisco ISE RADIUS server processes the MAB request and does not find an endpoint for the guest device.

    This MAB failure resolves to the restricted network profile and returns the url-redirect value in the profile to the NAD in an access-accept. To support this function, ensure that an authorization policy exists and features the appropriate wired or wireless MAB (under compound conditions) and, optionally, “Session:Posture Status=Unknown” conditions. The NAD uses this value to redirect all guest HTTPS traffic on the default port 8443 to the url-redirect value.

    The standard URL value in this case is: https://ip:port/guestportal/gateway?sessionId=NetworkSessionId&portal=<PortalID>&action=cwa.

  5. The guest device initiates an HTTP request to redirect URL via a web browser.

  6. The NAD redirects the request to the url-redirect value returned from the initial access-accept.

  7. The gateway URL value with action CWA redirects to the Guest portal login page.

  8. The guest enters their login credentials and submits the login form.

  9. The guest server authenticates the login credentials.

  10. Depending on the type of flow, the following occurs:

    • If it is a non-posture flow (authentication without further validation), where the Guest portal is not configured to perform client provisioning, the guest server sends a CoA to the NAD. This CoA causes the NAD to reauthenticate the guest device using the Cisco ISE RADIUS server. A new access-accept is returned to the NAD with the configured network access. If client provisioning is not configured and the VLAN needs to be changed, the Guest portal performs VLAN IP renew. The guest does not have to re-enter login credentials. The username and password entered for the initial login are used automatically.

    • If it is a posture flow, where the Guest portal is configured to perform client provisioning, the guest device web browser displays the Client Provisioning page for posture agent installation and compliance. (You can also optionally configure the client provisioning resource policy to feature a “NetworkAccess:UseCase=GuestFlow” condition.)

Because there is no client provisioning or posture agent for Linux, the Guest portal redirects to the Client Provisioning portal, which in turn redirects back to a guest authentication servlet to perform optional IP release/renew and then CoA.

With redirection to the Client Provisioning portal, the Client Provisioning service downloads a non-persistent web agent to the guest device and performs a posture check of the device. (You can optionally configure the posture policy with a “NetworkAccess:UseCase=GuestFlow” condition.)

If the guest device is non-compliant, ensure that you have configured an authorization policy that features “NetworkAccess:UseCase=GuestFlow” and “Session:Posture Status=NonCompliant” conditions.

When the guest device is compliant, ensure that you have an authorization policy configured with the conditions “NetworkAccess:UseCase=GuestFlow” and “Session:Posture Status=Compliant.” From here, the Client Provisioning service issues a CoA to the NAD. This CoA causes the NAD to reauthenticate the guest using the Cisco ISE RADIUS server. A new access-accept is returned to the NAD with the configured network access.


Note

“NetworkAccess:UseCase=GuestFlow” can also apply for Active Directory (AD) and LDAP users who log in as guests.

Wireless LAN Controller with Local WebAuth Process

In this scenario, the guest logs in and is directed to the wireless LAN controller (WLC). The WLC then redirects the guest to a Guest portal, where they are prompted to enter their login credentials, accept an optional Acceptable Use Policy (AUP), and perform an optional password change. When this is complete, the guest device’s browser is redirected back to the WLC to provide login credentials via a POST.

The WLC can now log the guest in via the Cisco ISE RADIUS server. When this is complete, the WLC redirects the guest device's browser to the original URL destination. The Wireless LAN Controller (WLC) and the network access devices (NAD) requirements to support the original URL redirect for guest portals are WLC 5760 and Cisco Catalyst 3850, 3650, 2000, 3000, and 4000 Series Access Switches running releases IOS-XE 3.6.0.E and 15.2(2)E.

Figure 1. WLC with Local WebAuth Non-Posture Flow

Wired NAD with Local WebAuth Process

In this scenario, the Guest portal redirects the guest login request to the switch (wired NAD). The login request is in the form of an HTTPS URL posted to the switch and contains the login credentials. The switch receives the guest login request and authenticates the guest using the configured Cisco ISE RADIUS server.

  1. Cisco ISE requires a login.html file with the HTML redirect to be uploaded to the NAD. This login.html file is returned to the browser of the guest device for any HTTPS request made.

  2. The browser of the guest device is redirected to the Guest portal where the guest’s login credentials are entered.

  3. After the Acceptable Use Policy (AUP) and change password are processed, both of which are optional, the Guest portal redirects the browser of the guest device to post the login credentials on the NAD.

  4. The NAD makes a RADIUS request to the Cisco ISE RADIUS server to authenticate and authorize the guest.

IP Address and Port Values Required for the Login.html Page

The IP address and port values must be changed in the following HTML code for the login.html page to those values being used by the Cisco ISE Policy Services nodes. The default port is 8443, but you can change this value, so ensure that the value you assign to the switch matches the setting in Cisco ISE.


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<head>
<title>ISE Guest Portal</title>
<meta Http-Equiv="Cache-Control" Content="no-cache">
<meta Http-Equiv="Pragma" Content="no-cache">
<meta Http-Equiv="Expires" Content="0">
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">

<meta http-equiv="REFRESH" content="0;url=https://ip:port/portal/PortalSetup.action?switch_url=wired">

</HEAD>
<BODY>

<center>
Redirecting ... Login
<br>
<br>
<a href="https://ip:port/portal/PortalSetup.action?switch_url=wired">ISE Guest Portal</a>
</center>

</BODY>
</HTML>

Because the custom login page is a public web form, consider these guidelines:

  • The login form must accept user entries for the username and password and must show them as uname and pwd.

  • The custom login page should follow best practices for a web form, such as page timeout, hidden password, and prevention of redundant submissions.

HTTPS Server Enabled on the NAD

To use web-based authentication, you must enable the HTTPS server within the switch using the ip http secure-server command.

Support for Customized Authentication Proxy Web Pages on the NAD

You can upload custom pages for success, expiry, and failure to the NAD. Cisco ISE does not require any specific customization, so you can create these pages using the standard configuration instructions included with the NAD.

Configure Web Authentication on the NAD

You need to complete the web authentication on the NAD by replacing the default HTML pages with your custom files.

Before you begin

During web-based authentication, create four substitute HTML pages to use instead of the switch default HTML pages.

Procedure

Step 1

To specify the use of your custom authentication proxy web pages, first store your custom HTML files on the switch flash memory. To copy your HTML files to the switch flash memory, run the following command on the switch:

copy tftp/ftp flash

Step 2

After copying your HTML files to the switch, perform the following commands in global configuration mode:

a.

ip admission proxy http login page file device:login-filename

Specifies the location in the switch memory file system of the custom HTML file to use in place of the default login page. The device: is flash memory.

b.

ip admission proxy http success page file device:success-filename

Specifies the location of the custom HTML file to use in place of the default login success page.

c.

ip admission proxy http failure page file device:fail-filename

Specifies the location of the custom HTML file to use in place of the default login failure page.

d.

ip admission proxy http login expired page file device:expired-filename

Specifies the location of the custom HTML file to use in place of the default login expired page.

Step 3

Configure the customized authentication proxy web pages following the guidelines provided by the switch.

Step 4

Verify the configuration of a custom authentication proxy web page, as shown in the following example:


Switch# show ip admission configuration
Authentication proxy webpage
        Login page           : flash:login.htm
        Success page         : flash:success.htm
        Fail Page            : flash:fail.htm
        Login expired Page   : flash:expired.htm

Authentication global cache time is 60 minutes
Authentication global absolute time is 0 minutes
Authentication global init state time is 2 minutes
Authentication Proxy Session ratelimit is 100
Authentication Proxy Watch-list is disabled
Authentication Proxy Auditing is disabled
Max Login attempts per user is 5


Device Registration WebAuth Process

Using Device Registration Web Authentication (Device Registration WebAuth) and the Hotspot Guest portal, you can allow guest devices to connect to a private network without requiring usernames and passwords.

In this scenario, the guest connects to the network with a wireless connection. See Figure 16-1 for an example of the Device Registration WebAuth process flow. The following is an outline of the subsequent Device Registration WebAuth process, which is similar for both wireless and wired connections:

  1. The network access device (NAD) sends a redirect to the Hotspot Guest portal.

  2. If the MAC address of the guest device is not in any endpoint identity group or is not marked with an Acceptable Use Policy (AUP) accepted attribute set to true, Cisco ISE responds with a URL redirection specified in an authorization profile.

  3. The URL redirection presents the guest with an AUP page (if enabled) when the guest attempts to access any URL.

    • If the guest accepts the AUP, the endpoint associated with their device MAC address is assigned to the configured endpoint identity group. This endpoint is now marked with an AUP accepted attribute set to true, to track the guest acceptance of the AUP.

    • If the guest does not accept the AUP or if an error occurs, for instance, while creating or updating the endpoint, an error message displays.

  4. Based on the Hotspot Guest portal configuration, a post-access banner page (if enabled) with additional information may appear.

  5. After the endpoint is created or updated, a Change of Authorization (CoA) termination is sent to the NAD.

  6. After the CoA, the NAD re-authenticates the guest connection with a new MAC Auth Bypass (MAB) request. The new authentication finds the endpoint with its associated endpoint identity group, and returns the configured access to the NAD.

  7. Based on the Hotspot Guest portal configuration, the guest is directed to the URL to which they requested access, or to a custom URL specified by the administrator, or to an Authentication Success Page.

The CoA type for both wired and wireless is Termination CoA. You can configure the Hotspot Guest portal to perform VLAN DHCP Release (and renew), thereby re-authorizing the CoA type for both wired and wireless to Change of Auth.

VLAN DHCP Release support is available for Windows devices only. It is not available for mobile devices. If the device being registered is mobile and the VLAN DHCP Release option is enabled, the guest is requested to manually renew their IP address. For mobile device users, we recommend using Access Control Lists (ACLs) on the WLC, rather than using VLANs.

Figure 2. Wireless Device Registration Web Authentication Flow
Wireless Device Registration Web Authentication Flow