"Sign in with Google" for ODK Aggregate will cease to function beginning
April 20th.
ACTIONS REQUIRED:
ODK Aggregate 1.4.5: provide all users that have been accessing the
webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
Aggregate username and password (you must specify an initial password) to
use instead of their Google credentials after April 19th.
Be sure to Save Changes to apply these changes!
ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and grant
it Site Admin permissions and an initial password. Use this username
instead of the Google account specified in the installer when administering
the system after April 19th.
Define ODK Aggregate usernames and passwords for all users of your website
as described in the 1.4.5 action section, above.
Is there any case that google apis through oauth2.0 service account will also not work for version 1.4.5??
Regards,
Ruby
···
On Wednesday, 1 April 2015 06:15:49 UTC+5:30, Mitch Sundt wrote:
> "Sign in with Google" for ODK Aggregate will cease to function beginning April 20th.
>
>
> ACTIONS REQUIRED:
>
>
> ODK Aggregate 1.4.5: provide all users that have been accessing the webserver via "Sign in with Google" (e.g., Gmail account) with an ODK Aggregate username and password (you must specify an initial password) to use instead of their Google credentials after April 19th.
>
> Be sure to Save Changes to apply these changes!
>
>
> ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and grant it Site Admin permissions and an initial password. Use this username instead of the Google account specified in the installer when administering the system after April 19th.
>
> Define ODK Aggregate usernames and passwords for all users of your website as described in the 1.4.5 action section, above.
>
> Be sure to Save Changes to apply these changes!
>
> Consider upgrading to 1.4.5 to prevent the accidental deletion of this user (and the resulting inaccessibility of your server) ( see https://code.google.com/p/opendatakit/wiki/AggregateReleaseNotes for upgrade steps).
>
>
> --
>
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
I have a bunch of carefully linked Fusion Tables published from
Aggregate that I logged in to using Sign in with Google. Is this going to
break those links? I'm hoping not because it will be a lot of work to
recreate them but I would rather know now than later.
Thank you!
···
On Tuesday, March 31, 2015 at 6:45:49 PM UTC-6, Mitch Sundt wrote:
>
> "Sign in with Google" for ODK Aggregate will cease to function beginning
> April 20th.
>
> *ACTIONS REQUIRED:*
>
> ODK Aggregate 1.4.5: provide all users that have been accessing the
> webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
> Aggregate username and password (you must specify an initial password) to
> use instead of their Google credentials after April 19th.
>
> *Be sure to Save Changes to apply these changes!*
>
> ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
> grant it Site Admin permissions and an initial password. Use this username
> instead of the Google account specified in the installer when administering
> the system after April 19th.
>
> Define ODK Aggregate usernames and passwords for all users of your website
> as described in the 1.4.5 action section, above.
>
> *Be sure to Save Changes to apply these changes!*
>
> Consider upgrading to 1.4.5 to prevent the accidental deletion of this
> user (and the resulting inaccessibility of your server) ( see
> https://code.google.com/p/opendatakit/wiki/AggregateReleaseNotes for
> upgrade steps).
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
>
unfortunately I was not aware of the 20 April being a critical day and now
I am locked out from my Aggregate as admin. I do have access to the server
through an Aggregate account, however it does not have admin rights, so I
can only see and export data, but I cannot do anything else, such as upload
new forms etc.
Is there anyway I can regain access with admin rights?
thanks so much for your help,
Jevgeniy
···
Am Mittwoch, 1. April 2015 02:45:49 UTC+2 schrieb Mitch Sundt:
>
> "Sign in with Google" for ODK Aggregate will cease to function beginning
> April 20th.
>
> *ACTIONS REQUIRED:*
>
> ODK Aggregate 1.4.5: provide all users that have been accessing the
> webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
> Aggregate username and password (you must specify an initial password) to
> use instead of their Google credentials after April 19th.
>
> *Be sure to Save Changes to apply these changes!*
>
> ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
> grant it Site Admin permissions and an initial password. Use this username
> instead of the Google account specified in the installer when administering
> the system after April 19th.
>
> Define ODK Aggregate usernames and passwords for all users of your website
> as described in the 1.4.5 action section, above.
>
> *Be sure to Save Changes to apply these changes!*
>
> Consider upgrading to 1.4.5 to prevent the accidental deletion of this
> user (and the resulting inaccessibility of your server) ( see
> https://code.google.com/p/opendatakit/wiki/AggregateReleaseNotes for
> upgrade steps).
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
>
Ok, upgrading to 1.4.5? I did try to install the v1.4.5 exe but the
installation fails because it doesnt accept my gmail login. Or perhaps I
dont know how to upgrade?
thanks,
Jevgeniy
···
Am Mittwoch, 1. April 2015 02:45:49 UTC+2 schrieb Mitch Sundt:
>
> "Sign in with Google" for ODK Aggregate will cease to function beginning
> April 20th.
>
> *ACTIONS REQUIRED:*
>
> ODK Aggregate 1.4.5: provide all users that have been accessing the
> webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
> Aggregate username and password (you must specify an initial password) to
> use instead of their Google credentials after April 19th.
>
> *Be sure to Save Changes to apply these changes!*
>
> ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
> grant it Site Admin permissions and an initial password. Use this username
> instead of the Google account specified in the installer when administering
> the system after April 19th.
>
> Define ODK Aggregate usernames and passwords for all users of your website
> as described in the 1.4.5 action section, above.
>
> *Be sure to Save Changes to apply these changes!*
>
> Consider upgrading to 1.4.5 to prevent the accidental deletion of this
> user (and the resulting inaccessibility of your server) ( see
> https://code.google.com/p/opendatakit/wiki/AggregateReleaseNotes for
> upgrade steps).
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
>
Am using ODK Aggregate 1.4.5 and i have been publishing on googlesheet and fusion table.But now once i try publish am getting this error
------------------------- start of error -------------------------------------
Error: RequestFailureException (com.google.gdata.util.InvalidEntryException: The Doclist API has been shut down. Please use the new Drive API, https://developers.google.com/drive/. GDataBadRequestExceptionThe Doclist API has been shut down. Please use the new Drive API, https://developers.google.com/drive/. )
------------------------- end of error -----------------------------------------
how can i rectify this hitch ?
Kind request
Simon
···
On Wednesday, 1 April 2015 03:45:49 UTC+3, Mitch Sundt wrote:
> "Sign in with Google" for ODK Aggregate will cease to function beginning April 20th.
>
>
> ACTIONS REQUIRED:
>
>
> ODK Aggregate 1.4.5: provide all users that have been accessing the webserver via "Sign in with Google" (e.g., Gmail account) with an ODK Aggregate username and password (you must specify an initial password) to use instead of their Google credentials after April 19th.
>
> Be sure to Save Changes to apply these changes!
>
>
> ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and grant it Site Admin permissions and an initial password. Use this username instead of the Google account specified in the installer when administering the system after April 19th.
>
> Define ODK Aggregate usernames and passwords for all users of your website as described in the 1.4.5 action section, above.
>
> Be sure to Save Changes to apply these changes!
>
> Consider upgrading to 1.4.5 to prevent the accidental deletion of this user (and the resulting inaccessibility of your server) ( see https://code.google.com/p/opendatakit/wiki/AggregateReleaseNotes for upgrade steps).
>
>
> --
>
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
No. Those are unaffected and should continue to work.
···
On Apr 2, 2015 4:50 AM, <23ruby11@gmail.com> wrote:
On Wednesday, 1 April 2015 06:15:49 UTC+5:30, Mitch Sundt wrote:
"Sign in with Google" for ODK Aggregate will cease to function beginning
April 20th.
ACTIONS REQUIRED:
ODK Aggregate 1.4.5: provide all users that have been accessing the
webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
Aggregate username and password (you must specify an initial password) to
use instead of their Google credentials after April 19th.
Be sure to Save Changes to apply these changes!
ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
grant it Site Admin permissions and an initial password. Use this username
instead of the Google account specified in the installer when administering
the system after April 19th.
Define ODK Aggregate usernames and passwords for all users of your
website as described in the 1.4.5 action section, above.
Those will continue to work; we use the Oauth 2.0 protocol for publishing.
When setting up a new publisher, you will be asked to supply a gmail
account that will be the owner of the data tables. Everything else will
otherwise behave as it has in the past.
···
On Wed, Apr 15, 2015 at 10:04 AM, Pest Lab COE wrote:
Hi,
I have a bunch of carefully linked Fusion Tables published from
Aggregate that I logged in to using Sign in with Google. Is this going to
break those links? I'm hoping not because it will be a lot of work to
recreate them but I would rather know now than later.
Thank you!
On Tuesday, March 31, 2015 at 6:45:49 PM UTC-6, Mitch Sundt wrote:
"Sign in with Google" for ODK Aggregate will cease to function beginning
April 20th.
ACTIONS REQUIRED:
ODK Aggregate 1.4.5: provide all users that have been accessing the
webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
Aggregate username and password (you must specify an initial password) to
use instead of their Google credentials after April 19th.
Be sure to Save Changes to apply these changes!
ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
grant it Site Admin permissions and an initial password. Use this username
instead of the Google account specified in the installer when administering
the system after April 19th.
Define ODK Aggregate usernames and passwords for all users of your
website as described in the 1.4.5 action section, above.
···
On Tue, Apr 21, 2015 at 1:57 PM, Ano Nym wrote:
Hi Mitch,
unfortunately I was not aware of the 20 April being a critical day and now
I am locked out from my Aggregate as admin. I do have access to the server
through an Aggregate account, however it does not have admin rights, so I
can only see and export data, but I cannot do anything else, such as upload
new forms etc.
Is there anyway I can regain access with admin rights?
thanks so much for your help,
Jevgeniy
Am Mittwoch, 1. April 2015 02:45:49 UTC+2 schrieb Mitch Sundt:
"Sign in with Google" for ODK Aggregate will cease to function beginning
April 20th.
ACTIONS REQUIRED:
ODK Aggregate 1.4.5: provide all users that have been accessing the
webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
Aggregate username and password (you must specify an initial password) to
use instead of their Google credentials after April 19th.
Be sure to Save Changes to apply these changes!
ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
grant it Site Admin permissions and an initial password. Use this username
instead of the Google account specified in the installer when administering
the system after April 19th.
Define ODK Aggregate usernames and passwords for all users of your
website as described in the 1.4.5 action section, above.
Visit https://appengine.google.com to see what AppEngine application IDs
your gmail account owns. If you have multiple gmail accounts, try each
until you find the one that shows the application you are trying to upgrade.
If that account has two-factor authentication, you will need to get an
app-specific password in order to run the update script. Note that you can
re-run the upload script by double-clicking it in the ODK Aggregate
directory that the installer generated (i.e., once the installer has
created the directory, you don't have to re-run the installer to re-run the
upload script, just double-click it to start it).
···
On Tue, Apr 21, 2015 at 11:31 PM, Ano Nym wrote:
Ok, upgrading to 1.4.5? I did try to install the v1.4.5 exe but the
installation fails because it doesnt accept my gmail login. Or perhaps I
dont know how to upgrade?
thanks,
Jevgeniy
Am Mittwoch, 1. April 2015 02:45:49 UTC+2 schrieb Mitch Sundt:
"Sign in with Google" for ODK Aggregate will cease to function beginning
April 20th.
ACTIONS REQUIRED:
ODK Aggregate 1.4.5: provide all users that have been accessing the
webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
Aggregate username and password (you must specify an initial password) to
use instead of their Google credentials after April 19th.
Be sure to Save Changes to apply these changes!
ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
grant it Site Admin permissions and an initial password. Use this username
instead of the Google account specified in the installer when administering
the system after April 19th.
Define ODK Aggregate usernames and passwords for all users of your
website as described in the 1.4.5 action section, above.
This is an oversight on our part. We were making a call to an API that
Google turned off on April 20th. We are working on a fix.
···
On Thu, Apr 23, 2015 at 5:47 AM, wrote:
On Wednesday, 1 April 2015 03:45:49 UTC+3, Mitch Sundt wrote:
"Sign in with Google" for ODK Aggregate will cease to function beginning
April 20th.
ACTIONS REQUIRED:
ODK Aggregate 1.4.5: provide all users that have been accessing the
webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
Aggregate username and password (you must specify an initial password) to
use instead of their Google credentials after April 19th.
Be sure to Save Changes to apply these changes!
ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
grant it Site Admin permissions and an initial password. Use this username
instead of the Google account specified in the installer when administering
the system after April 19th.
Define ODK Aggregate usernames and passwords for all users of your
website as described in the 1.4.5 action section, above.
Am using ODK Aggregate 1.4.5 and i have been publishing on googlesheet and
fusion table.But now once i try publish am getting this error
------------------------- start of error
Error: RequestFailureException
(com.google.gdata.util.InvalidEntryException: The Doclist API has been shut
down. Please use the new Drive API, https://developers.google.com/drive/.
GDataBadRequestExceptionThe
Doclist API has been shut down. Please use the new Drive API, https://developers.google.com/drive/. )
------------------------- end of error
Thank you very much Mitch! That is awesome!! Regards!
···
On Wednesday, April 15, 2015 at 12:14:54 PM UTC-6, Mitch Sundt wrote:
>
> Those will continue to work; we use the Oauth 2.0 protocol for publishing.
>
> When setting up a new publisher, you will be asked to supply a gmail
> account that will be the owner of the data tables. Everything else will
> otherwise behave as it has in the past.
>
>
>
>
> On Wed, Apr 15, 2015 at 10:04 AM, Pest Lab COE <edmpe...@gmail.com > wrote:
>
>> Hi,
>>
>> I have a bunch of carefully linked Fusion Tables published from
>> Aggregate that I logged in to using Sign in with Google. Is this going to
>> break those links? I'm hoping not because it will be a lot of work to
>> recreate them but I would rather know now than later.
>>
>> Thank you!
>>
>>
>> On Tuesday, March 31, 2015 at 6:45:49 PM UTC-6, Mitch Sundt wrote:
>>
>>> "Sign in with Google" for ODK Aggregate will cease to function
>>> beginning April 20th.
>>>
>>> *ACTIONS REQUIRED:*
>>>
>>> ODK Aggregate 1.4.5: provide all users that have been accessing the
>>> webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
>>> Aggregate username and password (you must specify an initial password) to
>>> use instead of their Google credentials after April 19th.
>>>
>>> *Be sure to Save Changes to apply these changes!*
>>>
>>> ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
>>> grant it Site Admin permissions and an initial password. Use this username
>>> instead of the Google account specified in the installer when administering
>>> the system after April 19th.
>>>
>>> Define ODK Aggregate usernames and passwords for all users of your
>>> website as described in the 1.4.5 action section, above.
>>>
>>> *Be sure to Save Changes to apply these changes!*
>>>
>>> Consider upgrading to 1.4.5 to prevent the accidental deletion of this
>>> user (and the resulting inaccessibility of your server) ( see
>>> https://code.google.com/p/opendatakit/wiki/AggregateReleaseNotes for
>>> upgrade steps).
>>>
>>> --
>>> Mitch Sundt
>>> Software Engineer
>>> University of Washington
>>> mitche...@gmail.com
>>>
>> --
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
>
So if we didn't see your URGENT message until now and don't remember our superuser name or password, did we lose access to all of our data...forever? Should we set up new aggregate accounts and appengine instances?
unfortunately this does not help me. I know the account details but they
are not accepted by aggregate while doing the updgrade.
···
Am Mittwoch, 22. April 2015 18:13:38 UTC+2 schrieb Mitch Sundt:
>
> Visit https://appengine.google.com to see what AppEngine application IDs
> your gmail account owns. If you have multiple gmail accounts, try each
> until you find the one that shows the application you are trying to upgrade.
>
> If that account has two-factor authentication, you will need to get an
> app-specific password in order to run the update script. Note that you can
> re-run the upload script by double-clicking it in the ODK Aggregate
> directory that the installer generated (i.e., once the installer has
> created the directory, you don't have to re-run the installer to re-run the
> upload script, just double-click it to start it).
>
>
>
>
> On Tue, Apr 21, 2015 at 11:31 PM, Ano Nym <jb.ma...@gmail.com > wrote:
>
>> Ok, upgrading to 1.4.5? I did try to install the v1.4.5 exe but the
>> installation fails because it doesnt accept my gmail login. Or perhaps I
>> dont know how to upgrade?
>>
>> thanks,
>> Jevgeniy
>>
>> Am Mittwoch, 1. April 2015 02:45:49 UTC+2 schrieb Mitch Sundt:
>>>
>>> "Sign in with Google" for ODK Aggregate will cease to function
>>> beginning April 20th.
>>>
>>> *ACTIONS REQUIRED:*
>>>
>>> ODK Aggregate 1.4.5: provide all users that have been accessing the
>>> webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
>>> Aggregate username and password (you must specify an initial password) to
>>> use instead of their Google credentials after April 19th.
>>>
>>> *Be sure to Save Changes to apply these changes!*
>>>
>>> ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
>>> grant it Site Admin permissions and an initial password. Use this username
>>> instead of the Google account specified in the installer when administering
>>> the system after April 19th.
>>>
>>> Define ODK Aggregate usernames and passwords for all users of your
>>> website as described in the 1.4.5 action section, above.
>>>
>>> *Be sure to Save Changes to apply these changes!*
>>>
>>> Consider upgrading to 1.4.5 to prevent the accidental deletion of this
>>> user (and the resulting inaccessibility of your server) ( see
>>> https://code.google.com/p/opendatakit/wiki/AggregateReleaseNotes for
>>> upgrade steps).
>>>
>>> --
>>> Mitch Sundt
>>> Software Engineer
>>> University of Washington
>>> mitche...@gmail.com
>>>
>> --
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
>
It is unclear what you are having difficulty with.
The uploading of the update to AppEngine requires a gmail account that is
the owner of that application id.
Once you have updated, the ODK Aggregate username you specified during the
install will have 'aggregate' as its password. Log in and change it.
···
On Fri, Apr 24, 2015 at 6:26 AM, Ano Nym wrote:
unfortunately this does not help me. I know the account details but they
are not accepted by aggregate while doing the updgrade.
Am Mittwoch, 22. April 2015 18:13:38 UTC+2 schrieb Mitch Sundt:
Visit https://appengine.google.com to see what AppEngine application IDs
your gmail account owns. If you have multiple gmail accounts, try each
until you find the one that shows the application you are trying to upgrade.
If that account has two-factor authentication, you will need to get an
app-specific password in order to run the update script. Note that you can
re-run the upload script by double-clicking it in the ODK Aggregate
directory that the installer generated (i.e., once the installer has
created the directory, you don't have to re-run the installer to re-run the
upload script, just double-click it to start it).
Ok, upgrading to 1.4.5? I did try to install the v1.4.5 exe but the
installation fails because it doesnt accept my gmail login. Or perhaps I
dont know how to upgrade?
thanks,
Jevgeniy
Am Mittwoch, 1. April 2015 02:45:49 UTC+2 schrieb Mitch Sundt:
"Sign in with Google" for ODK Aggregate will cease to function
beginning April 20th.
ACTIONS REQUIRED:
ODK Aggregate 1.4.5: provide all users that have been accessing the
webserver via "Sign in with Google" (e.g., Gmail account) with an ODK
Aggregate username and password (you must specify an initial password) to
use instead of their Google credentials after April 19th.
Be sure to Save Changes to apply these changes!
ODK Aggregate 1.4.4 and earlier: create an ODK Aggregate username and
grant it Site Admin permissions and an initial password. Use this username
instead of the Google account specified in the installer when administering
the system after April 19th.
Define ODK Aggregate usernames and passwords for all users of your
website as described in the 1.4.5 action section, above.
You received this message because you are subscribed to the Google
Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington mitche...@gmail.com