** Changed in: webapps-core
Status: Fix Committed => Fix Released
** Changed in: webbrowser-app (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: webapps-sprint
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member
** Changed in: webapps-core
Status: In Progress => Fix Committed
** Changed in: webapps-sprint
Status: In Progress => Fix Committed
** Changed in: webbrowser-app (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
** Changed in: webapps-sprint
Milestone: sprint-17 => sprint-18
--
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
Just to keep track of them, I entered
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1522585
to address the misleading error messages.
And
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1522562
as a workaround to help get the applications' state back to normal.
*
** Changed in: webapps-sprint
Milestone: sprint-16 => sprint-17
** Changed in: webapps-core
Status: New => In Progress
** Changed in: webapps-sprint
Status: New => Triaged
** Changed in: webapps-sprint
Status: Triaged => In Progress
** Changed in: webbrowser-app (Ubuntu
** Attachment added: "com.ubuntu.developer.webapps.webapp-gmail.conf"
https://bugs.launchpad.net/webapps-core/+bug/1517102/+attachment/4527737/+files/com.ubuntu.developer.webapps.webapp-gmail.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Actually, disregard my last comment: those error messages are quite
misleading, but they don't point at a real error: they'll also be
emitted when there are no URL patterns stored in the config file.
Pat, could you please paste your ~/.config/com.ubuntu.developer.webapps
.webapp-gmail/com.ubuntu.d
One thing that we noticed while reproducing this bug is that sometimes the URL
patterns are not updated:
qml: SAML request detected. Adding host pattern: https?://login\.ubuntu\.com/*
qml: Invalid JSON content found in url patterns file
qml: Invalid JSON content type found in url
A few more observations from our debug session.
I can reproduce the issue with a backup of my tokens. I had removed
.local/share/com...webapp-gmail, and once restarting Gmail the app was starting
straight on the login.ubuntu.com page, asking for my user/pass.
The issue is that after validating c
What I observed with a set of old tokens is that our own (canonical.com)
token renewal process gets ejected into the browser. The redirects are part
of the SAML / 3rd party auth. process, but not all of it is trapped
unfortunately.
Eventually, after restarting the webapp 3 times to finalize the pro
I created
https://bugs.launchpad.net/webapps-core/+bug/1517527
to cover the google.co.* case
--
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 successfu
Nothing changed, just that the pattern is found in the Exec line and I
think might be a left over from an earlier version (or just a mistake),
it was never an allowed form. For google, we allow e.g. www.google.*
where the * is expanded to [^\\./] after but google.co.* is not a valid
pattern (which
Did that pattern acceptance change, or what is the correct form? This would
be a good explanation for some of the re-authentication process to be
ejected into the browser, and break.
On Wed, Nov 18, 2015 at 3:41 PM, Alexandre Abreu <
alexandre.ab...@canonical.com> wrote:
> This log
>
> Ignoring e
This log
Ignoring empty or invalid webapp URL pattern:
"https?://accounts.google.co.*/*"
is a no-op, it "just" means that one of the patterns specified in the
command line is invalid (which it is and should be updated),
Could you also attach the content of :
~/.config/com.ubuntu.developer.weba
I'm afraid that the attached logs are not relative to the first
execution of the webapp, where the SAML login is performed.
#1 We do have this already, it's just a matter of copying the ~/.cache
/online-accounts-ui/id-* files and restoring them.
#2 We also have useful debugging messages (and inde
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
** Summary changed:
- Gmail webapp account setup not successful
+ Gmail webapp account renewal not successful
--
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 renew
17 matches
Mail list logo
