The authentication steps for a repeat user for various scenarios are as follows:

• Completed the finger print verification (Data Capture module is not configured): the internet is provisioned when the customer clicks or taps any menu item.

• Completed the finger print verification(Data Capture module is configured, the Data Capture form is filled): the internet is provisioned when the customer clicks or taps any menu item.

• Completed the finger print verification, bit Data capture form is not filled or partially filled( for non mandatory fields): the internet is provisioned when the customer clicks or taps any menu item. However, the Data Capture form appears if any information has changed.

• Not completed the finger print verification, but filled the Data Capture form: When the customer clicks or tap any menu item, the mobile number field appears along with the pre-filled Data Capture form. The customer must enter the mobile number again to access the internet. This process repeats for all internet access attempts until fingerprint verification is complete.

• Mobile number verification process was not completed during previous internet access: If the verification process is not complete within a limited time, the internet is provisioned even for invalid mobile numbers. For such users, when the captive portal loads and the customer clicks any menu item or link, the login screen appears with the mobile number field. The customer must enter a valid mobile number.

• The Data Capture module is configured, and the registration details are outdated: When the captive portal loads, and the customer click any menu item or link in the portal, the registration form appears with the previously filled data. The customer can update the form and press Connect to access the internet

  These are some of the scenarios when the registration details become outdated:

  • Added new mandatory fields: Added a new mandatory field in the Data Capture module. For example, if you configure the Data Capture module without a Gender field and later add it as mandatory.

  • Optional field becomes mandatory: The Data Capture module was modified to make an optional field that the customer skipped during registration mandatory. For example, you have configured a Data Capture module with the last name as optional. The customer connected to the SSID and completed the registration without mentioning the last name. Now, you modified the Data Capture module and made the last name mandatory for registration.

  • Modified the choice options: Removed or replaced a choice option that was available for selection. For example, you configured a mandatory business tag, 'Age Criteria,' with 'Child' and 'Adult' as choice options. The customer completed registration by selecting 'Child.' Later, you modified the choices to display as 'Kids' and 'Adult.

Note	If the Terms and Conditions change in any of these scenarios, the 'Accept Terms and Continue' button appears. The customer must press the 'Accept Terms and Continue' button to access the internet or continue to the next authentication step.

In Cisco Spaces, as part of the authentication workflow for a new user, you need to enter the email address only once. All domain-related validations and MX record checks are cached for a specific duration. These checks are not repeated for other users from the same domain within the cached duration.

For example, if 10 users connect to the Captive Portal at the same time and enter email addresses from the same domain (such as xyz@abc.com), the domain validation and MX record check occur only once during the specified caching period. However, SMTP connection and mailbox checks are performed for all 10 users to verify whether each user ID is valid.

To make a SMTP connection:

1. Establish a socket connection to the SMTP server and verify the response.

2. Run the ELHO command and verify the response.

3. Run the MAIL FROM command and verify the response.

4. Run the RCPT TO command and verify the response.

Note

As part of the Captive Portal new user onboard workflow, the email address of a user is recorded only once. You can authenticate to Cisco Spaces even if no response was received from the mailbox check. However, you must enter your email address again during your next visit. As part of the mailbox check process, Cisco Spaces will never send an email request to the email address provided by the user.

Registration Information

These are some of the scenarios when the registration details become outdated:

• Added new mandatory fields: You added a new mandatory field in the Data Capture form. For example, you configured the form without a Gender field, and the registration was completed. Later, you added the Gender field to the Data Capture form and marked it as mandatory.

• 'Optional field becomes mandatory: You modified the Data Capture form to make a previously optional field mandatory. For example, if the last name was optional and a customer registered without entering it, you can later update the form to require this field.

• Modified the choice options: You removed or replaced a choice option that was available for selection. For example, you originally had choice options as Child and Adult for the Age Criteria field. A customer selected Child during registration. Later, you changed the options to Kids and Adult.

Note	If there is any change in the Terms & Conditions in these scenarios, the Accept Terms and Continue option is displayed. You must select the Accept Terms and Continue option to access the internet or proceed to the next authentication step.

The authentication process for repeat users varies according to the scenario.

• Data Capture is not configured: When the captive portal loads and the customer clicks any menu item or link in the portal, the internet is provisioned.

• Data Capture is configured, and the customer completed the registration: When the captive portal loads, and the customer click any menu item or link in the portal, the internet is provisioned.

• Data Capture is configured, and the registration details are outdated: When the captive portal loads, and the customer click any menu item or link in the portal, the Data Capture form appears with the previously filled data. The customer can update the form, and press the “Connect” button to get access to the internet.

  These scenarios can cause the registration details to become outdated.

  • Added new mandatory fields: For example, you configured the Data Capture form without a Gender field. The customer completes registration. Later, you add the Gender field and mark it as mandatory.

  • Optional field becomes mandatory: For example, you configure a Data Capture form with the last name as optional. The customer connects to the SSID and completes registration without entering the last name. Later, you modify the form and make the last name mandatory.

  • Modified the choice options: Modified the choice options. For example, you configure a mandatory business tag “Age Criteria” with the choice options “Child” and “Adult.” The customer completes registration by selecting “Child” for Age Criteria. Later, you modify the options to display “Kids” and “Adult.

  • Entered invalid e-mail ID during previous log in: When the captive portal loads and the customer clicks any menu item or link in the portal, the Data Capture form appears with the invalid e-mail ID entered previously. The customer must enter a valid e-mail ID to continue.

Note	If the Terms and Conditions change in any of these scenarios, the Accept Terms and Continue button appears. The customer must press this button to access the internet or proceed to the next authentication step.

When the captive portal loads and the customer clicks any menu item or link in the portal, the internet is provisioned.

Note	If the Terms and Conditions change, the “Accept Terms and Continue” button appears. The customer must press the “Accept Terms and Continue” button to get access to the internet or to move to the next authentication step.

When the captive portal loads and the customer clicks any menu item or link, options to connect with all the configured social networks appear. Social networks that the customer has used previously for authentication are labeled as Continue with [social network]. For instance, if the customer previously used Facebook authentication to access the internet through the captive portal, the Facebook option is labeled as “Continue with Facebook. For social networks that have not been used previously for authentication, a sign-in option appears, such as “Sign in with LinkedIn.”

• If the customer selects a social network previously used for authentication, internet access is provisioned without requiring authentication. However, if the Terms and Conditions have changed, the Terms and Conditions screen appears. The customer must then press the “Accept Terms and Continue” button to access the internet.

• If the customer signs in using a social network that was not used previously for authentication, the complete authentication process must be finished for that social network. If the customer has accessed the internet using social authentication through any social network, the Terms and Conditions screen is not displayed during authentication. However, if the terms and conditions have changed, the Terms and Conditions screen appears during authentication. The customer must press the “Accept Terms and Continue” button to access the internet.