Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| radius:login_dynamic_keys [2024/02/13 14:14] – created system | radius:login_dynamic_keys [2024/02/13 14:28] (current) – system | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| <nav type=" | <nav type=" | ||
| * [[: | * [[: | ||
| - | * [[:radius:rad_kick|Dynamic Keys]] | + | * [[:radius:login_dynamic_keys|Dynamic Keys]] |
| </ | </ | ||
| ----- | ----- | ||
| + | |||
| + | ====== Dynamic Keys ====== | ||
| + | ===== Introduction ===== | ||
| + | * One of the most powerful features of login pages are the dynamic keys. | ||
| + | * Unfortunately, | ||
| + | * This special wiki page aims to clarify the aspects surrounding dynamic keys. | ||
| + | |||
| + | ===== Login Page URL ===== | ||
| + | ==== Coova Chilli ==== | ||
| + | * When you connect to a captive portal based on Coova Chill, you will be redirected to the UAM URL. | ||
| + | * Coova Chilli does this automatically and also formulates the query string that is automatically appended to the UAM URL. | ||
| + | * The components and values of the query string are largely determined by Coova Chili' | ||
| + | * Here is an example of the login page with its query string. | ||
| + | * https:// | ||
| + | * For example, with the Coova Chili configuration we have | ||
| + | * nasid = our_internet_cafe_mcp34 | ||
| + | * ssid = our_internet_cafe | ||
| + | * Some settings must be unique for the Coova Chili instance, e.g. nasid. | ||
| + | * Other settings can be more general and shared by several Coova Chili instances, e.g. ssid. | ||
| + | * If our login page has not yet been configured with dynamic keys, you will see the following screen. | ||
| + | |||
| + | <panel type=" | ||
| + | {{: | ||
| + | </ | ||
| + | |||
| + | ==== Mikrotik ==== | ||
| + | * Mikrotik Hotspots work more or less in a similar way. | ||
| + | * If you configure the Mikrotik to use a central login page the replacement login.html page will look something like this | ||
| + | <code html> | ||
| + | < | ||
| + | <form name=" | ||
| + | <input type=" | ||
| + | <input type=" | ||
| + | <input type=" | ||
| + | <input type=" | ||
| + | <input type=" | ||
| + | <input type=" | ||
| + | <input type=" | ||
| + | <input type=" | ||
| + | <input type=" | ||
| + | </ | ||
| + | <script language=" | ||
| + | <!-- | ||
| + | | ||
| + | //--> | ||
| + | </ | ||
| + | </ | ||
| + | * Here the Mikrotik will POST some additional data to the CakePHP controller which the controller can then use. | ||
| + | * With Mikrotik, you have more control over the elements that are included in the POST. | ||
| + | * You can even specify your own elements with the values you want. | ||
| + | * Like the Coova Chili pages, the Mikrotik also displays a list of available elements if the dynamic keys have not yet been configured. | ||
| + | |||
| + | |||
| + | ===== Connecting a Login Page with Captive Portal ===== | ||
| + | * The dynamic keys are used by RADIUSdesk to determine which login page should be served. | ||
| + | * You can use any of the listed elements and add it as a dynamic key to a login page | ||
| + | * Login pages can also contain several dynamic keys. | ||
| + | * For example, if you have a very specific login page that should only be displayed by a specific captive portal, you can use the nasid. | ||
| + | * If, on the other hand, you have a hotel chain and want to use the same page on ALL captive portals of these hotels, you can use a more general element, e.g. ssid. | ||
| + | * You can also combine them without any problems. | ||
| + | <panel type=" | ||
| + | {{: | ||
| + | </ | ||
| + | |||
| + | ===== A final word about Coova Chilli ===== | ||
| + | * You may have noticed that the example URL for the login page we have provided for Coova Chili is different from the typical URL we provide as the UAM URL. | ||
| + | * The typical one is: https:// | ||
| + | * What then happens behind the scenes is that the CakePHP controller redirects to the final login page. | ||
| + | * This location is determined by the value of the page's theme. | ||
| + | * The controller also appends the language component to the query string of the URL, e.g. i18n=fr_FR, so that the page is displayed in French. | ||
| + | |||