Differences

This shows you the differences between two versions of the page.

--- radius:login_ctc [2024/02/13 14:33] – created system
+++ radius:login_ctc [2024/02/13 15:17] (current) – [The Click to connect profile] system
@@ Line 8: / Line 8: @@
 ====== Click To Connect ======
 ===== Introduction =====
-  * The Login Pages include a function called **Click To Connect**
+  * The login pages contain a function called Click To Connect.
-  * The idea behind this functionality is to make it **as easy possible** for the user of the captive portal to get Internet access.
+  * The idea behind this feature is to make it as easy as possible for the Captive Portal user to get internet access.
-  * We do however also have two variants to the standard functionality.
+  * However, we also have two variants of the standard functionality.
-        * Agree to T&C first. (This is specified under the **Settings** tab.)
+        * First agree to the terms and conditions. (This is set under the Settings tab)
-        * Collect customer data first. The fields and whether they are compulsory are all configurable.
+        * First enter the customer data. The fields and whether they are mandatory are all configurable.
-===== The Click To Connect Profile =====
+===== The Click to connect profile =====
-  * The Click-To-Connect button makes use of a Permanent User behind the scenes to connect to the Internet.
+  * The Click-To-Connect button uses a permanent user behind the scenes to connect to the Internet.
-  * Given the fact that the user will be getting Internet access we have to be very careful in associating a profile to this user that serve its purpose.
+  * Considering the fact that the user is given internet access, we need to be very careful when assigning a profile to this user that fulfills its purpose.
-  * It will typically be a profile with
+  * As a rule, it will be a profile with
       * A daily reset.
       * A data limit per day.
       * A bandwidth limit.
-      * **Restriction must be per device**
+      * **The restriction must apply per device**
-<WRAP center round important 90%>
+<alert type="warning">
-Remember to include the per device restriction when defining the profile that will be used by the Click To Connect user.
+Remember to include the per-device restriction when defining the profile to be used by the Click To Connect user.
-</WRAP>
+</alert>
 ===== The Click To Connect User =====
-  * After you created the profile for the Click To Connect Permanent User you can now create the Permanent User.
+  * Once you have created the profile for the permanent Click To Connect user, you can now create the permanent user.
-  * The full username will be formulated by the Login Page and has the following convention
+  * The full user name is formulated from the login page and has the following convention
-        * First part of the username is **click_to_connect**.
+        * The first part of the username is **click_to_connect**.
-        * Then there is the @suffix. e.g. click_to_connect@our_internet_cafe.
+        * Then comes the @suffix. e.g. click_to_connect@our_internet_cafe.
         * The password MUST be **click_to_connect**.
-  * The suffix is typically added automatically based on the settings of the Realm the Permanent User belongs to.
+  * The suffix is usually added automatically, based on the settings of the realm to which the permanent user belongs.
 <panel type="primary">
@@ Line 39: / Line 39: @@
 </panel>
-  * We now thus assume we have created a Permanent User called **click_to_connect@our_internet_cafe** with the password of **click_to_connect**.
+  * So we assume that we have created a permanent user named **click_to_connect@our_internet_cafe** with the password **click_to_connect**.
 ===== Configuring Click to Connect =====
-  * Now that we have created
+  * Now that we have created the following
-        * A Profile for the Click To Connect Permanent User
+        * A profile for the permanent Click To Connect user
-        * The Click To Connect Permanent User.
+        * The permanent Click To Connect user.
-  * We can configure the Click To Connect Function.
+  * We can configure the Click To Connect function.
 <panel type="primary">
@@ Line 51: / Line 51: @@
 </panel>
-  * One item that needs our attention is the **Add suffix of** option.
+  * One point that requires our attention is the **Add suffix of** option.
   * In our case it is specified as **ssid**.
-  * What will happen then on the Login Page is that the **value** of the **ssid** item for the Login Page's query string will be taken and appended to the **Connect as**.
+  * On the login page, the **value** of the **ssid** element is then taken from the query string of the login page and appended to the **Connect as**.
-  * In our case the query string contains **.... ssid=our_internet_cafe....**.
+  * In our case, the query string contains **….... ssid=our_internet_cafe…...**
-  * This will thus result in a username: click_to_connect@our_internet_cafe with password click_to_connect to be used behind the scenes when the user click on the Click To Connect button.
+  * This results in a user name: click_to_connect@our_internet_cafe with the password click_to_connect, which is used in the background when the user clicks on the Click To Connect button.
-<WRAP center round tip 100%>
+<alert type="info">
-  * Make sure the Captive Portal is configured such that one of the items in the query string will have a **value** that will match the suffix of the Click to Connect Permanent User
+  * Make sure that the captive portal is configured so that one of the elements in the query string has a value that matches the suffix of the Click to Connect Permanent User
-  * Then select that item as the **Add suffix of** option.
+  * Then select this element as the **Add Suffix Of** option.
-</WRAP>
+</alert>
-==== Why the Add suffix of option? ====
+==== Why use the Add suffix from option? ====
-  * The **Add suffix of** option allows us to be more flexible when configuring the Click To Connect button.
+  * The Add Suffix From option allows us more flexibility when configuring the Click to Connect button.
-  * One can for instance use the same Permanent User across multiple Login Pages.
+  * For example, you can use the same permanent user for multiple login pages.
-  * One can also got to the other end and use a unique user per Login Page e.g. by using a more specific item in the query string like nasid.
+  * But you can also go the other way around and use a unique user per login page, for example by using a more specific element in the query string such as nasid.
-  * It also allows us to stick to a convention across the system where the Click To Connect Permanent Users will start for **click_to_connect** and a suffix.
+  * This also allows us to follow a convention throughout the system where the permanent users for Click To Connect start with **click_to_connect** and a suffix.
-===== Collect Customer Data =====
+===== Collecting customer data =====
-  * We also include the option to collect selected information from the customers **before** giving them Internet access.
+  * We also offer the option to collect selected information from customers **before** they are given internet access.
-  * If enabled you can select the interval which the user needs to re-supply the required information.
+  * If this option is enabled, you can select the interval at which the user must provide the required information again.
-  * There are a predefined list of items you can select from and also whether an item is required.
+  * There is a predefined list of items to choose from and also whether an item is required.
-  * There are also three custom fields which you can then use to declare your own values for the text which will be displayed on the web form that the user have to complete.
+  * There are also three custom fields that you can use to specify your own values for the text that will be displayed on the web form that the user must complete.