You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Rich Joslin <ma...@opusnet.com> on 2002/06/28 19:20:06 UTC
Tomcat Manager App
Has anyone built a GUI for the Tomcat manager app? Not that I want to
get all Macromessya on it or anything, but it would be cool to have all
those commands on one screen I think.
Opinions?
- Rich
RE: Tomcat Manager App
Posted by Rich Joslin <ma...@opusnet.com>.
Thanks. :-)
I also was informed that there are details on how to download a visual
app right in the config files! I guess I should read more. Hehe
Thanks, all.
- Rich
-----Original Message-----
From: Lars Nielsen Lind [mailto:moonie@worldonline.dk]
Sent: Friday, June 28, 2002 10:47 AM
To: Tomcat Users List
Subject: Re: Tomcat Manager App
Rich Joslin wrote:
>Has anyone built a GUI for the Tomcat manager app? Not that I want to
>get all Macromessya on it or anything, but it would be cool to have all
>those commands on one screen I think.
>
>Opinions?
>
>- Rich
>
>
Hi.
See: http://www.linuxservermanager.com, where GUI-APP will soon be
available.
Best regards,
Lars Nielsen Lind
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Tomcat Manager App
Posted by Lars Nielsen Lind <mo...@worldonline.dk>.
Rich Joslin wrote:
>Has anyone built a GUI for the Tomcat manager app? Not that I want to
>get all Macromessya on it or anything, but it would be cool to have all
>those commands on one screen I think.
>
>Opinions?
>
>- Rich
>
>
Hi.
See: http://www.linuxservermanager.com, where GUI-APP will soon be
available.
Best regards,
Lars Nielsen Lind
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Security Realm Limitations (More on protecting PDF documents.)
Posted by Brad Rhoads <br...@zethcon.com>.
Is there an API that so I can update the web.xml programaticly?
Other options that wouldn't require restarting Tomcat? While the # of PDFs
will not change often, access will. I assume I'd also have to restart Tomcat
to change <auth-contraint>s; It looks like I'll have to create a role for
each user.
Along the same lines, it looks like the JDBC Realm let's you specify a DB
table for users, but for resources and their roles???
-----Original Message-----
From: August Detlefsen [mailto:augustd123@yahoo.com]
Sent: Friday, June 28, 2002 4:16 PM
To: Tomcat Users List; brhoads@zethcon.com
Subject: Re: Security Realm Limitations (More on protecting PDF
documents.)
You can define a different <security-restraint> for each PDF, and
assign the required roles to that:
<security-constraint>
<web-resource-collection>
<web-resource-name>PDF for Group One</web-resource-name>
<url-pattern>/group_1_only.pdf</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>group1</role-name>
</auth-constraint>
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>PDF for Group Two</web-resource-name>
<url-pattern>/group_2_only.pdf</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>group2</role-name>
</auth-constraint>
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>Shared PDF</web-resource-name>
<url-pattern>/everybody.pdf</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>group1</role-name>
<role-name>group2</role-name>
</auth-constraint>
</security-constraint>
This will make for a big, unwieldy web.xml though, and it will require
restarting tomcat every time you add a new PDF (do they change
frequently)?
Do security constraints follow symlinks? Maybe you could create two
protcted directories (group1, group2) and then symlink the files from a
central repository?
--- Brad Rhoads <br...@zethcon.com> wrote:
>
> I've determined that I can use security realms to protect PDF
> documents.
> (See http://jakarta.apache.org/tomcat/tomcat-4.0-doc/realm-howto.html
> if you
> happen to be getting started on this problem).
>
> I need to be able to give access to one set of pdfs to one group of
> users,
> and to different sets for other groups of users. It looks like I can
> accomplish this much by creating separate directories for each group
> and
> setting up a role for each group. But I have two related problems
> left:
>
> 1. The same PDF may be available to multiple groups. It seems that I
> would
> have to maintain duplicate copies of the PDFs, one for each group.
>
> 2. This group level security provides the base list of available
> PDFs. I
> need to be able to take away access to documents from certain users
> within a
> group.
>
> Suggestions? Or better yet examples?
>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Security Realm Limitations (More on protecting PDF documents.)
Posted by August Detlefsen <au...@yahoo.com>.
You can define a different <security-restraint> for each PDF, and
assign the required roles to that:
<security-constraint>
<web-resource-collection>
<web-resource-name>PDF for Group One</web-resource-name>
<url-pattern>/group_1_only.pdf</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>group1</role-name>
</auth-constraint>
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>PDF for Group Two</web-resource-name>
<url-pattern>/group_2_only.pdf</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>group2</role-name>
</auth-constraint>
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>Shared PDF</web-resource-name>
<url-pattern>/everybody.pdf</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>group1</role-name>
<role-name>group2</role-name>
</auth-constraint>
</security-constraint>
This will make for a big, unwieldy web.xml though, and it will require
restarting tomcat every time you add a new PDF (do they change
frequently)?
Do security constraints follow symlinks? Maybe you could create two
protcted directories (group1, group2) and then symlink the files from a
central repository?
--- Brad Rhoads <br...@zethcon.com> wrote:
>
> I've determined that I can use security realms to protect PDF
> documents.
> (See http://jakarta.apache.org/tomcat/tomcat-4.0-doc/realm-howto.html
> if you
> happen to be getting started on this problem).
>
> I need to be able to give access to one set of pdfs to one group of
> users,
> and to different sets for other groups of users. It looks like I can
> accomplish this much by creating separate directories for each group
> and
> setting up a role for each group. But I have two related problems
> left:
>
> 1. The same PDF may be available to multiple groups. It seems that I
> would
> have to maintain duplicate copies of the PDFs, one for each group.
>
> 2. This group level security provides the base list of available
> PDFs. I
> need to be able to take away access to documents from certain users
> within a
> group.
>
> Suggestions? Or better yet examples?
>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Security Realm Limitations (More on protecting PDF documents.)
Posted by Brad Rhoads <br...@zethcon.com>.
I've determined that I can use security realms to protect PDF documents.
(See http://jakarta.apache.org/tomcat/tomcat-4.0-doc/realm-howto.html if you
happen to be getting started on this problem).
I need to be able to give access to one set of pdfs to one group of users,
and to different sets for other groups of users. It looks like I can
accomplish this much by creating separate directories for each group and
setting up a role for each group. But I have two related problems left:
1. The same PDF may be available to multiple groups. It seems that I would
have to maintain duplicate copies of the PDFs, one for each group.
2. This group level security provides the base list of available PDFs. I
need to be able to take away access to documents from certain users within a
group.
Suggestions? Or better yet examples?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Tomcat Manager App
Posted by Rich Joslin <ma...@opusnet.com>.
More great information from the man himself.
I'm really starting to like this list.
Thanks again!
=]
- Rich
-----Original Message-----
From: Craig R. McClanahan [mailto:craigmcc@apache.org]
Sent: Friday, June 28, 2002 11:09 AM
To: Tomcat Users List
Subject: Re: Tomcat Manager App
On Fri, 28 Jun 2002, Rich Joslin wrote:
> Date: Fri, 28 Jun 2002 10:20:06 -0700
> From: Rich Joslin <ma...@opusnet.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: Tomcat Manager App
>
> Has anyone built a GUI for the Tomcat manager app? Not that I want to
> get all Macromessya on it or anything, but it would be cool to have
> all those commands on one screen I think.
>
There is an HTML-ized version of the manager servlet that you can
configure instead in the web.xml of the manager webapp (see that web.xml
file for details). But that's not really the right approach, IMHO.
> Opinions?
The primary reason that I made the manager webapp in the first place was
to make it easy to integrate into development tools that wanted to
wupport dynamic deployment of applications, rather than for direct use
from a browser. Two existing examples are quite interesting:
* In the Java Web Services Developer Pack (JWSDP), you will find a
modified version of "deploytool" from the J2EE reference
implementation
that is a Swing-based GUI for building and deploying webapps. It uses
the Manager webapp facilities behind the scenes.
http://java.sun.com/webservices/
* Tomcat 4.1.x (and the JWSDP) includes a library of custom Ant tasks
so that you can build application deployment and undeployment directly
into your build scripts. Again, they just talk to the Manager
webapp's
commands in the background.
Using a user-friendly HTML interface would make it much more difficult
to integrate client applications, which is why it's there at all.
(The admin webapp in Tomcat 4.1.x and JWSDP also lets you tweak
configuration parameters on running webapps, but it's not the easiest
way to deploy new ones).
>
> - Rich
>
>
Craig
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Tomcat Manager App
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Fri, 28 Jun 2002, Rich Joslin wrote:
> Date: Fri, 28 Jun 2002 10:20:06 -0700
> From: Rich Joslin <ma...@opusnet.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: Tomcat Manager App
>
> Has anyone built a GUI for the Tomcat manager app? Not that I want to
> get all Macromessya on it or anything, but it would be cool to have all
> those commands on one screen I think.
>
There is an HTML-ized version of the manager servlet that you can
configure instead in the web.xml of the manager webapp (see that web.xml
file for details). But that's not really the right approach, IMHO.
> Opinions?
The primary reason that I made the manager webapp in the first place was
to make it easy to integrate into development tools that wanted to wupport
dynamic deployment of applications, rather than for direct use from a
browser. Two existing examples are quite interesting:
* In the Java Web Services Developer Pack (JWSDP), you will find a
modified version of "deploytool" from the J2EE reference implementation
that is a Swing-based GUI for building and deploying webapps. It uses
the Manager webapp facilities behind the scenes.
http://java.sun.com/webservices/
* Tomcat 4.1.x (and the JWSDP) includes a library of custom Ant tasks
so that you can build application deployment and undeployment directly
into your build scripts. Again, they just talk to the Manager webapp's
commands in the background.
Using a user-friendly HTML interface would make it much more difficult to
integrate client applications, which is why it's there at all.
(The admin webapp in Tomcat 4.1.x and JWSDP also lets you tweak
configuration parameters on running webapps, but it's not the easiest way
to deploy new ones).
>
> - Rich
>
>
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>