Any response, from people who have faced the problem or googlers, on this issue would be extremely helpful. I am blocked in being able to continue development and have been for about 2 weeks.
Thank you ahead of time, Chad On May 20, 7:17 pm, Chad Pry <[email protected]> wrote: > I recently started developing against the google health api. The > initial steps of setting up my domain (key, secret) have been > accomplished as well as building client side [web platform] code to > handle the request token, authorization, and access token management. > I've run into an issue that is concerning me. As I read the > discussion group, my understanding of the health api is it support > OAuth 1 and not 1a. I understand this to mean the callback url (next > url) needs to be assigned in the request token stage of communication > with the api. After this, I am able to communicate with the api, > redirect the web url to google health for authorization but have run > into a snag. The oauth verifier is not being sent and therefore my > request of an access token is responding with a 401 UnAuthorized. I > am not aware of another step that is missing, but continually receive > a 401 with each attempt. The OAuth Playground is working correctly > with my key/secret credentials as well as I can communicate to other > OAuth apis at google and receive the verifier. > > Any help would be greatly appreciated. > > Cheers,Chad -- 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.
