Authentication Page

This section allows administrators to enable and configure multiple guest authentication methods and customize the Captive Portal login experience. Login methods can be enabled individually or combined, depending on operational, security, and access requirements.

The type of data processed depends on the selected login method and operator configuration. Data retention duration and automatic deletion behavior are configured under System > Data Retention.

1. Login Options

This page allows you to enable and configure various login methods to meet specific user authentication and access requirements. Here you have the flexibility to select a single login method or a combination of methods to best suit the organization's security protocols and user access needs. 

Some authentication methods do not collect user data, while others collect authentication identifiers or operator-defined information. The scope of collected data depends entirely on the selected login method and configuration.

Free Guest Access - Bypass Page (default)

This option provides immediate network access by bypassing the authentication page entirely. No user input or data collection is performed. 

This method is suitable for environments where instant access is required without validation or data capture. This method is enabled by default.

Free Guest Access - With Validation

This option enables Free Access with optional validation mechanisms. Any optional fields displayed are defined by the operator and may be enabled or disabled at their discretion.

Guests may:

• Enter information in up to three optional custom fields

• Use a shared venue-wide password

• Click a “Connect to WiFi” button for simple access

Any non-required fields left empty are automatically hidden.




Fields:

• Order Priority: Defines the placement of this form on the page. The forms are displayed in ascending order based on their priority value. For example, if this form has an order priority of 1, it will be shown first. If it has an order priority of 10, it will be shown last. This is useful when multiple forms are used, ensuring a structured and user-friendly layout.
  
  

• Free guest access title: This field defines the title or prompt that appears to the guest for accessing the network

  Example: "Connection via password"
  
  

• Free guest access text: This field provides instructions or information to the guest about the access process.
  Example: "Use a password to get connected to our network."
  
  

• Free guest access extra field 1 label: Label for the first additional field where guests can enter information.
  Example: "Custom Field 1"
  
  

• Free guest access extra field 1 validation: Validation rule for the first additional field to ensure data is entered.
  Example: "You must enter an answer"
  
  

• Free guest access extra field 2 label: Label for the second additional field where guests can enter information.
  Example: "Custom Field 2"
  
  

• Free guest access extra field 2 validation: Validation rule for the second additional field to ensure data is entered.
  Example: "You must enter an answer"
  
  

• Free guest access extra field 3 label: Label for the third additional field where guests can enter information.
  Example: "Custom Field 3"
  
  

• Free guest access extra field 3 validation: Validation rule for the third additional field to ensure data is entered.
  Example: "You must enter an answer"
  
  

• Free guest access password label: Label for the password field, if password protection is used.
  Example: "WiFi Password"
  
  

• Free guest access password validation: Validation rule for the password field to ensure it is provided.
  Example: "You must enter an answer"
  
  

• Free guest access password: The actual password required to access the network. This value needs to match the user input. 
  Example: "12345678"
  
  

• Invalid password text: Message displayed if the entered password is incorrect.
  

  Example: "Wrong password."
  
  

Any non-required extra fields that are left empty will be automatically hidden. To create a "Click and Connect" experience using a "Connect to WiFi" button, leave all fields and the password empty. 

Voucher Authentication

Voucher Authentication requires users to log in with a pre-defined username and password. This method is suitable for manual management of access credentials, allowing for straightforward voucher creation and distribution. It also supports automated processes and integration with third-party systems via API. 

Fields:

• Order Priority: Defines the placement of this form on the page. The forms are displayed in ascending order based on their priority value. For example, if this form has an order priority of 1, it will be shown first. If it has an order priority of 10, it will be shown last. This is useful when multiple forms are used, ensuring a structured and user-friendly layout.
  

• Title: The title for the voucher authentication method.
  Example: "Connect with your Personal Code"
  
  

• Main Text: Instructions for users on how to use their voucher credentials.
  Example: "Enter your username and password to connect to our service."
  
  

• Username Label: Label for the field where users enter their username.
  Example: "Username"
  
  

• Username Validation: Validation message if the username field is left blank.
  Example: "Please enter your username."
  
  

• Password Label: Label for the field where users enter their password.
  Example: "Password"
  
  

• Password Validation: Validation message if the password field is empty.
  Example: "Please enter your password."
  
  

