We are developing a payment/customer portal to facilitate online signup and payment of hotspot services. To this end we are developing a web portal to operate on a centralised web server. This server will also be the RADIUS server for the Hotspot service on the Mikrotik routers.
We would like to use HTTP-CHAP as client authentication as HTTP-PAP is too insecure without running SSL certificates on the hotspot HTTP server which we do not want to do.
To achieve seemless integration with the hotspot "login" servlet, we shall use a META Refresh tag in the "hotspot/login.html" file to redirect the client browser to our external central server login page (which will be in the walled garden, and also a HTTPS site). After purchasing time on the hotspot we need our central (external) web server to redirect the clients browser to "http://hotspot/login?...." providing the correct "username" and CHAP encoded "password".
I see from the Miktorik router servlet documentation (http://www.mikrotik.com/testdocs/ros/2.9/ip/hotspot.php), that we may use the variables "chap-id" and "chap-challenge". My question is, may I pass these variables as part of the initial META Refresh redirect from the hotspot servlet page (login.html) to our central portal, for use by the subsiquent redirect from the central portal back to the hotspot's login servlet? Are there any timeouts or caveats regarding the CHAP challenge I should know about?
Regards, Dan...
[/url]