Hi all,
Having tried several times to run tomcat (with apache) using the
SecurityManager,
my idea was simply to set the permissions for running the Tomcat example
servlets and JSP provided.
For that I:
1. Edited server.xml to use Policy:
ContextInterceptor className="org.apache.tomcat.context.P
Look at tomcat.sh, the shell arg "-security" needs to be shifted out so it isn't
passed on as an option just before java org.apache.tomcat.startup.Tomcat is started.
BTW, this is fixed for the next Tomcat 3.2.x release.
Regards,
Glenn
Gauri Sukhatankar wrote:
>
> Hi,
>
> I am having problems
Hi,
> 1. Edited server.xml to use Policy:
>
> 2. Edited tomcat.policy
> 3. Started tomcat with the "-security" option.
>>> tomcat.sh start -security
Are you sure you granted the right permission the the right codebase ?
It is very important to have TOMCAT_HOME set before running the server
Hi,
I am having problems in using the SecurityManager with tomcat 3.2.1.
There seems to be a bug or documention mismatch.
Please let me know if you have any ideas on fixing this:
I am using Tomcat 3.2.1 to run a servlet that acts as an RMI client.
Based on the documentation
(http://jakarta.ap
