07-08-2014 12:13
07-08-2014 12:13
Hello everybody,
Thanks for your time.
I was wondering how complicated would it be to create a custom login page for the fitbit authentification.
I know by standard Oauth requires to trigger a callback, and this is done after the user regulary used the fitbit login form, and give access to an app.
I know this uses a different token everytime and I know how they're generated, but would it be wrong to POST myself the form info with the token to /oauth/authorize ?
Would it fail because the request it's not comming from fitbit.com?
Sorry I'm messy with the explanation. I'm kind of multitasking right now.
I hope I cna get some guidance.
Thanks!
Answered! Go to the Best Answer.
Best Answer07-08-2014 12:16
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
07-08-2014 12:16
Hi Juan,
No, you cannot create a custom Fitbit OAuth sign in or authorization form. This would be a huge security risk.
Best Answer07-08-2014 12:16
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
07-08-2014 12:16
Hi Juan,
No, you cannot create a custom Fitbit OAuth sign in or authorization form. This would be a huge security risk.
Best Answer07-08-2014 12:20
07-08-2014 12:20
Thanks for the quick answer.
It's ok, it's better for me to have an official answer on this.
Appreciate it!
Best Answer