11-25-2015 07:39
11-25-2015 07:39
As reading in the guidelines:
"
WARNING - DO NOT embed the Authorization Page
Any attempt to embed the OAuth 2.0 authentication page will result in your application being banned from the Fitbit API.
For security consideration, the OAuth 2.0 authorization page must be presented in a dedicated browser view. Fitbit users can only confirm they are authenticating with the genuine Fitbit.com site if they have they have the tools provided by the browser, such as the URL bar and Transport Layer Security (TLS) certificate information.
For native applications, this means the authorization page must open in the default browser. Native applications can use custom URL schemes as callback URIs to redirect the user back from the browser to the application requesting permission.
iOS applications may use the SFSafariViewController class instead of app switching to Safari. Use of the WKWebView or UIWebViewclass is prohibited.
Android applications may use Chrome Custom Tabs instead of app switching to the default browser. Use of WebView is prohibited.
For web applications, do not use an iframe. Web applications may use a pop-up window, so long as the URL bar is visible"
So my question is:
Could I use a software like Qt to make the authentication? For example using a QWebview or QNetworkAccessManager?
Thanx for your help!
11-25-2015 09:53
11-25-2015 09:53
In general, we want applications to rely on an OS's browser and to present the OAuth authorization page in a browser outside of the requesting application's control.
You're the first to ask about Qt and I may need to investigate more. From what I read in its documentation, the QWebview's content is modifable by the application requesting access, so Fitbit would not permit this.
11-25-2015 09:59
11-25-2015 09:59