Hi, I've read the docs and I believe I'm doing everything by theOAuth standard (and Google's docs). I only mentioned Twitter and other apps to show that our implementation has been tested and this isn't the first integration we've done. Any idea why the redirection doesn't work?
Andy On Jun 14, 2010, at 8:13 PM, Bess Ho wrote: > You can't assume same OAuth works for Twitter would work for Google Health. > You have to follow all the rules and instructions in getting your app > approved and certified by Google Health > > On Mon, Jun 14, 2010 at 5:10 AM, AndyBT <[email protected]> wrote: > Hi, > > I've been trying to get H9 working with our site's OAuth stack, but > the browser is not redirected back to our site when the token is > authorized. It is redirected to the main screen of H9 (https:// > h9.google.com/h9/p/) instead. The very same OAuth implementation works > fine with Twitter (and a number of other sites) and I don't see > anything wrong with the requests either. Do you have any idea what the > problem might be? > Please see the request below. I have tried it with a non-localhost > callback URI, but got the same results. > > Andy > > REQUEST TOKEN: > GET /accounts/OAuthGetRequestToken?scope=https%3A%2F%2Fwww.google.com > %2Fh9%2Ffeeds%2F&secure=0 > Host: www.google.com > Accept: application/x-www-form-urlencoded > Authorization: OAuth oauth_callback="https%3A%2F%2Flocalhost > %3A8181%2FBodyTrace%2Foauth.html", > oauth_signature="WvFoIjoatdeQ2edwcTMRm4xO1%2BI%3D", > oauth_version="1.0", oauth_nonce="25357458- > df48-4c2e-8500-95269078a030", oauth_signature_method="HMAC-SHA1", > oauth_consumer_key="www.bodytrace.com", oauth_timestamp="1276515738" > === > 200 OK > Date: Mon, 14 Jun 2010 11:42:18 GMT > Content-Length: 118 > Expires: Mon, 14 Jun 2010 11:42:18 GMT > X-XSS-Protection: 1; mode=block > Alternate-Protocol: 443:npn-spdy/1 > Content-Type: text/plain; charset=UTF-8 > Server: GSE > Cache-Control: private, max-age=0 > X-Content-Type-Options: nosniff > oauth_token=CIPR97-oEhDQlquC- > _____8BGLfFo5gD&oauth_token_secret=EnNXym2dpZD05jWiLY6zQBii&oauth_callback_confirmed=true > > > URI WE REDIRECT TO AUTHORIZE: > https://www.google.com/accounts/OAuthAuthorizeToken?oauth_token=CIPR97-oEhDQlquC-_____8BGLfFo5gD > > > URI OF AUTHORIZATION PAGE IN BROWSER: > https://h9.google.com/h9/oauth?oauth_token=CIPR97-oEhDQlquC-_____8BGLfFo5gD > > -- > 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. > > > > > -- > Bess Ho > UI Architect / Developer / Designer > iPhone Developer > Silicon Valley Web Builder (SVWB) Founder > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain CONFIDENTIAL material. If you receive > this material/information in error, please contact the sender and delete or > destroy the material/information. > > -- > 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. -- 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.
