Smart Wireless Authentication

From wiki.gpii
Revision as of 10:53, 6 November 2014 by Till (talk | contribs) (Created page with "{{Developer Space/Component| Smart Wireless Authentication| Providing seamless wireless network service is not only about network quality but also about user experience and e...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Smart Wireless Authentication

Providing seamless wireless network service is not only about network quality but also about user experience and ease of access has become an important factor for quality of life. Adding an extra burden on users – particularly technically non-literate users or ones with special needs – actually excludes many people from access, especially when using complicated username:password schemes with media breaks. As a step towards the proliferation of accessible networks, this work the usability of ways for associating handheld and personal devices to Wi-Fi networks or other infrastructures using out of band methods (such as barcodes, RF beacons, RF surfaces, gestures/movements, audio fingerprint). The system does that do not identify the user but proves his presence in an authorized area and reduces the problem from access to another better understood area of accessibility.

Keywords: authentication,wifi,HTML5,
Technologies: HTML5,javascript,PHP, OpenWRT
License: see below
FurtherInfo:, Contact

NOTE: If you find this component useful or want to comment leave a short message on the discussion page of this component

Component Description

Target Audience(s)

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.

Potential Applications

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).

Technologies used

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.

Licence Information

Currently the software reuses multiple libraries, see 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.

Further Resources

Getting Involved

Code Repository