Sergio Juan wrote:
Hi.
I'm currently working in a complex web application. In a stage of development, we
wanted to control access to files
from the users, and we got all the logic in a SecurityManager of its own. As we were
not very familiar with all the
capacities of the Security Manager, we
Hi.
I'm currently working in a complex web application. In a stage of development, we
wanted to control access to files from the users, and we got all the logic in a
SecurityManager of its own. As we were not very familiar with all the capacities of
the Security Manager, we chose for the
This could be caused by using the deprecated HTTP1.1 connector rather than
the new Coyote Connector in server.xml.
Jake
At 10:06 AM 6/6/2003 +0200, you wrote:
Hi.
I'm currently working in a complex web application. In a stage of
development, we wanted to control access to files from the
]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Friday, June 06, 2003 4:39 PM
Subject: Re: Problem with SecurityManager and jmx
This could be caused by using the deprecated HTTP1.1 connector rather than
the new Coyote Connector in server.xml.
Jake
At 10:06 AM 6/6/2003 +0200, you wrote:
Hi.
I'm
How do i configure the Security Manager to use different policies for each
host/webapp/webapp(libs/classes)?
Example:
1. Install a clean Tomcat 4.1.xx
2. Creating a simple jsp page in examples/securityTest.jsp
securityTest.jsp
---
% secure.secureClass.readPasswd() %
---
I am encountering a big problem when trying to use Tomcat's security
manager. I have set the following lines in the policy file:
grant codeBase "file:${tomcat.home}/webapps/PFOCE" {
permission java.net.SocketPermission "1.2.3.4:1024-65535", "accept,
connect, listen, resolve";
I am encountering a big problem when trying to use Tomcat's security
manager. I have set the following lines in the policy file:
grant codeBase "file:${tomcat.home}/webapps/PFOCE" {
permission java.net.SocketPermission "1.2.3.4:1024-65535", "accept,
connect, listen, resolve";
