Proxy captive portal traffic for input-limited devices
A system for re-registering an input-limited device, such as a voice-enabled device, with a captive portal access point that requires completion of a portal webpage prior to allowing client devices access to a network, such as the Internet, is described. Such captive portal access points are commonly found in hotels, and may be used for both freely provided public WiFi and for connections that require providing payment. For re-registration of the input-limited device with the captive portal access point, a server may send a notification to a mobile computing device associated with the input-limited device.
1. A first device, comprising:
at least one processor; and
at least one memory comprising instructions that, when executed by the at least one processor, cause the first device to:
receive, from a server, an indicator representing a second device can no longer communicate data with the server through a captive portal system, the second device being configured without an alphanumeric keyboard;
receive, from the second device, captive portal login webpage data associated with the captive portal system;
generate updated captive portal login webpage data including captive portal login credentials and first device identifying information; and
send the updated captive portal login webpage data to the second device, the captive portal login credentials being usable by the captive portal system to re-authenticate the second device with the captive portal system.
2. The first device of claim 1 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the first device to:
output, via a speaker component of the first device, audio representing the second device can no longer communicate data with the server through the captive portal system; and
at least partially contemporaneously with outputting the audio, present visual content representing the second device can no longer communicate data with the server through the captive portal system.
3. The first device of claim 1 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the first device to:
after receiving the indicator, determine that the first device was used to previously authenticate the second device with the captive portal system.
4. The first device of claim 1 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the first device to:
prior to receiving the indicator, receive, from the server, a second indicator representing when the second device is to be re-authenticated with the captive portal system.
5. The first device of claim 1 , wherein the indicator includes captive portal network information and captive portal login information.
6. The first device of claim 1 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the first device to:
based at least in part on receiving indicator, establish a wireless connection with the second device.
7. The first device of claim 1 , wherein the indicator includes service set identifier (SSID) information associated with the captive portal system.
8. The first device of claim 1 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the first device to:
after receiving the indicator, identify the second device using a local network to which the first device and the second device are both connected.
9. A method, executable by a first device, comprising:
receiving, from a server, an indicator representing a second device can no longer communicate data with the server through a captive portal system, the second device being configured without an alphanumeric keyboard;
receiving, from the second device, captive portal login webpage data associated with the captive portal system;
generating updated captive portal login webpage data including captive portal login credentials and first device identifying information; and
sending the updated captive portal login webpage data to the second device, the captive portal login credentials being usable by the captive portal system to re-authenticate the second device with the captive portal system.
10. The method of claim 9 , further comprising:
outputting, via a speaker component of the first device, audio representing the second device can no longer communicate data with the server through the captive portal system; and
at least partially contemporaneously with outputting the audio, present visual content representing the second device can no longer communicate data with the server through the captive portal system.
11. The method of claim 9 , further comprising:
after receiving the indicator, determining that the first device was used to previously authenticate the second device with the captive portal system.
12. The method of claim 9 , further comprising:
prior to receiving the indicator, receiving, from the server, a second indicator representing when the second device is to be re-authenticated with the captive portal system.
13. The method of claim 9 , wherein the indicator includes captive portal network information and captive portal login information.
14. The method of claim 9 , further comprising:
based at least in part on receiving the indicator, establishing a wireless connection with the second device.
15. The method of claim 9 , wherein the indicator includes service set identifier (SSID) information associated with the captive portal system.
16. The method of claim 9 , further comprising:
after receiving the indicator, identifying the second device using a local network to which the first device and the second device are both connected.