This is serious issues the users going to face in few days unless, ODK
takes any initiative to resolve it. I couldn't find about it from ODK and
looking forward to hear from ODK tea, how they are going to handle this
issue and what would the impact of it on new and existing users of ODK?
Please see the link for details. ClientLogin is a deprecated
authentication protocol that allows you to supply a username and password
so your standalone or local client application can connect to App Engine
resources.
https://cloud.google.com/appengine/docs/deprecations/clientlogin
Thanks
Before warning of serious issues due to the deprecation of some
Google-provided API, please search the source code to see if the code
actually uses that API.
Our software does not use ClientLogin. We use Spring Framework to manage
our user authentication, and do not use any Google mechanisms for that.
The only area of concern w.r.t. Google APIs is in the installer and the
upload script that uploads the configured application to Google at the end
of the installer.
And we have someone donating their time to explore transitioning that to
use a newer mechanism (and the old mechanism is not yet shut off). A quick
earlier exploration of this showed that a straightforward migration would
require everyone to install the Google Cloud SDK environment, perform some
manual steps, and then run the installer. The steps involved would likely
prevent most non-technical users from setting up their own Google AppEngine
systems.
···
On Thu, Mar 10, 2016 at 1:34 PM, A.N.M AL-IMRAN wrote:
This is serious issues the users going to face in few days unless, ODK
takes any initiative to resolve it. I couldn't find about it from ODK and
looking forward to hear from ODK tea, how they are going to handle this
issue and what would the impact of it on new and existing users of ODK?
Please see the link for details. ClientLogin is a deprecated
authentication protocol that allows you to supply a username and password
so your standalone or local client application can connect to App Engine
resources.
https://cloud.google.com/appengine/docs/deprecations/clientlogin
Thanks
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
Thanks for your response, that helps a lot. I am user of ODK and using this
platform for some of our base line and quality monitoring surveys. Some of
our upcoming survey using ODK will be launched after April 12, and as per
Google cloud administration, the API for uploading the scripts of ODK
Aggregate installation, will be shut off by April 12. Reason I am concerned
is, I am not really a non technical person; however, not really comfortable
with cloud hosting configuration. I am worried about, whether, there will
be updated guideline available to setup ODK Aggregate to app engine, as
soon as the old system close down. Secondly, how difficult will it be, to
configure! if that is same as setting up ODK to AWS server, then it will be
quite difficult to manage. I would appreciate your understanding for the
users of ODK, those used to setup their own server in a user friendly way
to use this useful tool. Thanks
A N M AL IMRAN (Imran)
Brossard, QC
Canada
Cell: +1 (438) 501 3576
···
On 16 March 2016 at 19:57, Mitch Sundt wrote:
Before warning of serious issues due to the deprecation of some
Google-provided API, please search the source code to see if the code
actually uses that API.
Our software does not use ClientLogin. We use Spring Framework to
manage our user authentication, and do not use any Google mechanisms for
that.
The only area of concern w.r.t. Google APIs is in the installer and the
upload script that uploads the configured application to Google at the end
of the installer.
And we have someone donating their time to explore transitioning that to
use a newer mechanism (and the old mechanism is not yet shut off). A quick
earlier exploration of this showed that a straightforward migration would
require everyone to install the Google Cloud SDK environment, perform some
manual steps, and then run the installer. The steps involved would likely
prevent most non-technical users from setting up their own Google AppEngine
systems.
On Thu, Mar 10, 2016 at 1:34 PM, A.N.M AL-IMRAN imran3may@gmail.com wrote:
This is serious issues the users going to face in few days unless, ODK
takes any initiative to resolve it. I couldn't find about it from ODK and
looking forward to hear from ODK tea, how they are going to handle this
issue and what would the impact of it on new and existing users of ODK?
Please see the link for details. ClientLogin is a deprecated
authentication protocol that allows you to supply a username and password
so your standalone or local client application can connect to App Engine
resources.
https://cloud.google.com/appengine/docs/deprecations/clientlogin
Thanks
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to a topic in the
Google Groups "ODK Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/opendatakit-developers/6jFhtv7NA4Y/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
There has been no deprecation timetable announced by Google for the
features used in the installer (and those features do not depend upon
ClientLogin). April 12th is not a date to be concerned about.
···
------------
The Google AppEngine ( appengine.google.com ) site is being shut down at
the end of March and migrated to Google Developers Console (
console.cloud.google.com ). We will be updating our screen shots and
documentation to use the new site in the next week.
Google has been shuffling and changing that new site's features weekly,
which has prevented us from reliably documenting the steps needed to create
an AppEngine instance through that site. And those changes have been
happening (weekly) for the last 10 months.
Rest assured that our aim is to hide as many of the steps as we can within
our installer wizard and upload scripts. And if we cannot, to provide clear
screen shots and step-by-step instructions so that non-technical users can
successfully set up their own servers on Google AppEngine.
On Wed, Mar 16, 2016 at 6:25 PM, A.N.M AL-IMRAN imran3may@gmail.com wrote:
Thanks for your response, that helps a lot. I am user of ODK and using
this platform for some of our base line and quality monitoring surveys.
Some of our upcoming survey using ODK will be launched after April 12, and
as per Google cloud administration, the API for uploading the scripts of
ODK Aggregate installation, will be shut off by April 12. Reason I am
concerned is, I am not really a non technical person; however, not really
comfortable with cloud hosting configuration. I am worried about, whether,
there will be updated guideline available to setup ODK Aggregate to app
engine, as soon as the old system close down. Secondly, how difficult will
it be, to configure! if that is same as setting up ODK to AWS server, then
it will be quite difficult to manage. I would appreciate your understanding
for the users of ODK, those used to setup their own server in a user
friendly way to use this useful tool. Thanks
A N M AL IMRAN (Imran)
Brossard, QC
Canada
Cell: +1 (438) 501 3576
On 16 March 2016 at 19:57, Mitch Sundt mitchellsundt@gmail.com wrote:
Before warning of serious issues due to the deprecation of some
Google-provided API, please search the source code to see if the code
actually uses that API.
Our software does not use ClientLogin. We use Spring Framework to
manage our user authentication, and do not use any Google mechanisms for
that.
The only area of concern w.r.t. Google APIs is in the installer and the
upload script that uploads the configured application to Google at the end
of the installer.
And we have someone donating their time to explore transitioning that to
use a newer mechanism (and the old mechanism is not yet shut off). A quick
earlier exploration of this showed that a straightforward migration would
require everyone to install the Google Cloud SDK environment, perform some
manual steps, and then run the installer. The steps involved would likely
prevent most non-technical users from setting up their own Google AppEngine
systems.
On Thu, Mar 10, 2016 at 1:34 PM, A.N.M AL-IMRAN imran3may@gmail.com wrote:
This is serious issues the users going to face in few days unless, ODK
takes any initiative to resolve it. I couldn't find about it from ODK and
looking forward to hear from ODK tea, how they are going to handle this
issue and what would the impact of it on new and existing users of ODK?
Please see the link for details. ClientLogin is a deprecated
authentication protocol that allows you to supply a username and password
so your standalone or local client application can connect to App Engine
resources.
https://cloud.google.com/appengine/docs/deprecations/clientlogin
Thanks
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to a topic in the
Google Groups "ODK Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/opendatakit-developers/6jFhtv7NA4Y/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
Thanks, Mitch.
A N M AL IMRAN (Imran)
Brossard, QC
Canada
Cell: +1 (438) 501 3576
···
On 16 March 2016 at 22:43, Mitch Sundt wrote:
There has been no deprecation timetable announced by Google for the
features used in the installer (and those features do not depend upon
ClientLogin). April 12th is not a date to be concerned about.
The Google AppEngine ( appengine.google.com ) site is being shut down at
the end of March and migrated to Google Developers Console (
console.cloud.google.com ). We will be updating our screen shots and
documentation to use the new site in the next week.
Google has been shuffling and changing that new site's features weekly,
which has prevented us from reliably documenting the steps needed to create
an AppEngine instance through that site. And those changes have been
happening (weekly) for the last 10 months.
Rest assured that our aim is to hide as many of the steps as we can within
our installer wizard and upload scripts. And if we cannot, to provide clear
screen shots and step-by-step instructions so that non-technical users can
successfully set up their own servers on Google AppEngine.
On Wed, Mar 16, 2016 at 6:25 PM, A.N.M AL-IMRAN imran3may@gmail.com wrote:
Thanks for your response, that helps a lot. I am user of ODK and using
this platform for some of our base line and quality monitoring surveys.
Some of our upcoming survey using ODK will be launched after April 12, and
as per Google cloud administration, the API for uploading the scripts of
ODK Aggregate installation, will be shut off by April 12. Reason I am
concerned is, I am not really a non technical person; however, not really
comfortable with cloud hosting configuration. I am worried about, whether,
there will be updated guideline available to setup ODK Aggregate to app
engine, as soon as the old system close down. Secondly, how difficult will
it be, to configure! if that is same as setting up ODK to AWS server, then
it will be quite difficult to manage. I would appreciate your understanding
for the users of ODK, those used to setup their own server in a user
friendly way to use this useful tool. Thanks
A N M AL IMRAN (Imran)
Brossard, QC
Canada
Cell: +1 (438) 501 3576
On 16 March 2016 at 19:57, Mitch Sundt mitchellsundt@gmail.com wrote:
Before warning of serious issues due to the deprecation of some
Google-provided API, please search the source code to see if the code
actually uses that API.
Our software does not use ClientLogin. We use Spring Framework to
manage our user authentication, and do not use any Google mechanisms for
that.
The only area of concern w.r.t. Google APIs is in the installer and the
upload script that uploads the configured application to Google at the end
of the installer.
And we have someone donating their time to explore transitioning that to
use a newer mechanism (and the old mechanism is not yet shut off). A quick
earlier exploration of this showed that a straightforward migration would
require everyone to install the Google Cloud SDK environment, perform some
manual steps, and then run the installer. The steps involved would likely
prevent most non-technical users from setting up their own Google AppEngine
systems.
On Thu, Mar 10, 2016 at 1:34 PM, A.N.M AL-IMRAN imran3may@gmail.com wrote:
This is serious issues the users going to face in few days unless, ODK
takes any initiative to resolve it. I couldn't find about it from ODK and
looking forward to hear from ODK tea, how they are going to handle this
issue and what would the impact of it on new and existing users of ODK?
Please see the link for details. ClientLogin is a deprecated
authentication protocol that allows you to supply a username and password
so your standalone or local client application can connect to App Engine
resources.
https://cloud.google.com/appengine/docs/deprecations/clientlogin
Thanks
--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to a topic in the
Google Groups "ODK Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/opendatakit-developers/6jFhtv7NA4Y/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
You received this message because you are subscribed to a topic in the
Google Groups "ODK Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/opendatakit-developers/6jFhtv7NA4Y/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.