RADIUSdesk

Trace:

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
2022:bootstrap_settings [2022/06/04 15:24] – [CoovaChilli Specific Settings] admin2022:bootstrap_settings [2022/06/04 16:38] (current) – [Using CHAP instead of PAP] admin
Line 7: Line 7:
   * There is a special theme called **Custom** which allows you to provide your own URLs where the redirection should go.   * There is a special theme called **Custom** which allows you to provide your own URLs where the redirection should go.
   * There are also a couple of pre defined themes. Selecting one of those as a theme will redirect to the older Webix style login pages.   * There are also a couple of pre defined themes. Selecting one of those as a theme will redirect to the older Webix style login pages.
-  * The items on the drop-down is in fact defined inside the DynamicLogin.php file: https://github.com/RADIUSdesk/rdcore/blob/main/cake3/rd_cake/config/DynamicLogin.php +  * The items on the drop-down are in fact defined inside the DynamicLogin.php file in **/var/www/html/cake3/rd_cake/config/DynamicLogin.php**. 
-  * One of the ideas around the Login Pages is to have a common URL for the captive portal e.g. https://cloud.radiusdesk.com/cake3/rd_cake/dynamic-details/chilli-browser-detect/+  * One of the ideas around the Login Pages is to have a common login page URL for the captive portal e.g. https://cloud.radiusdesk.com/cake3/rd_cake/dynamic-details/chilli-browser-detect/
   * The CakePHP Controller will then determine:   * The CakePHP Controller will then determine:
         * Which login page to serve based on the value of **Theme**.         * Which login page to serve based on the value of **Theme**.
Line 121: Line 121:
   * 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)   * 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)
   * The other option is to use **CHAP** instead of PAP.   * The other option is to use **CHAP** instead of PAP.
 +
 +==== JSON Interface Complications ====
 +  * 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.
 +  * For this then to work you need configure Coova to include HTTPS support. (Port 4990)
 +  * Not all Coova Chilli instances include this support and the certificates required for this support to work correct further complicates things.
 +  * 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.
 +  * There is however a tradeoff and the session detail will be missing after successful authentication.
 +  * Use this option for devices like the **Teltonika** routers.
 +
 +==== Using CHAP instead of PAP ====
 +  * Coova Chilli typically uses PAP authentication.
 +  * 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.
 +  * For this to work correct you need to leave out the UAM Secret when configuring CoovaChilli.
 +<WRAP center round important 90%>
 +When you choose to use CHAP the UAM secret should be **left out** from the CoovaChilli configuration
 +</WRAP>
 +  * MESHdesk and APdesk now also allow you to leave the UAM Secret out in its configuration.
 +  * Also make sure your MESHdesk firmware on OpenWrt is the latest that includes this support.
 +
 +{{:2022:no_uam_secret.png|}}
 +
 +  * This then brings us to the end of the discussion on the settings.
 +  * Be sure to check out the other Wiki Pages that will cover other aspects of the Login Pages.
 +
 +
 +
  
  
Last modified: 2022/06/04 15:24