• Invalid Username Text: Error message displayed if the entered username is incorrect.
  Example: "The username you entered is incorrect."
  
  

• Invalid Password Text: Error message shown when the password is incorrect.
  Example: "The password you entered is incorrect."
  
  

• Expired or Not Valid Username Text: Message indicating that the user’s credentials are no longer valid.
  Example: "Your credentials have expired or are invalid."
  
  

• Require Only Username:  This checkbox specifies whether only the username is required for authentication, omitting the need for a password. When selected, users will only need to enter their username to gain access, simplifying the login process and eliminating the password field.

Voucher Manager App is used to manage the Vouchers.

This method is ideal for managed voucher access, whether through manual voucher creation or integration with systems like payment portals, PMS systems, booking engines, or CRM platforms.

Paid Access 

The Paid Access Button redirects users to an integrated payment portal where they can purchase pre-defined internet access plans, whether quota-based or time-based.

Requirements to use this feature:
1. Voucher Authentication must be enabled (it is part of Voucher Authentication)
2. A PayPal business account to process payments
3. Allow direct access to PayPal CDNs in "Guest Network > Walled Garden" page (required in some countries)

Fields:

• Title: The title for the paid access option.
  Example: "Connect with Paid Access"
  
  

• Main Text: Instructions on using PayPal to make a payment.
  Example: "Use your PayPal account to pay for internet access."
  
  

• Button Text: The text on the button users click to proceed with payment.
  Example: "Pay Now"
  

This method is useful for charging for internet access in locations using satellite or LTE connections, or for any time-based or data quota plans.

2. Login methods that collect User Data

The login methods listed in this section may collect or process user-related data, depending on the selected method and operator configuration.

To enable any of these methods, the administrator must explicitly acknowledge responsibility for data collection, transparency, retention, and security configuration. These methods are available only over HTTPS connections. If secure access is not available, they cannot be enabled.

Before activating any data-collecting login method, ensure that your guest-facing Terms & Privacy notice is properly configured and clearly informs users about data collection and processing. This can be managed under the Terms & Privacy page.

Operator Responsibility Notice

By enabling login methods that collect or process user-related data, the operator acts as the data controller and is responsible for:

• Selecting the appropriate login methods

• Enabling or disabling optional data fields

• Defining data retention and deletion policies using tools such as System > Data Retention

• Ensuring compliance with applicable privacy and data protection laws and regulations

Facebook Login Authentication 

Allows guests to authenticate using their Facebook account. Authentication is performed via a Facebook application and requires explicit user consent.

NOTE: This feature is currently unavailable and will be restored on future software updates.

When enabled, authentication will be performed directly between the guest and Facebook using the operator’s own application credentials. Depending on Facebook permissions granted by the user, limited profile information may be returned solely for authentication purposes.

Fields:

• Order Priority: Defines the placement of this form on the page. The forms are displayed in ascending order based on their priority value. For example, if this form has an order priority of 1, it will be shown first. If it has an order priority of 10, it will be shown last. This is useful when multiple forms are used, ensuring a structured and user-friendly layout.
  
  
• Facebook login title: This field defines the title or prompt that appears to the guest for accessing the network via Facebook.
  Example: "Facebook Login"
  
  
• Facebook login submit button: This field sets the text for the button that users click to log in with Facebook.
  Example: "Log in with Facebook"
  
  
• Facebook login text: This field provides additional instructions or information to the guest about the Facebook login process.
  Example: "Use your existing Facebook account to connect to our network.."

Email Connect

Email Connect prompts users to enter their email address to gain Internet access. The email address is stored locally as an authentication identifier. Optional extra fields are stored only if enabled by the operator.

Fields:

• Order Priority: Defines the placement of this form on the page. The forms are displayed in ascending order based on their priority value. For example, if this form has an order priority of 1, it will be shown first. If it has an order priority of 10, it will be shown last. This is useful when multiple forms are used, ensuring a structured and user-friendly layout.
  
  

• Email connect title: The title or prompt displayed to users for accessing the network via email.
  Example: "Connection via Email"
  
  

• Email connect text: Provides instructions or information to users about using their email address to connect.
  Example: "Use your email address to get connected to our network."
  
  

• Email extra field 1 label: Label for the first additional field where users can enter information.
  Example: "Custom Field 1"
  
  

