Currently ODK Aggregate uses OpenID for authentication, OpenID is being
deprecated in mid April which is going to break a bunch of Aggregate apps,
are there any plans to move the authentication to use OAuth2?
Not at this time.
Instead, the newer ODK Aggregate 1.4.5 installer requests a super-user
username which uses the older DigestAuth protocol that is used by ODK
Collect.
Going forward, groups will need to create these "ODK Aggregate" usernames
and assign passwords, and abandon their use of Google Gmail accounts for
authentication / authorization.
Should we support it, the steps that users will need to perform to set up
the Oauth2 mechanisms are roughly as awkward as those needed to set up
Google publishing credentials. Internally, we will need to replace several
libraries and workflows. Given the clumsiness of the configuration on the
Google side, this effort doesn't seem justified at this time.
ยทยทยท
On Mon, Mar 30, 2015 at 11:52 PM, John Wesonga wrote:Currently ODK Aggregate uses OpenID for authentication, OpenID is being
deprecated in mid April which is going to break a bunch of Aggregate apps,
are there any plans to move the authentication to use OAuth2?--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com