Revision history [back]

What I'm proposing is to improve Sailfish users' experience when connecting to the internet through a captive portal WiFi hotspot.

How I propose we do this is:

• step 1 - to have an option, when on the wifi available networks screen, and you select a certain open network for connection, an option to set this network SSID has a captive portal authentication one,
• step 2 - in which case login credentials are requested, as if the network was not open.
• step 3 - Sailfish internally opens (and keeps it open) the captive portal authentication webpage,
• step 4 - Sailfish, through scrapping, detects the login fieds and submit button on the internally open page,
• step 5 - Sailfish, automatically enters the given credentials and submits them to get proper access to the network

In case of being unsuccessfull which would be detected through failure to access some predictable web location (maybe a Jolla web-service), and only then, present the Sailfish user with the internally opened captive portal web page, for manual intervention.

If even, after manual intervention the network access is still failing, disable that network connection, so that the user knows it is not actually connected to the network.

In case of successfull connection established the credentials should be saved, just like any other closed network, and in the future automatically go through the whole login process before considering the network has connected.

• related to this (altough what I'm asking is a bit more automatic, and also that question was getting really off topic).
• also related to this (altough, that one is a bit vague, and going nowhere anytime soon)

What I'm proposing is to improve Sailfish users' experience when connecting to the internet through a captive portal WiFi hotspot.

How I propose we do this is:

• step 1 - to have an option, when on the wifi available networks screen, and you select a certain open network for connection, an option to set this network SSID has a captive portal authentication one,
• step 2 - in which case login credentials are requested, as if the network was not open.
• step 3 - Sailfish internally opens (and keeps it open) the captive portal authentication webpage,
• step 4 - Sailfish, through scrapping, detects the login fieds and submit button on the internally open page,
• step 5 - Sailfish, automatically enters the given credentials and submits them to get proper access to the network

In case of being unsuccessfull which would be detected through failure to access some predictable web location (maybe a Jolla web-service), and only then, present the Sailfish user with the internally opened captive portal web page, for manual intervention.

If even, If, even after manual intervention intervention, the network access is still failing, disable that network connection, so that the user knows it is not actually connected to the network.

In case of successfull connection established the credentials should be saved, just like any other closed network, and in the future automatically go through the whole login process before considering the network has connected.

• related to this (altough what I'm asking is a bit more automatic, and also that question was getting really off topic).
• also related to this (altough, that one is a bit vague, and going nowhere anytime soon)

What I'm proposing is to improve Sailfish users' experience when connecting to the internet through a captive portal WiFi hotspot.

How I propose we do this is:

• step 1 - to have an option, when on the wifi available networks screen, and you select a certain open network for connection, an option to set this network SSID has a captive portal authentication one,
• step 2 - in which case login credentials are requested, as if the network was not open.
• step 3 - Sailfish internally opens (and keeps it open) the captive portal authentication webpage,
• step 4 - Sailfish, through scrapping, detects the login fieds and submit button on the internally open page,
• step 5 - Sailfish, automatically enters the given credentials and submits them to get proper access to the network

In case of being unsuccessfull which would be detected through failure to access some predictable web location (maybe a Jolla web-service), and only then, present the Sailfish user with the internally opened captive portal web page, for manual intervention.

If, even after manual intervention, the network access is still failing, disable that network connection, so that the user knows it is not actually connected to the network.

In case of successfull connection established the credentials should be saved, just like any other closed network, and in the future automatically go through the whole login process internally before considering the network has connected.

Conclusion: this would make the captive portal authentication transparent to the user, which would be very practical, instead of the current upractical behaviour of needing to open the browser (and keep it open) and loging in to the web page manually!

• related to this (altough what I'm asking is a bit more automatic, and also that question was getting really off topic).
• also related to this (altough, that one is a bit vague, and going nowhere anytime soon)

What I'm proposing is to improve Sailfish users' experience when connecting to the internet through a captive portal WiFi hotspot.

How I propose we do this is:

• step 1 - to have an option, when on the wifi available networks screen, and you select a certain open network for connection, an option to set this network SSID has a captive portal authentication one,
• step 2 - in which case login credentials are requested, as if the network was not open.
• step 3 - Sailfish internally opens (and keeps it open) the captive portal authentication webpage,
• step 4 - Sailfish, through scrapping, detects the login fieds fields and submit button on the internally open page,
• step 5 - Sailfish, automatically enters the given credentials and submits them to get proper access to the network

In case of being unsuccessfull which would be detected through failure to access some predictable web location (maybe a Jolla web-service), and only then, present the Sailfish user with the internally opened captive portal web page, for manual intervention.

If, even after manual intervention, the network access is still failing, disable that network connection, so that the user knows it is not actually connected to the network.

In case of successfull connection established the credentials should be saved, just like any other closed network, and in the future automatically go through the whole login process internally before considering the network has connected.

Conclusion: this would make the captive portal authentication transparent to the user, which would be very practical, instead of the current upractical behaviour of needing to open the browser (and keep it open) and loging in to the web page manually!

• related to this (altough what I'm asking is a bit more automatic, and also that question was getting really off topic).
• also related to this (altough, that one is a bit vague, and going nowhere anytime soon)

What I'm proposing is to improve Sailfish users' experience when connecting to the internet through a captive portal WiFi hotspot.

How I propose we do this is:

• step 1 - to have an option, when on the wifi available networks screen, and you select a certain open network for connection, an option to set this network SSID has a captive portal authentication one,
• step 2 - in which case login credentials are requested, as if the network was not open.open. (which in reality is not)
• step 3 - Sailfish internally opens (and keeps it open) the captive portal authentication webpage,
• step 4 - Sailfish, through scrapping, detects the login fields and submit button on the internally open page,
• step 5 - Sailfish, automatically enters the given credentials and submits them to get proper access to the network

In case of being unsuccessfull which would be detected through failure to access some predictable web location (maybe a Jolla web-service), and only then, present the Sailfish user with the internally opened captive portal web page, for manual intervention.

If, even after manual intervention, the network access is still failing, disable that network connection, so that the user knows it is not actually connected to the network.

In case of successfull connection established the credentials should be saved, just like any other closed network, and in the future automatically go through the whole login process internally before considering the network has as connected.

Conclusion: this would make the captive portal authentication transparent to the user, which would be very practical, instead of the current upractical behaviour of needing to open the browser (and keep it open) and loging in to the web page manually!

• related to this (altough what I'm asking is a bit more automatic, and also that question was getting really off topic).
• also related to this (altough, that one is a bit vague, and going nowhere anytime soon)

What I'm proposing is to improve Sailfish users' experience when connecting to the internet through a captive portal WiFi hotspot.

How I propose we do this is:

• step 1 - to have an option, when on the wifi available networks screen, and you select a certain open network for connection, an option to set this network SSID has a captive portal authentication one,
• step 2 - in which case login credentials are requested, as if the network was not open. (which in reality is not)
• step 3 - Sailfish internally opens (and keeps it open) the captive portal authentication webpage,
• step 4 - Sailfish, through scrapping, detects the login fields and submit button on the internally open page,
• step 5 - Sailfish, automatically enters the given credentials and submits them to get proper access to the network

In case of being unsuccessfull which would be detected through failure to access some predictable web location (maybe a Jolla web-service), and only then, present the Sailfish user with the internally opened captive portal web page, for manual intervention.

If, even after manual intervention, the network access is still failing, disable that network connection, so that the user knows it is not actually connected to the network.

In case of successfull connection established the credentials should be saved, just like any other closed network, and in the future automatically go through the whole login process internally before considering the network as connected.

Conclusion: this would make the captive portal authentication transparent to the user, which would be very practical, instead of the current upractical behaviour of needing to open the browser (and keep it open) and loging in to the web page manually!

• related to this (altough what I'm asking is a bit more automatic, and also that question was getting really off topic).
• also related to this (altough, that one is a bit vague, and going nowhere anytime soon)