If you want to use a secure token, you'll need to generate keys. If you have figured out some way to avoid needing secure tokens, you can just use the non secure versions. For secure tokens, security is contingent on having unique keys.
On Mon, Aug 17, 2009 at 10:46 AM, Dominick Accattato <[email protected]>wrote: > I get the same warning. Are we supposed to create this file since it > doesn't exist in the tree? > > On Mon, Aug 17, 2009 at 12:34 PM, tog <[email protected]> wrote: > > > Hi, > > > > I am quite new to shindig and my goal is to build an "opensocial > > capable" application using grails. > > Has someone get a similar experience ? > > > > So far I am able to test trunk using jetty from the command line and > > tomcat. > > My only point is the following message ... but I am not able to find > > any gadgets.properties in the directory tree. Can anyone help ? > > > > WARNING: Couldn't load OAuth signing key. To create a key, run: > > openssl req -newkey rsa:1024 -days 365 -nodes -x509 -keyout testkey.pem > \ > > -out testkey.pem -subj '/CN=mytestkey' > > openssl pkcs8 -in testkey.pem -out oauthkey.pem -topk8 -nocrypt -outform > > PEM > > > > Then edit gadgets.properties and add these lines: > > shindig.signing.key-file=<path-to-oauthkey.pem> > > shindig.signing.key-name=mykey > > > > > > What is the best way to play with the opensocial data container ? Is > > there some tiny application using this backend. I already had a look > > to: > > - SocialSite (which is not using Shindig) > > - mediated-opensocial but this is from my point of view an extension > > rather that an application using it. > > > > Thanks for your help > > > > Guillaume > > >
