I have a copy of Aggregate 1.3.4 running under a Google Apps for Business
Domain and wish to publish to either Spreadsheet or Fusion Table. If I
select Spreadsheet nothing happens, if I select Fusion Tables I get an
error message - see attached.
A search identified a similar issue logged under Issue 776:Failure to
publish when user is a non-gmail.com account (i.e., Google apps domain).
I have followed the suggestions regarding "Delegate domain-wide authority
to your service account", again see attached, but following a log off/log
on/browser restart/clear history etc. still cannot publish anything.
In my experience, publishing from a non-Gmail account is unreliable. I
think the problem is with Google's OAuth APIs. Does it work if you
publish from a non-Gmail domain?
Yaw
···
--
Need ODK services? http://nafundi.com provides form design,
professional support, custom reporting, and software development for
ODK.
I have a copy of Aggregate 1.3.4 running under a Google Apps for Business
Domain and wish to publish to either Spreadsheet or Fusion Table. If I
select Spreadsheet nothing happens, if I select Fusion Tables I get an error
message - see attached.
A search identified a similar issue logged under Issue 776:Failure to
publish when user is a non-gmail.com account (i.e., Google apps domain).
I have followed the suggestions regarding "Delegate domain-wide authority to
your service account", again see attached, but following a log off/log
on/browser restart/clear history etc. still cannot publish anything.
Hi Yaw,
Thanks for the prompt response - following a comparative test I can confirm
the same Aggregate release, same form with similar data works perfectly well
with the exception of publishing to a spreadsheet when configured on a
simple non 'Google Apps for Business' account. The test was conducted using
a simple xxxxx@gmail.com account rather than a linked domain through
Google's Business offering.
Your comment about publishing from a non-Gmail account being unreliable,
does this imply that an install on AWS would also be problematic?
Regards
Mick
···
-----Original Message-----
From: opendatakit-developers@googlegroups.com
[mailto:opendatakit-developers@googlegroups.com] On Behalf Of Yaw Anokwa
Sent: 06 September 2013 03:50
To: ODK Developers
Subject: Re: [ODK Developers] Publishing to Aggregate 1.3.4
Mick,
In my experience, publishing from a non-Gmail account is unreliable. I think
the problem is with Google's OAuth APIs. Does it work if you publish from a
non-Gmail domain?
Yaw
Need ODK services? http://nafundi.com provides form design, professional
support, custom reporting, and software development for ODK.
I have a copy of Aggregate 1.3.4 running under a Google Apps for
Business Domain and wish to publish to either Spreadsheet or Fusion
Table. If I select Spreadsheet nothing happens, if I select Fusion
Tables I get an error message - see attached.
A search identified a similar issue logged under Issue 776:Failure to
publish when user is a non-gmail.com account (i.e., Google apps domain).
I have followed the suggestions regarding "Delegate domain-wide
authority to your service account", again see attached, but following
a log off/log on/browser restart/clear history etc. still cannot publish
anything.
Yes that applies to the AWS version as well as it's not an Aggregate
problem it's a Google problem.
The ODK core team discussed ways to fix this at Google IO 2013 with some of
their developers they gave us a solution that only worked with the beta
libraries, when using the release candidate libraries it does not work.
Basically in short it appears to be a problem with an upgrade to the OAuth2
specifications at Google. To successfully work you had to supply the
business-app-domain as a 'p' parameter (if I recall correctly); however,
the new system puts it as an 's' parameter but this is failing. Long story
short we have been trying for months to resolve this and Google internally
seems to be contradicting it's self. Once Google straightens it out we will
upgrade Aggregate's code and then it will work. Until then it might work or
might not work depending on the release and where Google currently is and
what version of Aggregate your running.
We know it's a mess (and apologize) but we are dependent on Google
providing libraries and APIs that are consistent and usable and work as
advertised and it's all in flux right now on Google's end so it makes it
impossible for us to provide reliable service. However, any gmail account
will work just fine. This has been an historic problem for google. For
example for years an owner of any App Engine instance had to be a gmail
account (well proper google account). Google's business offering accounts
could not own certain types of Google services, they eventually fixed it
but they are still working through fixing more it appears from an outsiders
perspective.
Waylon
···
On Fri, Sep 6, 2013 at 12:56 AM, Mick Terry <michael.terry@mctservices.co.uk wrote:
Hi Yaw,
Thanks for the prompt response - following a comparative test I can confirm
the same Aggregate release, same form with similar data works perfectly
well
with the exception of publishing to a spreadsheet when configured on a
simple non 'Google Apps for Business' account. The test was conducted using
a simple xxxxx@gmail.com account rather than a linked domain through
Google's Business offering.
Your comment about publishing from a non-Gmail account being unreliable,
does this imply that an install on AWS would also be problematic?
In my experience, publishing from a non-Gmail account is unreliable. I
think
the problem is with Google's OAuth APIs. Does it work if you publish from a
non-Gmail domain?
Yaw
Need ODK services? http://nafundi.com provides form design, professional
support, custom reporting, and software development for ODK.
I have a copy of Aggregate 1.3.4 running under a Google Apps for
Business Domain and wish to publish to either Spreadsheet or Fusion
Table. If I select Spreadsheet nothing happens, if I select Fusion
Tables I get an error message - see attached.
A search identified a similar issue logged under Issue 776:Failure to
publish when user is a non-gmail.com account (i.e., Google apps domain).
I have followed the suggestions regarding "Delegate domain-wide
authority to your service account", again see attached, but following
a log off/log on/browser restart/clear history etc. still cannot publish
anything.
