Here you can adjust the appearance of all the different aspects of your HSMX Gateway.
Deprecated in HSMX 5 A logout console is a small popup that guests will see when they login. A logout console can show the remaining time and volume and has a logout button. The logout console needs to be enabled in the (portal page) rules. There are two types of log-out consoles:
Deprecated in HSMX 5 The logout page is a page where the client will be redirected to after they logout. Upload a ZIP archive that contains “index.html”
Here is a list of all portal pages, they can be edited or deleted. In the navigation bar there is an icon to create a new portal page. The portal page rules determine which portal will be displayed to the client. Depending on the type of portal, the portal can be uploaded or a SFTP account can configured to upload the portal to the HSMX gateway.
There are five types of portal pages:
Registration forms are used by subscribers to register themselves into the system and (generally) receive a free billing plan. The registration form can be used in combination with OAuth / Social media websites and SMS.
The captive portal needs to support registration forms and uses the ordering to assign identifiers to each registration form. The first entry refers to ID 1, the second to ID 2 and so on.
With this option enabled, guests will always be redirect to the billing plan page even if they already possess a valid billing-plan.
Send predefined e-mail to a subscriber upon account creation. Enable it independently for vouchers and/or credit-card authorizations.
Registration forms can be used to create accounts on the portal and capture data while doing so! The registration form needs to be enabled while editing the portal page and the portal page needs to have the registration logic (portals created by the portal editor are already compatible with the latest features).
These fields will be showed on the portal page and stored in the database. Placeholder and HTML5 validation are both HTML5 depended and will thus not work if the browser has no support for it.
The validate option has the following options:
Checkbox(for custom fields create-custom-fields):
CheckedThe field needs to checked to validate
UncheckedThe field needs to unchecked upon submission for validation
Defines the system auto-generated username and password if registration is successful.
! Username will be ignored when voucher code only is enabled.
As additional option you can enable oauth. This is a framework being used to support third party login details (Facebook, Twitter, …). With this option enabled the system will redirect you to another portal (for instance Facebook login) to complete registration. The system is also capable of fetching user info from this third party (like e-mail, if the software allows it).
OAuth is an open protocol to allow secure authorization in a simple and standard method from web, mobile and desktop applications. Profiles for major social websites are available where only the client secret and client Id are missing. These values (together with the fields that can be captured, see data capturing tab) can be found when creating an APP on the third party server (Facebook, Twitter, …). To add more predefined values you can always contact support. More information regarding a manual API configuration can be found here: http://download.fdxtended.com/oauth_manual.html
The walled garden tab can be used to open a specific IP / domain for a specific amount of time to allow redirection without being validated, this is needed when redirecting the customer to, for instance, Facebook.
This section will determine what happens when registration is complete, options are:
Note: to send an e-mail, the registration form must contain the e-mail field. Similar logic applies to sending SMS (requires a phone number).
Name: name of the registration form
Visible for portal use: make the registration form visible for portals
Visible for admin interface: adds the registration form to web management interface (registration form will be ignored if authentication method is set to “no username”)
Portal session error
When cookies are enabled, the portal session error shows up when multiple portal sessions are done with the same sessionid (e.g. multiple tabs in browser).
Templates that will be selected in the admin interface, you can change the template at any time when creating accounts.
With this enabled the system will set the password equal to the username.
Configure the password policy being used on the portal page, password policies can be used to make password changes mandatory and avoid password recycling by users.
Templates are used for vouchers, invoices and reload cards. The overview provides a list of current installed templates.
You can also create a template using the build-in text editor. To start press the create icon in the top-right corner and choose a name, template type and the height/width (in millimeter) of your new template. An WYSIWYG editor will load and allow you to modify the template, once done click Add.
You can delete a template using delete button in the Templates overview. To resume editing, click the edit button on the right side of the row. When trying to edit a default template a page will be shown that allows you to change the template name or download it in RTF format.
Templates created with the build-in text editor will generate PDF files when creating vouchers, whereas uploaded templates will give you an RTF file upon usage.
Note: When Voucher Code Only is enabled use variable
||user|| to print the voucher code and not