You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Jordan Zimmerman <jo...@shop.com> on 2009/01/22 21:34:47 UTC
OAuth and Shindig
The only doc I've found re OAuth and Shindig is here:
http://cwiki.apache.org/confluence/display/SHINDIG/Enabling+OAuth+suppor
t
Are there any other docs? Figuring out what I need to do is clear as
mud.
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: OAuth and Shindig
Posted by Brian Eaton <be...@google.com>.
On Fri, Jan 23, 2009 at 4:43 PM, Jordan Zimmerman <jo...@shop.com> wrote:
> Thank you.
You're welcome.
> Why can't something like what you just wrote be placed on the Shindig
> website?
Done, just updated the wiki:
http://cwiki.apache.org/confluence/display/SHINDIG/Enabling+OAuth+support
I would be interested in hearing your experiences with the persistence
implementation in Shindig. Were you able to share code across your
appdata/userprefs/oauth implementations? Is there any refactoring
that could happen in Shindig that would have made that sharing easier?
Cheers,
Brian
RE: OAuth and Shindig
Posted by Jordan Zimmerman <jo...@shop.com>.
I am collecting my experience etc. and building a library that will make
the next me that comes along a lot happier
(http://code.google.com/p/mediated-opensocial/).
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
-----Original Message-----
From: Rodrigo Gallardo [mailto:rodrigo@nul-unu.com]
Sent: Friday, January 23, 2009 5:02 PM
To: shindig-dev@incubator.apache.org
Subject: Re: OAuth and Shindig
On Fri, Jan 23, 2009 at 04:09:53PM -0800, Jordan Zimmerman wrote:
> This is really infuriating. Someone wrote all of this Java OAuth code.
I
> cannot understand why that person(s) can't write a document that
> explains how to use it. The only doc I've found on the net is this:
>
http://cwiki.apache.org/confluence/display/SHINDIG/Enabling+OAuth+suppor
> t - I guess it's describing cryptography so the author feels the need
to
> be cryptic.
The author does not feel such need at all. The author simply lacks the
knowdledge to say anything more detailed, but decided to dump the
little he knew in hopes that others would contribute back their own
improvements.
<tonge-movement destination="cheek">
The author is sorry to have been unhelpful, but nevertheless risks
running afoul of your grace and suggests you collect your experience
and what others have explained in this thread and contribute it to
the document, to better shield some other inocent souls from your
toils and tribulations.
</tonge-movement>
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: OAuth and Shindig
Posted by Rodrigo Gallardo <ro...@nul-unu.com>.
On Fri, Jan 23, 2009 at 04:09:53PM -0800, Jordan Zimmerman wrote:
> This is really infuriating. Someone wrote all of this Java OAuth code. I
> cannot understand why that person(s) can't write a document that
> explains how to use it. The only doc I've found on the net is this:
> http://cwiki.apache.org/confluence/display/SHINDIG/Enabling+OAuth+suppor
> t - I guess it's describing cryptography so the author feels the need to
> be cryptic.
The author does not feel such need at all. The author simply lacks the
knowdledge to say anything more detailed, but decided to dump the
little he knew in hopes that others would contribute back their own
improvements.
<tonge-movement destination="cheek">
The author is sorry to have been unhelpful, but nevertheless risks
running afoul of your grace and suggests you collect your experience
and what others have explained in this thread and contribute it to
the document, to better shield some other inocent souls from your
toils and tribulations.
</tonge-movement>
RE: OAuth and Shindig
Posted by Jordan Zimmerman <jo...@shop.com>.
Thank you.
Why can't something like what you just wrote be placed on the Shindig
website?
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
-----Original Message-----
From: Brian Eaton [mailto:beaton@google.com]
Sent: Friday, January 23, 2009 4:40 PM
To: shindig-dev@incubator.apache.org
Subject: Re: OAuth and Shindig
Hi Jordan -
Sorry to hear you're frustrated, especially given how helpful several
other people have already been. I'm the original author of lots of
the code that's troubling you, so I'll try to explain what each piece
is doing and what is reusable.
The OAuthCrypterProvider is used to provide encryption for some
client-side state. The Shindig implementation is suitable for
production use, provided that you share a shindig.oauth.state-key file
across all of your servers. The contents of that file should be a
long (20 or 30 characters) secret string.
The OAuthRequest class is suitable for production use. If you need to
add additional parameters to OAuth signed requests beyond the standard
opensocial parameters, you will want to write your own provider, or
possibly your own implementation of RequestPipeline.
The BasicOAuthStore class is not suitable for production use. You
need to tie into a persistent storage system.
This all looks to be in synch with the code snippet you sent.
Cheers,
Brian
On Fri, Jan 23, 2009 at 4:09 PM, Jordan Zimmerman <jo...@shop.com>
wrote:
> This is really infuriating. Someone wrote all of this Java OAuth code.
I
> cannot understand why that person(s) can't write a document that
> explains how to use it. The only doc I've found on the net is this:
>
http://cwiki.apache.org/confluence/display/SHINDIG/Enabling+OAuth+suppor
> t - I guess it's describing cryptography so the author feels the need
to
> be cryptic.
>
> Grrr....
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> All your favorite stores.
> OneCart(r) convenience.
> www.shop.com
>
>
>
> -----Original Message-----
> From: Jordan Zimmerman [mailto:jordanz@shop.com]
> Sent: Friday, January 23, 2009 3:34 PM
> To: shindig-dev@incubator.apache.org
> Subject: RE: OAuth and Shindig
>
>>That's what we did in our implementation. Make sure you do not have
>>"org.apache.shindig.gadgets.oauth.OAuthModule" as one of the
> guice-modules
>>inside your web application's web.xml.
>
> OK. I've gotten my OAuthModule to init now. What's unclear to me is if
> I'm supposed to re-use any of Shindig's OAuth stuff or am I supposed
to
> re-write it all. E.g. my Guice module now has this:
>
> bind(BlobCrypter.class).annotatedWith(Names.named(
> OAuthFetcherConfig.OAUTH_STATE_CRYPTER)).toProvider(
> OAuthModule.OAuthCrypterProvider.class);
>
bind(OAuthRequest.class).toProvider(OAuthModule.OAuthRequestProvider.cla
> ss);
>
> // my class
> bind(OAuthStore.class).toProvider(MediatedOAuthStoreProvider.class);
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> All your favorite stores.
> OneCart(r) convenience.
> www.shop.com
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: OAuth and Shindig
Posted by Brian Eaton <be...@google.com>.
Hi Jordan -
Sorry to hear you're frustrated, especially given how helpful several
other people have already been. I'm the original author of lots of
the code that's troubling you, so I'll try to explain what each piece
is doing and what is reusable.
The OAuthCrypterProvider is used to provide encryption for some
client-side state. The Shindig implementation is suitable for
production use, provided that you share a shindig.oauth.state-key file
across all of your servers. The contents of that file should be a
long (20 or 30 characters) secret string.
The OAuthRequest class is suitable for production use. If you need to
add additional parameters to OAuth signed requests beyond the standard
opensocial parameters, you will want to write your own provider, or
possibly your own implementation of RequestPipeline.
The BasicOAuthStore class is not suitable for production use. You
need to tie into a persistent storage system.
This all looks to be in synch with the code snippet you sent.
Cheers,
Brian
On Fri, Jan 23, 2009 at 4:09 PM, Jordan Zimmerman <jo...@shop.com> wrote:
> This is really infuriating. Someone wrote all of this Java OAuth code. I
> cannot understand why that person(s) can't write a document that
> explains how to use it. The only doc I've found on the net is this:
> http://cwiki.apache.org/confluence/display/SHINDIG/Enabling+OAuth+suppor
> t - I guess it's describing cryptography so the author feels the need to
> be cryptic.
>
> Grrr....
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> All your favorite stores.
> OneCart(r) convenience.
> www.shop.com
>
>
>
> -----Original Message-----
> From: Jordan Zimmerman [mailto:jordanz@shop.com]
> Sent: Friday, January 23, 2009 3:34 PM
> To: shindig-dev@incubator.apache.org
> Subject: RE: OAuth and Shindig
>
>>That's what we did in our implementation. Make sure you do not have
>>"org.apache.shindig.gadgets.oauth.OAuthModule" as one of the
> guice-modules
>>inside your web application's web.xml.
>
> OK. I've gotten my OAuthModule to init now. What's unclear to me is if
> I'm supposed to re-use any of Shindig's OAuth stuff or am I supposed to
> re-write it all. E.g. my Guice module now has this:
>
> bind(BlobCrypter.class).annotatedWith(Names.named(
> OAuthFetcherConfig.OAUTH_STATE_CRYPTER)).toProvider(
> OAuthModule.OAuthCrypterProvider.class);
> bind(OAuthRequest.class).toProvider(OAuthModule.OAuthRequestProvider.cla
> ss);
>
> // my class
> bind(OAuthStore.class).toProvider(MediatedOAuthStoreProvider.class);
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> All your favorite stores.
> OneCart(r) convenience.
> www.shop.com
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
RE: OAuth and Shindig
Posted by Jordan Zimmerman <jo...@shop.com>.
This is really infuriating. Someone wrote all of this Java OAuth code. I
cannot understand why that person(s) can't write a document that
explains how to use it. The only doc I've found on the net is this:
http://cwiki.apache.org/confluence/display/SHINDIG/Enabling+OAuth+suppor
t - I guess it's describing cryptography so the author feels the need to
be cryptic.
Grrr....
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
-----Original Message-----
From: Jordan Zimmerman [mailto:jordanz@shop.com]
Sent: Friday, January 23, 2009 3:34 PM
To: shindig-dev@incubator.apache.org
Subject: RE: OAuth and Shindig
>That's what we did in our implementation. Make sure you do not have
>"org.apache.shindig.gadgets.oauth.OAuthModule" as one of the
guice-modules
>inside your web application's web.xml.
OK. I've gotten my OAuthModule to init now. What's unclear to me is if
I'm supposed to re-use any of Shindig's OAuth stuff or am I supposed to
re-write it all. E.g. my Guice module now has this:
bind(BlobCrypter.class).annotatedWith(Names.named(
OAuthFetcherConfig.OAUTH_STATE_CRYPTER)).toProvider(
OAuthModule.OAuthCrypterProvider.class);
bind(OAuthRequest.class).toProvider(OAuthModule.OAuthRequestProvider.cla
ss);
// my class
bind(OAuthStore.class).toProvider(MediatedOAuthStoreProvider.class);
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
RE: OAuth and Shindig
Posted by Jordan Zimmerman <jo...@shop.com>.
>That's what we did in our implementation. Make sure you do not have
>"org.apache.shindig.gadgets.oauth.OAuthModule" as one of the
guice-modules
>inside your web application's web.xml.
OK. I've gotten my OAuthModule to init now. What's unclear to me is if
I'm supposed to re-use any of Shindig's OAuth stuff or am I supposed to
re-write it all. E.g. my Guice module now has this:
bind(BlobCrypter.class).annotatedWith(Names.named(
OAuthFetcherConfig.OAUTH_STATE_CRYPTER)).toProvider(
OAuthModule.OAuthCrypterProvider.class);
bind(OAuthRequest.class).toProvider(OAuthModule.OAuthRequestProvider.cla
ss);
// my class
bind(OAuthStore.class).toProvider(MediatedOAuthStoreProvider.class);
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: OAuth and Shindig
Posted by Chirag Shah <ch...@gmail.com>.
That's what we did in our implementation. Make sure you do not have
"org.apache.shindig.gadgets.oauth.OAuthModule" as one of the guice-modules
inside your web application's web.xml.
On Fri, Jan 23, 2009 at 3:15 PM, Jordan Zimmerman <jo...@shop.com> wrote:
> As I suspected, Guice complains that there already is a binding (due to
> OAuthModule). So, it seems I have to replace OAuthModule.
>
> Instead of me guessing, can anyone direct me to docs on how to do this
> correctly?
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> All your favorite stores.
> OneCart(r) convenience.
> www.shop.com
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
RE: OAuth and Shindig
Posted by Jordan Zimmerman <jo...@shop.com>.
As I suspected, Guice complains that there already is a binding (due to
OAuthModule). So, it seems I have to replace OAuthModule.
Instead of me guessing, can anyone direct me to docs on how to do this
correctly?
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
RE: OAuth and Shindig
Posted by Jordan Zimmerman <jo...@shop.com>.
> I think it's something like this. Please correct me if it's incorrect.
I'll give that a try. Thanks for looking at my code, too :)
However, it seems to me that that's going to conflict with the
OAuthModule's registration of the same. I don't know Guice well enough,
though.
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
-----Original Message-----
From: Chirag Shah [mailto:chiragshah1@gmail.com]
Sent: Thursday, January 22, 2009 6:00 PM
To: shindig-dev@incubator.apache.org
Subject: Re: OAuth and Shindig
>
> that some of the Shindig OAuth internals are initialized. But, how am
I
> supposed to tell Guice about my OAuthStore implementation?
I think it's something like this. Please correct me if it's incorrect.
Add the following inside MediatedGuiceModule
http://code.google.com/p/mediated-opensocial/source/browse/trunk/shindig
/com/shop/opensocial/mediated/shindig/config/MediatedGuiceModule.java
@Override
protected void configure() {
...
bind(OAuthStore.class).toProvider(CustomOAuthStoreProvider.class);
...
}
public static class CustomOAuthStoreProvider implements
Provider<OAuthStore> {
private final CustomOAuthTokenStore store;
public CustomOAuthStoreProvider() {
store = new CustomOAuthTokenStore();
}
public OAuthStore get() {
return store;
}
}
On Thu, Jan 22, 2009 at 5:00 PM, Jordan Zimmerman <jo...@shop.com>
wrote:
> >Implementing this should involve implementing the
> >SecurityTokenDecoder and OAuthConsumerStore interfaces.
> You mean OAuthStore, I think. Also, I don't see where
> SecurityTokenDecoder comes into play or how I'm supposed to implement
> it.
>
> Another question: What about OAuthModule? It appears to be necessary
so
> that some of the Shindig OAuth internals are initialized. But, how am
I
> supposed to tell Guice about my OAuthStore implementation?
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> All your favorite stores.
> OneCart(r) convenience.
> www.shop.com
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: OAuth and Shindig
Posted by Chirag Shah <ch...@gmail.com>.
>
> that some of the Shindig OAuth internals are initialized. But, how am I
> supposed to tell Guice about my OAuthStore implementation?
I think it's something like this. Please correct me if it's incorrect.
Add the following inside MediatedGuiceModule
http://code.google.com/p/mediated-opensocial/source/browse/trunk/shindig/com/shop/opensocial/mediated/shindig/config/MediatedGuiceModule.java
@Override
protected void configure() {
...
bind(OAuthStore.class).toProvider(CustomOAuthStoreProvider.class);
...
}
public static class CustomOAuthStoreProvider implements
Provider<OAuthStore> {
private final CustomOAuthTokenStore store;
public CustomOAuthStoreProvider() {
store = new CustomOAuthTokenStore();
}
public OAuthStore get() {
return store;
}
}
On Thu, Jan 22, 2009 at 5:00 PM, Jordan Zimmerman <jo...@shop.com> wrote:
> >Implementing this should involve implementing the
> >SecurityTokenDecoder and OAuthConsumerStore interfaces.
> You mean OAuthStore, I think. Also, I don't see where
> SecurityTokenDecoder comes into play or how I'm supposed to implement
> it.
>
> Another question: What about OAuthModule? It appears to be necessary so
> that some of the Shindig OAuth internals are initialized. But, how am I
> supposed to tell Guice about my OAuthStore implementation?
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> All your favorite stores.
> OneCart(r) convenience.
> www.shop.com
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
RE: OAuth and Shindig
Posted by Jordan Zimmerman <jo...@shop.com>.
>Implementing this should involve implementing the
>SecurityTokenDecoder and OAuthConsumerStore interfaces.
You mean OAuthStore, I think. Also, I don't see where
SecurityTokenDecoder comes into play or how I'm supposed to implement
it.
Another question: What about OAuthModule? It appears to be necessary so
that some of the Shindig OAuth internals are initialized. But, how am I
supposed to tell Guice about my OAuthStore implementation?
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
All your favorite stores.
OneCart(r) convenience.
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: OAuth and Shindig
Posted by Paul Lindner <pl...@hi5.com>.
There are some docs on implementing client side here:
http://code.google.com/apis/orkut/docs/rest/developers_guide_protocol.html
architecture is here: 2-legged OAuth for the OpenSocial REST API
Implementing this should involve implementing the SecurityTokenDecoder
and OAuthConsumerStore interfaces.
On Jan 22, 2009, at 12:34 PM, Jordan Zimmerman wrote:
> The only doc I've found re OAuth and Shindig is here:
> http://cwiki.apache.org/confluence/display/SHINDIG/Enabling+OAuth+suppor
> t
>
> Are there any other docs? Figuring out what I need to do is clear as
> mud.
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> All your favorite stores.
> OneCart(r) convenience.
> www.shop.com
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.