The biggest hurdle is connecting to your oauth consumer key store (slightly different for inbound vs. outbound). Assuming you've already done the necessary legwork to connect other persistence mechanisms (people, activities), this shouldn't be too different though.
Once that's set up, you still need to provide the appropriate UI for the actual user sign in flow. There's a basic implementation of this for the outbound, gadget-initiated case, but for inbound oauth you need to make sure that relevant endpoints are set up appropriately. This is largely beyond the scope of Shindig itself, since Shindig is only worried about handling requests and not performing the initial authentication. On Thu, Jan 22, 2009 at 12:33 AM, Jordan Zimmerman <[email protected]> wrote: > I'm assuming that the OAuth classes > (OAuthConsumerRequestAuthenticationHandler et al) are production ready. > Is there anything I need to implement to complete the OAuth integration > for production? > > > > Jordan Zimmerman > Principal Software Architect > 831.647.4712 > 831.214.2990 (cell) > [email protected] <mailto:[email protected]> > > SHOP*COMTM > All your favorite stores. > OneCart(r) convenience. > www.shop.com <http://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.
