Smart Wireless Authentication
NOTE: If you find this component useful or want to comment leave a short message on the discussion page of this component
The system is intergrated with a captive portal running on a standard OpenWRT based router and can be used as an appliance for any entity that wants to offer internet access but also access to any type of smart or e-inclusive environment via WiFi.
A typical use case can be e.g. a shop/restaurant that wants to offer accessible search of their catalogue/menu via a personalized device, however wants to restrict internet access to the shop area. By offering alternative methods of access in parallel, the customer can choose which mode works best for him. The system requires no further integration. We are currently evaluating the use of a system eg. with a vendor for tablet PC based menus for cafes and bars.
One application would a public display use case in combination with a mobile personalized device.
In many setting the user will already carry a device equipped with a lot of AT with him, a wearable or smartphone. If he wants to take control over a kiosk or any other kind of public interface with his personalized interface, we do not need to identify the user or load settings. The only protection in terms of personalization or manipulation of the interface is typically the queue in front of the device that ensures that only people in the correct spatial context will be able to take over control. Instead of having to search for a USB slot or a NFC reader, the offered component can actually mirror the problem towards the already personalized device (the smart phone). This also removes the need from the vendor to offer any physically accessible interfaces (like slots or readers).
The code is optimized to run on embedded routers and captive portals. It is written in HTML5 with php server components.
It is designed to integrate with PHP-based captive portals (chillispot atm) but most of the logic is HTML/JS based and can be adapted to other web-based authentication solutions, where user identity is not important.
Currently the software reuses multiple libraries, see https://github.com/teco-kit/UsableWi-FiAccess/blob/master/legal.txt for details
Status, Known Issues & Planned Work
Needs refactoring, packaging and better documentation
Only bare components:Theming/Framework integration is necessary.
Also basic accessibility improvements/auto-personalization should be considered.