On Mon, Jan 12, 2009 at 10:05 PM, Stuart Lewis <[email protected]> wrote:
> Hi Andrew,
>
> > I mistakenly thought that my access denied problem with DSpace and xmlui
> was
> > to do with logging. Actually I think it might be to do with the default
> java
> > security policy, which might be more strictly enforced in java6. I think
> I
> > need some sort of 'grant' directive for File.Permission but I am not sure
> > exactly what. Also I don't want it to go in the global policy file, but
> > rather, one that is specific to DSpace (xmlui). Can anyone help me
> please?
>
> You'll want to grant Tomcat the permission to read and write to files and
> directories in [dspace]/ and other directories such as the search index
> directories if they are stored outside of [dspace] (e.g. we keep our search
> indexes on local disks, and [dspace] on a mounted external server).
Yes, it looks like I need to do this. I have been granting access file by
file, which is slow and painful, but it is making the problem retreat.
> You can be more precise if you want (e.g. just read permissions for
> [dspace]/config/*
That sounds alot more convenient than file by file.
> http://tomcat.apache.org/tomcat-6.0-doc/security-manager-howto.htmlsuggests
> that it is only possible to have a single catalina.policy file for a tomcat
> instance, not one per webapp.
Well, I must admit, I am putting it into the global policy file for now.
Maybe that's just as well.
I think that a policy file needs to be included in the DSpace release for
when people are using java6 with the stricter security. Shall I file this as
a defect?
--
Regards,
Andrew M.
http://www.andrewpetermarlow.co.uk
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
