This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
user_guide:user_registration_api [2021/02/08 05:13] – [Introduction] admin | user_guide:user_registration_api [2021/02/08 10:14] (current) – [Finding the login_page_id] admin | ||
---|---|---|---|
Line 2: | Line 2: | ||
===== Introduction ===== | ===== Introduction ===== | ||
* This document is applicable to the Git version of RADIUSdesk (2021Version) | * This document is applicable to the Git version of RADIUSdesk (2021Version) | ||
- | * To interact with the API of RADIUSdesk you will need an API key. | + | |
- | * Each Access Provider registered on the system has a unique API key. | + | |
+ | * Select a login page and click **Edit** | ||
+ | * At the bottom of the **Settings** sub-tab is a **Registration** tab. | ||
+ | * There you can enable and fine tune it for the specified login page. | ||
+ | |||
+ | ===== API ===== | ||
+ | ==== API URL ==== | ||
+ | * We assume the FQDN of the RADIUSdesk | ||
+ | * http:// | ||
+ | |||
+ | ==== Items included in the POST ==== | ||
+ | |||
+ | * Let us take a look at the items submitted to the back-end when a user registers and then discuss important items in that list. | ||
+ | |||
+ | <code javascript> | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | ^ Item ^ Typical Value ^ Comment | ||
+ | | mac | 28-D2-44-20-AA-00 | ||
+ | | login_page | ||
+ | | login_page_id | ||
+ | | name | Dirk | ||
+ | | surname | ||
+ | | username | ||
+ | | password | ||
+ | | phone | 0721235555 | ||
+ | |||
+ | ==== Finding the login_page_id ==== | ||
+ | * See the following screenshot to get to the login_page_id | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | * The first hidden column contains the value of login_page_id. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== A Word On The MAC Address ==== | ||
+ | |||
+ | * The MAC Address is the MAC address from the WiFi interface of the device that the user will connect with to the Captive Portal. | ||
+ | * When we use the login page to do the user registration we can extract it from the detail provided to us by CoovaChilli typically. | ||
+ | * When we create something like a mobile app and want to allow someone to register **without being connected to the Captive Portal**, we can still supply the MAC address of the device using the app. | ||
+ | * Here is some info on how to get it programmatically: | ||
+ | |||
+ | ==== Reply - Success ==== | ||
+ | |||
+ | * This is typically what a successful reply will look like | ||
+ | <code javascript> | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | ==== Reply - Failure ==== | ||
+ | * This is a typical message if someone tries to register twice from the same device | ||
+ | <code javascript> | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | } | ||
+ | </ | ||