OAuth Provider Extension for ZCS6.0

[yutaka]

Hi vmahajan,

Right now, I am working on modifying this extension to be scalable by using memcached as storage for OAuth Token info instead of local cache.
So I do not have enough time and environment to work on the problem you have.
But I will get back to you soon after the modification is done.

In the meantime, could you check a few things for me?
Right after provider.retrieveAccessToken, could you put these lines below?

System.out.println(provider.getConsumer().getToken ());
System.out.println(provider.getConsumer().getToken Secret());

It will give you AccessToken and TokenSecret you have to use to get access to protected resources.

Thank you

[vmahajan]

I don't see any oauth.signpost.basic.DefaultOAuthProvider.getConsu mer() method in the signpost API - signpost-core 1.2.1 API. Even in your previous reply your code instantiated provider by passing consumer as one of the arguments - I didn't find that constructor either.


.

[vmahajan]

I've got it working now!

The signature validation error was happening because the resource URI I was using was /home/user1/inbox.rss, and the signature on the consumer side was calculated using this URI. However on the server side the request gets redirected to /service/home/user1/inbox.rss, so the server uses a different URI to calculate signature on its side and hence the signature mismatch. Changing the URI to /service/home/user1/inbox.rss on the consumer side fixed the issue.

Thanks.

[yutaka]

Hi vmahajan,

I am really glad hear that!

And I am really sorry about my wrong suggestion to you.
I use signpost-core 1.1 API in my test environment.
So my suggestion was based on that.
Maybe oauth.signpost.basic.DefaultOAuthProvider.getConsu mer() method was removed somewhere between version 1.1 and 1.2.1

Anyway you now have the environment where you can try Oauth Extesntion.
Enjoy yourself!

[yutaka]

Hi guys,

I have just done scalability enhancement for OAuth Provider Extension,
by using memcached as storage for OAuth Token info instead of store's local cache.
So you can deploy this extension to multi store server environment also.
Please check this out and let me know your feedback!

bucchi's zmoauthprovext at v0.3 - GitHub


I am not sure so far, but maybe my next target will be OAuthIMAP(OAuthIMAP (Google OAuth & Federated Login Research)) or OAuthWRAP(OAuth / OAuth WRAP).
If you have any idea about this, let me know.


Thanks

[yutaka]

Oh, I almost forgot to tell you this:

I upgraded my Zimbra Server to 6.0.6 just before previous post.
So version 0.3 has been tested only on 6.0.6.

Thx

[vmahajan]

Cool. I was able to run the extension containing memcached enhancement, even though I just ran it on a single server setup.