Differences

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

Link to this comparison view

Next revision		 Previous revision
radius:login_settings [2024/02/13 08:19] – created systemradius:login_settings [2024/02/13 15:18] (current) – [User Registration With Top-Up Profile] system
Line 28: Line 28:
   * This function is useful for sites where a permanent user registers by entering their email address and password.   * This function is useful for sites where a permanent user registers by entering their email address and password.
   * When the permanent user is created (provided the settings on the realm are so), a suffix is added.   * When the permanent user is created (provided the settings on the realm are so), a suffix is added.
 +<panel type="primary">
 {{:radius:login_pages:realm_suffix.png|}} {{:radius:login_pages:realm_suffix.png|}}
- +</panel> 
-  * Thus you will have a username like dirk@gmail.com@our_internet_cafe. +  * This will give you a username like dirk@gmail.com@our_internet_cafe. 
-  * Specifying the **Auto-add Suffix** as **our_internet_cafe** will then automatically append that value to the username supplied by the user. +  * If you specify the auto-add suffix as **our_internet_cafe**, this value is automatically appended to the user name specified by the user. 
 +<panel type="primary">
 {{:radius:login_pages:username_suffix.png|}} {{:radius:login_pages:username_suffix.png|}}
-  * They then simply have to remember their email address and the password they choose.+</panel> 
 +  * He then only has to remember his email address and the password he has chosen.
  
 ===== Sending Email ===== ===== Sending Email =====
-  * There are two places where the system can send the user an email through a Login Page. +  * There are two places where the system can send the user an email via a login page. 
-        * The Lost Password option. +        * The lost password option. 
-        * The User Registration option. +        * The User registration option. 
-  * Remember **you first have to configure the system with valid email settings** for this to work.+  * Remember that you must first configure the system with valid email settings for this to work. 
 +<panel type="primary">
 {{:radius:login_pages:email_settings.png|}} {{:radius:login_pages:email_settings.png|}}
 +</panel>
  
 ===== T&C URL ===== ===== T&C URL =====
-  * For T&C you can specify a URL +  * You can specify a URL for T&C 
-  * Remember if this URL is located on another server, you have to add an entry to the Walled Garden of the Captive Portal for the user to reach this URL.+  * Remember, if this URL is on a different server, you will need to include an entry in the Captive Portal walled garden for the user to reach this URL.
  
-===== Show Usage ===== +===== Show usage ===== 
-  * There is an option where the page can display the usage to a user after they connected.+  * There is an option that allows the page to show usage to a user after they have connected.
   * This is handy for a voucher based system or a system that uses permanent users with top-ups.   * This is handy for a voucher based system or a system that uses permanent users with top-ups.
 +<panel type="primary">
 {{:radius:login_pages:usage_included.png|}} {{:radius:login_pages:usage_included.png|}}
 +</panel>
 ===== Support for Arabic ===== ===== Support for Arabic =====
   * Support for Arabic is now also included.   * Support for Arabic is now also included.
-  * There are however a small tweak you should do for it to work in an optimal way. +  * However, there is one small change you should make to make the system work optimally. 
-  * Edit the /var/www/html/login/bootstrap5/index.html page. +  * Edit the page ///var/www/html/login/bootstrap5/index.html//. 
-  * Remove the default Bootstrap 5 Stylesheet.+  * Remove the default Bootstrap 5 stylesheet.
 <code html> <code html>
 <!--Comment the line below out if you are planning to implement languages including Arabic--> <!--Comment the line below out if you are planning to implement languages including Arabic-->
 <!--<link href="css/bootstrap.min.css" rel="stylesheet">--> <!--<link href="css/bootstrap.min.css" rel="stylesheet">-->
 </code> </code>
