On Thu, Jan 30, 2003 at 01:46:28AM +0000, [EMAIL PROTECTED] wrote: > Let there be a malicious user who knows you are using Xindice. He can > easily access all your xindic collections through the simple API. There > is no guarantee that the data will not be traversed by another java > application. > How is it "easily enough" for the programmer to limit access? > > I know there are plans to make a collection with authentication, maybe > sub-collections as well. But how can you dismiss this ? Am I missing > something?
I can understand leaving authentication and authorization out of the core, but I too find it puzzling that the default method of accessing collections in that case isn't the embedded mode. If that were the case, you could indeed limit access to the database, as long as you trust code running in the same VM (which could be an issue in a servlet context, I guess). The default setup does not allow you to limit access at all, unless you consider a firewall between Xindice and the rest of the world enough. Emile
