Stefano Mazzocchi a626ea51ff if the user's computer's clock is not synchronized with Freebase's, the initial oauth handshake will fail because Freebase believe there is a replay attack going on. To avoid that we ask Acre to tell us what time it is in Freebase land and we sign the request with that instead. We default back to the user clock only if Acre is down or swamped. ... git-svn-id: http://google-refine.googlecode.com/svn/trunk@704 7d457c2a-affb-35e4-300a-418c747d4874		2010-05-10 23:24:58 +00:00
..
Credentials.java	- fixed oauth problem with non-127.0.0.1 hosts	2010-04-30 06:12:42 +00:00
FreebaseProvider.java	Checkpoint for OAuth functionality in Gridworks	2010-04-21 21:08:34 +00:00
FreebaseTimeCommonsHttpOAuthConsumer.java	if the user's computer's clock is not synchronized with Freebase's, the initial oauth handshake will fail because Freebase believe there is a replay attack going on. To avoid that we ask Acre to tell us what time it is in Freebase land and we sign the request with that instead. We default back to the user clock only if Acre is down or swamped.	2010-05-10 23:24:58 +00:00
OAuthUtilities.java	if the user's computer's clock is not synchronized with Freebase's, the initial oauth handshake will fail because Freebase believe there is a replay attack going on. To avoid that we ask Acre to tell us what time it is in Freebase land and we sign the request with that instead. We default back to the user clock only if Acre is down or swamped.	2010-05-10 23:24:58 +00:00
Provider.java	Checkpoint for OAuth functionality in Gridworks	2010-04-21 21:08:34 +00:00