Hi Shushu, Using AuthSub/OAuth for authentication is recommended for web applications that integrate with Health, and is necessary for Health partners that wish to be listed in the Health services directory and in users' profiles along with provided data. Also, OAuth is Google's recommended authorization scheme, since it is a more robust, standard strategy compared to ClientLogin.
When authenticated with AuthSub/OAuth, clients can only insert or read from users' profiles. Updates and deletes are currently supported if the client authenticates with ClientLogin; however, since OAuth is recommend over ClientLogin, we don't have an integration strategy to recommend that supports full data syncing at the moment. We are investigating how we might support additional operations with OAuth, and will definitely keep the community notified of any developments. Also, we are very open to ideas from the Health developer community that might streamline the syncing use case. Please don't hesitate to share! Paul On Jul 26, 11:43 pm, shushu <[email protected]> wrote: > Hello, > I develop an application that syncs data between Google Health and a > propietary system, using PHP. > Accordingly, I can use OAuth or AuthSub for authentication. > > Is it 100% true that in the bottom line, I cannot update or delete > information ? > All I can do is read data and add data (by sending notices) ? > > I ask this according to the documentation here > -http://code.google.com/intl/iw-IL/apis/health/docs/2.0/reference.html... > > What is the proper way to add to my application a "real" syncing > capabilities ? > > Regards, > Shushu -- You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en.
