Greetings Luc, Can you open an issue in JIRA for this situation? This seems like it will be a problem in many environments that do not allow for unauthenticated access.
On Tue, Dec 1, 2009 at 12:33 PM, Luc Castera <[email protected]> wrote: > Paul & Louis, > > Thanks for your help. It is really appreciated! > > I found the config you mentionned in container.js and was able to solve > my problem. > > Turns out I had changed the following line in SocialAPIGuiceModule.java: > > bind(Boolean.class) > > > .annotatedWith(Names.named(AnonymousAuthenticationHandler.ALLOW_UNAUTHENTICATED)) > .toInstance(Boolean.TRUE); > > to FALSE. > > And the call to social/rpc was failing due to authentication, with the > following message: > > {"message":"unauthorized: The request did not have a proper security > token nor oauth message and unauthenticated requests are not > allowed","code":401} > > I set it to TRUE and it is now allowing that call to be completed. > However, it is also allowing all calls to my REST endpoints to be > accessed without authentication and I would like to prevent that. > > How can I let the social/rpc introspection call go through without > authentication without removing authentication for all my REST > endpoints? > > Thank you, > > Luc > > > > On Mon, 2009-11-30 at 11:40 -0800, Louis Ryan wrote: > > Luc > > > > You may be better off directly defining the exposed JSON-RPC services in > > your Shindig container.js rather than relying on the service > introspection. > > This is documented inside the sample container.js file provided with > > Shindig. > > > > -Louis > > > > On Mon, Nov 30, 2009 at 9:31 AM, Paul Lindner <[email protected]> wrote: > > > > > When shindig starts it makes a request to to /social/rpc to get the > list of > > > available methods. See container.js sections "osapi" and > "osapi.services" > > > for ways to hard-code the list or change the endpoints used. > > > > > > > > > On Mon, Nov 30, 2009 at 6:18 AM, Luc Arthur Castera > > > <[email protected]>wrote: > > > > > > > Paul, > > > > > > > > When I load the gadget that uses osapi.people, I get a javascript > error > > > in > > > > Firebug: osapi.people is undefined > > > > > > > > I also see the following warning coming from rpc.js: Unknown RPC > service: > > > > osapi._handleGadgetRpcMethod > > > > > > > > On the shindig logs, I see the following error: > > > > > > > > Nov 30, 2009 9:06:59 AM > > > > org.apache.shindig.gadgets.render.DefaultServiceFetcher > retrieveServices > > > > SEVERE: Failed to parse services methods from endpoint > > > > http://localhost:8080/social/rpc. JSONObject["data"] not found. > > > > > > > > My environment is the following: > > > > - Ubuntu 9.10 > > > > - Java 1.6.0_16 > > > > - Java version of Shindig (Trunk: SVN Revision 818615) > > > > > > > > I appreciate your help with this, > > > > > > > > Luc > > > > > > > > > > > > > > > > On Fri, Nov 27, 2009 at 5:45 AM, Paul Lindner <[email protected]> > wrote: > > > > > > > > > osapi should 'just work' if you specify <Require feature="osapi"/> > in > > > > your > > > > > ModulePrefs. What behavior are you observing? Do you get the osapi > > > > classes > > > > > loaded? Is there any error with 'listMethods' in your shindig > logs? > > > > > > > > > > Can you provide more information about your environment? Java/PHP? > > > > > Javascript Errors? etc.... > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > On Wed, Nov 25, 2009 at 5:10 PM, Luc Arthur Castera > > > > > <[email protected]>wrote: > > > > > > > > > > > Hey, > > > > > > > > > > > > I wrote a gadget that uses the OS lite api (osapi.people, > > > > osapi.appdata, > > > > > > etc...). When I test the gadget on iGoogle, it works fine but > when I > > > > try > > > > > it > > > > > > on my local shindig instance, it is not working properly. It > looks > > > like > > > > > the > > > > > > osapi.people and osapi.appdata are not implemented in Shindig. > > > > > > > > > > > > FYI, I have written my adapters for my local shindig instance and > I > > > am > > > > > able > > > > > > to use the older JS APIs without any issue. > > > > > > > > > > > > Are we suppose to implement the osapi.js libraries ourselves when > we > > > > > build > > > > > > our container or is it just that the shindig implementation > hasn't > > > > > > implemented these newer APIs yet? > > > > > > > > > > > > Any pointers of the issue would be greatly helpful. I tried to > search > > > > the > > > > > > mailing list but could not find anything on that matter. > > > > > > > > > > > > Thank you, > > > > > > > > > > > > Luc > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > ______________________ > > > > Luc Castera > > > > > > > > > > -- > ______________________ > Luc Castera > Founder, ShareMeme Inc. > http://messagepub.com > Phone: 786-877-3789 > Skype: luc.castera > >
