Hi Harry,
I am glad that you are confident with OAuth2.
Authentication token goes from Google, as it is needed, and the
application never knows the user's credentials (username and password).
I do not see the reason of creating local server though.
Anyway, thanks for your interest in our work!
Best regards,
Igor Grivko
On 07/03/2012 11:31 PM, Harri Pasanen wrote:
Hi,
I had no problems with Google docs, but I could not see how the ICS
module obtained the authentication token. It seemed to use some
hack/feature of QWebView?
I ended up using a variation of
http://tftfy.blogspot.fr/2011/12/simple-oauth-20-in-qt.html instead,
which seems to be pretty complete implementation of OAuth2 in Qt,
although a bit more complex to use. That does implement the
callback interface (local server), which IMHO is required, and is
missing from the ICS module.
If you don't implement local server, the OAuth2 standard's hack was to
user some browser title change... but the redirect URI for that did
not work with ICS module.
Harri
On 07/03/2012 08:21 PM, Igor Grivko wrote:
Hi Harry,
Sorry for delay with reply, I was on vacation.
Google uses standard OAuth2 way of authentication, you can have a
look at:
https://developers.google.com/accounts/docs/OAuth2
Then I probably need to say some words about how it is supposed to work.
You need to create Google account (if you do not have one already)
and visit Google Console page:
https://code.google.com/apis/console
There you can create your own "Google Application". All the requests
that Google performs will be counted as yours. We do not provide the
secrets to our Google application - as Google has courtesy limits for
requests, and we do not want to be charged.
Then you need to get "secrets" from your Google application - you
need to go to tab *Api Access* in Google Console.
There you can find Cliend ID, Client Secret, and Redirect URI.
Redirect URI can be any working web server - you can use www.ics.com,
for instance.
Those three strings is the "fingerprints" of your Google application.
Of course you need to turn on the access to Calendar API too.
You can take a look at Wiki page of the our Calendar project:
http://code.google.com/p/qt-google-calendar/wiki/HowToRegisterYourApplicationInGoogle
Of course you do not need to create your own server.
Hope it helps. Feel free to ask any questions!
Best regards,
Igor Grivko
---------- Forwarded message ----------
From: *Harri Pasanen* <ha...@mpaja.com <mailto:ha...@mpaja.com>>
Date: Mon, Jun 25, 2012 at 12:39 PM
Subject: Re: [Interest] ICS Announces Qt-Based Google APIs
To: Justin Noel <jus...@ics.com <mailto:jus...@ics.com>>
Cc: interest@qt-project.org <mailto:interest@qt-project.org>
I took a quick look at qt-google-calendar, but it's unclear to me
how the authentication is supposed to work?
Basically the code expects you to fill in response uri, but does not
implement the server for it?
What am I supposed to put in there (m_strRedirectURI)? Reading
google docs it should probably be http://localhost:port
but then I should have a server listening there (or oauth2 should
provide one).
Confused,
Harri
On 06/20/2012 03:52 PM, Justin Noel wrote:
On 06/19/2012 03:48 PM, Till Oliver Knoll wrote:
Am 19.06.2012 um 20:21 schrieb Lynn Gray <lg...@ics.com
<mailto:lg...@ics.com>>:
* *Google Maps* – embed Google Maps images or Street View
panoramas without the need for JavaScript.
Just out of curiosity: is this a Google Map, shown via a WebKit
view, controlled (internally) via the Google JavaScript API which
is exposed as C++ methods?
The main developer of these packages just left on a well deserved
vacation. I wasn't directly involved with this project but I may be
of assistance here. The map in particular is a WebView + javascript
wrappers. Most of the other google apis are accessed directly
without webview, etc. If anyone has more questions you can fire
them my way.
Thanks!
--Justin
_______________________________________________
Interest mailing list
Interest@qt-project.org <mailto:Interest@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org <mailto:Interest@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
