This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 2022:bootstrap_settings [2022/06/04 15:20] – [CoovaChilli Specific Settings] admin | 2022: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 | + | * The items on the drop-down |
| - | * One of the ideas around the Login Pages is to have a common URL for the captive portal e.g. https:// | + | * One of the ideas around the Login Pages is to have a common |
| * 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 119: | Line 119: | ||
| ===== 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 added two options specific for CoovaChilli based captive portals. | ||
| - | * The one specifies that the JSON Interface is | + | * 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. | ||
| + | |||
| + | ==== 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' | ||
| + | * 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 **/ | ||
| + | * 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 | ||
| + | </ | ||
| + | * 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. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * 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. | ||
| + | |||
| + | |||