Description of problem:
When I try to add a google account to the Online Accounts of gnome3, google tells me "Action not authorized."
Version-Release number of selected component (if applicable):
Net install of x86_64 F17 beta from 03/25/12.
patrick@crudora:~$ rpm -qa|grep -i gnome-online
patrick@crudora:~$ rpm -qa|grep -i control-center
Steps to Reproduce:
1. From gnome-control-center, select "Online Account"
2. Click the plus symbol to add an account
3. Set 'Account Type' to Google and click Add...
4. Log in with google credentials
5. Click "Grant Access"
6. Google returns "Action not authorized."
Google accounts cannot be added to gnome3
Google account added!
Maybe this is a google problem, and not a gnome problem? It seems 100% repeatable for me.
Seems to work for me. Is your system time correctly set? Also can you provide a screenshot of this "Action not authorized" page?
Created attachment 572905 [details]
Screenshot of denial
The time seems to be right, as far as I can tell.
As you can see, the gnome screen shot tool included the system time (just after 10pm, EST) in the filename.
It worked fine for me in F16, too.
I'm on F17 (Just Installed) and I'm getting the same thing.
I feel like an important thing to note is that I'm using two factor authentication with a pin challenge from an Android phone.
(In reply to comment #3)
> I feel like an important thing to note is that I'm using two factor
> authentication with a pin challenge from an Android phone.
That is the catch.
GNOME Online Accounts does not support this 2 factor authentication at the moment.
I had it working in F16 with two factor. Do you know where I would look to check the status of this? I would like to use two factor authentication quite badly, however I want to see how Gnome Online accounts works.
It is working for me since updating to gnome 3.4!
Just as a note, I am also using two factor authentication, and it worked fine in f16.
Really ? Seems 2factor still not working on fully updated F17 gnome 3.4.x...
So, I dug around a bit more on this, and I don't see what we can do about it. My understanding is that the 2-factor authentication part is something that is handled completely on the server side and there isn't anything that we need to do on the client.
The fact that it works for some people and not for others, also points in this direction because I don't see what we do differently for these two sets of people. eg., some people claim it worked for them in F16 but not in F17, and some claim it the other way round (see #6).
Maybe I am misreading the documentation provided by Google, so if you think I am wrong, please let me know.
(In reply to comment #8)
> So, I dug around a bit more on this, and I don't see what we can do about
> it. My understanding is that the 2-factor authentication part is something
> that is handled completely on the server side and there isn't anything that
> we need to do on the client.
> The fact that it works for some people and not for others, also points in
> this direction because I don't see what we do differently for these two sets
> of people. eg., some people claim it worked for them in F16 but not in F17,
> and some claim it the other way round (see #6).
> Maybe I am misreading the documentation provided by Google, so if you think
> I am wrong, please let me know.
This just bit me too. The main problem was that once I'd completed the two-factor challenge, I got a modal challenge for the single-use application password, which can only be generated online. So I guess if you come prepared (i.e. copy it into your clipboard beforehand) then you're OK, but it would be nice to have an escape hatch.
Just chiming back in to say that I just joined my google account using F18 with gnome-shell-3.6.2 (gnome-online-accounts-3.6.2) and it asked for my account's 2 factor code and signed my right in without error/issue.
(In reply to comment #7)
> Really ? Seems 2factor still not working on fully updated F17 gnome 3.4.x...
Works in my F18 as well. Cool! Thanks!
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.