• Email extra field 1 validation: Validation rule for the first additional field to ensure data is entered.
  Example: "You must enter an answer"
  
  

• Email extra field 2 label: Label for the second additional field where users can enter information.
  Example: "Custom Field 2"
  
  

• Email extra field 2 validation: Validation rule for the second additional field to ensure data is entered.
  Example: "You must enter an answer"
  
  

• Email extra field 3 label: Label for the third additional field where users can enter information.
  Example: "Custom Field 3"
  
  

• Email extra field 3 validation: Validation rule for the third additional field to ensure data is entered.
  Example: "You must enter an answer"
  
  

• Email connect label: Label for the email address field.
  Example: "Email address"
  
  

• Email connect validation: Validation rule to ensure the email address is valid.
  Example: "You must enter a valid email address"
  
  
• Require OTP Email Verification: If enabled, an OTP (One-Time Password) will be sent to the email address that the user provided for verification before access is granted. Useful for stricter access control and logging.
  
  

  Requirements to use OTP feature:
  SMTP Outgoing server must be configured in Campaigns > Connectivity Settings.

This method is ideal for scenarios where you want to provide free access while storing email addresses for authentication, operational, or operator-defined purposes. Any non-required extra fields that are left empty will be automatically hidden.

Mobile/SMS Authentication

Allows users to log in by entering their mobile phone number. They receive a one-time password (OTP) via SMS, which they must enter on the validation page to gain access. The mobile number is stored locally as an authentication identifier. Optional extra fields are stored only if enabled by the operator.

Requirements to use the Mobile Login feature:
An account with an third-party SMS provider such as SMS Global or Clickatell is required.

Fields:

• Order Priority: Defines the placement of this form on the page. The forms are displayed in ascending order based on their priority value. For example, if this form has an order priority of 1, it will be shown first. If it has an order priority of 10, it will be shown last. This is useful when multiple forms are used, ensuring a structured and user-friendly layout.
  
  

• SMS Authentication Title: The title for the SMS authentication option.

  Example: "Connect with Your Mobile"
  
  

• SMS Authentication Main Text: Instructions for using a mobile phone number to receive an OTP and gain access.

  Example: "Enter your phone number to receive an OTP and access the network."
  
  

• Mobile Label Text: Label for the field where users enter their mobile phone number.

  Example: "Enter your mobile number"
  
  

• Mobile Validation Text: Validation rule for the mobile phone number field.

  Example: "Please enter your mobile phone number."
  
  

• SMS Spam Protection Text: Message displayed if the user attempts to receive an OTP too frequently.

  Example: "Please try again later!"
  
  

• Mobile Extra Field 1 Label: Label for the first additional field where users can enter information.

  Example: "Custom Field 1"
  
  

• Mobile Extra Field 1 Validation: Validation rule for the first additional field.

  Example: "You must enter an answer."
  
  

• Mobile Extra Field 2 Label: Label for the second additional field where users can enter information.

  Example: "Custom Field 2"
  
  

• Mobile Extra Field 2 Validation: Validation rule for the second additional field.

  Example: "You must enter an answer."
  
  

• Mobile Extra Field 3 Label: Label for the third additional field where users can enter information.

  Example: "Custom Field 3"

   

• Mobile Extra Field 3 Validation: Validation rule for the third additional field.

  Example: "You must enter an answer."

3. Page Texts

On this tab, administrators can edit the title of the Authentication page and its main content using an HTML Editor. With the HTML Editor, they can also add external content, links, and other elements to customize the page further. This flexibility allows administrators to customize the page's appearance and functionality to meet specific needs and preferences.

4. Auto Login

This tab allows administrators to manage settings related to user login data retention and auto-login features.

• Remember User Login Data: Enabling this feature ensures that guests who have previously logged in using Free Guest Access, Email Connect, Facebook Login, or Mobile Authentication are not prompted to re-enter their data within the specified period.
  
  ⚠️ Note: This feature does not apply to the Voucher Login method. The "remember" feature for Voucher Guests can be managed via the Guest Network > Guest Limits page.
  
  

• Enable Auto-Login: Activating the auto-login feature allows the system to bypass the Captive Portal entirely for "known" guests, logging them in automatically. The Captive Portal page will appear briefly before closing automatically, ensuring a seamless login experience without disabling the Captive Portal.