-  * Activate the inclusion of it in JavaScript (towards the bottom of the index.html page)+  * Activate the inclusion of it in JavaScript (at the bottom of the index.html page)
 <code javascript> <code javascript>
 if(i18n == 'ar_AR'){ if(i18n == 'ar_AR'){
Line 74: Line 78:
     }).appendTo('head');                   }).appendTo('head');              
 }else{ }else{
-    //Normal Stylesheet (if you did comment out the normal Bootstrap stylesheet - activate this section for non-arabic languages+    //Normal Stylesheet (if you have commented out the normal Bootstrap stylesheet - activate this section for non-Arabic languages
          
     $('<link/>', {     $('<link/>', {
Line 84: Line 88:
 } }
 </code> </code>
-  * This tweak will allow the RTL and normal stylesheet to co-exist thus allowing you to serve pages in Arabic and other languages. +  * This tweak allows RTL and normal stylesheet to coexist, so you can output pages in Arabic and other languages. 
-  * Not doing the tweak will have a restricted effect on the RTL styling.+  * If you do not perform this tweak, RTL styling will be restricted.
  
 ===== User Registration With Top-Up Profile ===== ===== User Registration With Top-Up Profile =====
-  * When you enable user registration for a login page you have to specify the **Realm** and the **Profile** the newly registered user will belong to. +  * When you enable user registration for a login page, you must specify the realm and profile to which the newly registered user will belong. 
-  * One popular option is to choose a Data Top-Up type of profile. +  * A popular option is to choose a profile of the Data Top-Up type. 
-  * If you choose such a profile it is very important to give the user its first Top-Up value in order to impose a limit to the data the user can use.+  * If you choose such a profile, it is very important to assign an initial top-up value to the user in order to limit the data that the user can use. 
 + 
 +<alert type="warning">
  
-<WRAP center round important 90%> +If you do not specify an initial top-up value, the user may be able to use unlimited data. 
-Not adding an initial Top-Up will potentially give the user unlimited data usage +</alert> 
-</WRAP> +  * The file **/var/www/cake3/rd_cake/src/Controller/RegisterUsersController.php** contains a section that you can enable to automatically add the first top-up for you when the user registers. 
-  * The **/var/www/cake3/rd_cake/src/Controller/RegisterUsersController.php** file has a section which you can activate which will automatically add the initial Top-Up for you when the user registers. +  * Simply change **$add_topup = true;** and specify the value of the first top-up
-  * Simply change **$add_topup = true;** and specify the value of the initial Top-Up+
 <code php> <code php>
 //============== SMALL HACK 26 MAY 2022 =============== //============== SMALL HACK 26 MAY 2022 ===============
Line 124: Line 129:
  
  
-===== CoovaChilli Specific Settings ===== +===== CoovaChilli-specific settings ===== 
-  * As of June 2022 we added two options specific for CoovaChilli based captive portals. +  * As of June 2022, we have added two options that apply specifically to CoovaChilli-based captive portals. 
-  * The one can specify if the JSON Interface is **not to be used** (for whatever reason e.g. it might not be compiled with this option)+  * One allows you to specify whether the JSON interface **should not be used** (for whatever reason, e.g. because it cannot be compiled with this option)
   * The other option is to use **CHAP** instead of PAP.   * The other option is to use **CHAP** instead of PAP.
  
-==== JSON Interface Complications ==== +==== Complications with the JSON interface ==== 
-  * When you serve the Login Page from public a server with a FQDN and want to do Ajax calls to Coova Chilli's JSON interface, most modern browsers **only** allow these Ajax calls to be over HTTPS. +  * If you are serving the login page from a public server with an FQDN and want to make Ajax calls to Coova Chili's JSON interface, most modern browsers will **only** allow these Ajax calls over HTTPS. 
-  * For this then to work you need configure Coova to include HTTPS support. (Port 4990) +  * For this to work, you need to configure Coova to support HTTPS. (Port 4990) 
-  * Not all Coova Chilli instances include this support and the certificates required for this support to work correct further complicates things. +  * Not all Coova Chili instances provide this support, and the certificates required for this support to work properly make things even more complicated. 
-  * When we specify to the Login Page NOT to use the JSON Interface the login page engages **/var/www/html/login/bootstrap5/js/sConnectSimple.js** instead of **/var/www/html/login/bootstrap5/js/sConnect.js** to connect and disconnect the user. +  * If we specify on the login page NOT to use the JSON interface, the login page will fall back to **/var/www/html/login/bootstrap5/js/sConnectSimple.js** instead of **/var/www/html/login/bootstrap5/js/sConnect.js** to connect and disconnect the user. 
-  * There is however a tradeoff and the session detail will be missing after successful authentication. +  * However, there is a trade-off and the session details will be missing after successful authentication. 
-  * Use this option for devices like the **Teltonika** routers.+  * Use this option for devices such as the Teltonika routers.
  
 ==== Using CHAP instead of PAP ==== ==== Using CHAP instead of PAP ====
-  * Coova Chilli typically uses PAP authentication. +  * Coova Chili normally uses PAP authentication.. 
-  * For this to work it uses a UAM service with a UAM secret to encrypt the password. +  * For this to work, it uses a UAM service with a UAM secret to encrypt the password. 
-  * We can also opt to use CHAP instead and NOT use the UAM service. +  * You can also choose to use CHAP and NOT use the UAM service. 
-  * For this to work correct you need to leave out the UAM Secret when configuring CoovaChilli. +  * For this to work correctly, you must omit the UAM secret when configuring CoovaChilli. 
-<WRAP center round important 90%> +<alert type="warning"> 
-When you choose to use CHAP the UAM secret should be **left out** from the CoovaChilli configuration +If you decide to use CHAP, you should omit the UAM secret in the CoovaChilli configuration. 
-</WRAP> +</alert> 
-  * MESHdesk and APdesk now also allow you to leave the UAM Secret out in its configuration. +  * For MESHdesk and APdesk, you can now also omit the UAM secret in the configuration. 
-  * Also make sure your MESHdesk firmware on OpenWrt is the latest that includes this support.+  * Also make sure that your MESHdesk firmware on OpenWrt is the latest one that includes this support.
  
 {{:2022:no_uam_secret.png|}} {{:2022:no_uam_secret.png|}}
  
-  * This then brings us to the end of the discussion on the settings. +  * This brings us to the end of the discussion on settings. 
-  * Be sure to check out the other Wiki Pages that will cover other aspects of the Login Pages.+  * Be sure to check out the other wiki pages that cover other aspects of login pages.
  • radius/login_settings.1707805172.txt.gz
  • Last modified: 2024/02/13 08:19
  • by system