Get Latest Updates
Apache shindig is one of the famous gadget applications used accross various social sites. The technology used in the backend for this shindig application is XML/JS/CSS/HTML. The front end application page will be html and gadgets are available in the format of XML embedded in html.
The shindig application URL looks like http://host:port/ShindigApp/index.htm. The Shindig application is deployed in Tomcat front ended by Apache Server. We installed a OAM 10g WebGate on Apache server and protected the above URL. Upon accessing the application it is redirecting to page where it shows “404 page not found”. It is imperative that in OAM 11g, webgates have DenyOnNotProtected value set to true by default there by all unprotected URLs will be denied with access.
So I have used headers tool to find more specifics.
The Apache Shindig application calls js URL internally while loading the application. The URL looks like
The Shindig is loading the rpc.js which is not present in the shindig application – so I can’t make it out where exactly it is picking up. Upon googling I found that this is normal behavior of shindig while loading gadgets.
So I have specified this URL as resource and save the resource. Since the URL has ../ the policy manager got corrupted and console was showing null entries for all policies.
I am petrified with this. Atlast we have recovered the policy manager back to working state by some sql scripts – this is a topic for another day.
So the choice to unprotecting shindig URLs is faded out. So I have tried setting DenyOnNotProtected flag to false and reconfigured webgate and I am able to access the OAM protected shindig application well.
Hope this is useful.