Some updates:
On 11/25/2013 03:13 PM, Alberto Mardegan wrote:
There are a few ways to address this issue; I will list only the two on
the top of my head (though they are not originally mine, to be honest):
1) Until the authentication has completed, act like an ordinary web browser.
2) Delegate the authentication to Online Accounts.
We have decided to test this second option, to verify its feasibility. And:
The main question I have is: should the webapp container have only read
access to the cookies, or should we let it update them? In other words:
should we simply copy all the cookies over from OA to the webapp when it
starts (let's call this option #1), or should we also have a way for the
webapp to modify the OA cookies (option #2)?
for this, we are testing option #1; so far, it seems that there isn't a
problem with reusing the same cookies more than once, but of course this
is something which depends on the site, and can change in the future.
If you want to replicate these tests, you will need:
- the "app-access" branch of ubuntu-system-settings-online-accounts:
https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/app-access
- the "export-cookies" branch of signon-ui:
https://code.launchpad.net/~mardy/signon-ui/export-cookies
- The test code itself: https://github.com/mardy/cookie-test
