I think we need 2 things first : 1. a reliable way to reproduce the account credentials renewal process; this is where the cookie renewal happens
2. Additional logs and tools to trace down the various redirections and cookie operations that the renewal process requires 3. Once we are there, the solution should be clearer. It may take relaxing the url pattern policy even further, or manage the redirection / overlays in a different way #1 For reproducing, I think it is key to be able to store valid "old" cookies and account configurations, taken from different places in the system (the OA central base, the OA cookies, also the app cookies, the OA/app permissions), and be able to save that into an archive that can then be re-injected on a new device. Because we have to re-install our phones quite frenquently, it has been difficult to reproduce regularly, but really there is nothing preventing us from restoring cookies from 3 months ago, and get forced by Google to re-authenticate as a result. #2 For tracing the redirection and cookie operations, it will take a few more log statements. But that should be the occasion to remove the remainder of the other useless debug lines that end up in the webapp- container logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517102 Title: Gmail webapp account renewal not successful To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1517102/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
