08-07-2015 11:22 - edited 08-07-2015 12:16
08-07-2015 11:22 - edited 08-07-2015 12:16
I'm trying to integrate authorization into my web app. I've got the authorization process working. The user can authorize my web app to access their fitbit data. But after the callback, how can I redirect the user's browser back to my app? The browser just hangs on the fitbit auth page with a progress indicator spinning with the message "Hold On, Please". Then it gets an internal server error. Shouldn't fitbit api redirect back to my page?
Edit: I tried adding an additional callback hoping that's how fitbit can help with this problem. I have these callbacks configured on the site. The first one gets called, the second one (my app page) does not:
http://localhost:8080/fitbit/fitbit_callback
http://localhost:8080/fitbit-api-test
Edit: I tried adding a redirect_uri parameter with the auth request and that didn't work either.
08-07-2015 13:55
08-07-2015 13:55
From the labels you gave this topic, I assume that you're using OAuth 1.0a. The equivalent of redirect_uri in OAuth 1.0a is 'oauth_callback'.