You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Dov Rosenberg <do...@conviveon.com> on 2005/12/13 01:10:13 UTC
Securing File System Resources ?
Our application has its own security model that controls access to our
information based on our own roles and permissions. We store files related
to our application on the file system where our application is running.
These associated files are served out by a web server. Our goal is to come
up with a scheme where we could apply our security model to control access
to these files via the web server. For example someone associates a PDF
with some meta data. We don¹t want the user to be able to bookmark the
underlying URL and email it to their friends for them to download without
having them authenticated by our service.
We are looking at a couple of different ideas.
1. Create a servlet filter to sit in front of the resources requests and
somehow tie that into our application logic
2. Create a regular proxy type of servlet that can accept requests and
validate them using our security model
3. Figure out a way to secure the filesystem using a Proxy server of some
type.
Any other thoughts or ideas are appreciated. Thanks in advance
--
Dov Rosenberg
Conviveon/Inquira
Knowledge Management Experts
http://www.conviveon.com
http://www.inquira.com
Re: Securing File System Resources ?
Posted by Ryan Slack <ry...@evine.ca>.
Dov Rosenberg wrote:
> How would a proxy server affect the equation? One thought was to use a proxy
> server to validate the user, and see if that authorization flag can be
> passed along to any embedded links within the page. We could then use a
> filter to inspect the HTTP header on the request and determine if the user
> has been authenticated before allowing the request to go forward.
>
> Thanks in advance
>
> Dov
>
>
> On 12/13/05 12:13 PM, "Ryan Slack" <ry...@evine.ca> wrote:
>
>
>>Dov Rosenberg wrote:
>>
>>>Our application has its own security model that controls access to our
>>>information based on our own roles and permissions. We store files related
>>>to our application on the file system where our application is running.
>>>These associated files are served out by a web server. Our goal is to come
>>>up with a scheme where we could apply our security model to control access
>>>to these files via the web server. For example someone associates a PDF
>>>with some meta data. We don¹t want the user to be able to bookmark the
>>>underlying URL and email it to their friends for them to download without
>>>having them authenticated by our service.
>>>
>>>We are looking at a couple of different ideas.
>>>
>>>1. Create a servlet filter to sit in front of the resources requests and
>>>somehow tie that into our application logic
>>>2. Create a regular proxy type of servlet that can accept requests and
>>>validate them using our security model
>>>3. Figure out a way to secure the filesystem using a Proxy server of some
>>>type.
>>>
>>>Any other thoughts or ideas are appreciated. Thanks in advance
>>>
>>>
>>>
>>
>>Filter and container enforced security is mainly good for pattern based
>>criteria. Are you looking to give permissions based on a name pattern,
>>like *.pdf, or somedir/*.pdf? Otherwise you need a database of
>>permissions and mappings, such as what Jaas/SecurityManager based
>>applications rely on.
>>On top of that, you options may be limited by how your security model
>>works. For example, you /could/ use a seperate servlet ala web.xml, but
>>if your security model relies on all requests going through one servlet,
>>you're better off with a filter.
>>
>>Savy?
>>--Ryan
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
What kind of proxy server do you mean? A proxy servlet? An http proxy
server (like Squid or Apache)?
If you really want to use a proxy server sure, but why not just use a
filter and the session? Do you really expect to get that many 'bad'
requests as to load your web-server beyond it's capacity?
Also, I don't see how this is really Tapestry related, or even Tomcat
for that matter, seen as your "application has its own security model".
Savy?
--Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Securing File System Resources ?
Posted by Dov Rosenberg <do...@conviveon.com>.
How would a proxy server affect the equation? One thought was to use a proxy
server to validate the user, and see if that authorization flag can be
passed along to any embedded links within the page. We could then use a
filter to inspect the HTTP header on the request and determine if the user
has been authenticated before allowing the request to go forward.
Thanks in advance
Dov
On 12/13/05 12:13 PM, "Ryan Slack" <ry...@evine.ca> wrote:
>
> Dov Rosenberg wrote:
>> Our application has its own security model that controls access to our
>> information based on our own roles and permissions. We store files related
>> to our application on the file system where our application is running.
>> These associated files are served out by a web server. Our goal is to come
>> up with a scheme where we could apply our security model to control access
>> to these files via the web server. For example someone associates a PDF
>> with some meta data. We don¹t want the user to be able to bookmark the
>> underlying URL and email it to their friends for them to download without
>> having them authenticated by our service.
>>
>> We are looking at a couple of different ideas.
>>
>> 1. Create a servlet filter to sit in front of the resources requests and
>> somehow tie that into our application logic
>> 2. Create a regular proxy type of servlet that can accept requests and
>> validate them using our security model
>> 3. Figure out a way to secure the filesystem using a Proxy server of some
>> type.
>>
>> Any other thoughts or ideas are appreciated. Thanks in advance
>>
>>
>>
> Filter and container enforced security is mainly good for pattern based
> criteria. Are you looking to give permissions based on a name pattern,
> like *.pdf, or somedir/*.pdf? Otherwise you need a database of
> permissions and mappings, such as what Jaas/SecurityManager based
> applications rely on.
> On top of that, you options may be limited by how your security model
> works. For example, you /could/ use a seperate servlet ala web.xml, but
> if your security model relies on all requests going through one servlet,
> you're better off with a filter.
>
> Savy?
> --Ryan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Securing File System Resources ?
Posted by Dov Rosenberg <do...@conviveon.com>.
How would a proxy server affect the equation? One thought was to use a proxy
server to validate the user, and see if that authorization flag can be
passed along to any embedded links within the page. We could then use a
filter to inspect the HTTP header on the request and determine if the user
has been authenticated before allowing the request to go forward.
Thanks in advance
Dov
On 12/13/05 12:13 PM, "Ryan Slack" <ry...@evine.ca> wrote:
>
> Dov Rosenberg wrote:
>> Our application has its own security model that controls access to our
>> information based on our own roles and permissions. We store files related
>> to our application on the file system where our application is running.
>> These associated files are served out by a web server. Our goal is to come
>> up with a scheme where we could apply our security model to control access
>> to these files via the web server. For example someone associates a PDF
>> with some meta data. We don¹t want the user to be able to bookmark the
>> underlying URL and email it to their friends for them to download without
>> having them authenticated by our service.
>>
>> We are looking at a couple of different ideas.
>>
>> 1. Create a servlet filter to sit in front of the resources requests and
>> somehow tie that into our application logic
>> 2. Create a regular proxy type of servlet that can accept requests and
>> validate them using our security model
>> 3. Figure out a way to secure the filesystem using a Proxy server of some
>> type.
>>
>> Any other thoughts or ideas are appreciated. Thanks in advance
>>
>>
>>
> Filter and container enforced security is mainly good for pattern based
> criteria. Are you looking to give permissions based on a name pattern,
> like *.pdf, or somedir/*.pdf? Otherwise you need a database of
> permissions and mappings, such as what Jaas/SecurityManager based
> applications rely on.
> On top of that, you options may be limited by how your security model
> works. For example, you /could/ use a seperate servlet ala web.xml, but
> if your security model relies on all requests going through one servlet,
> you're better off with a filter.
>
> Savy?
> --Ryan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Securing File System Resources ?
Posted by Ryan Slack <ry...@evine.ca>.
Dov Rosenberg wrote:
> Our application has its own security model that controls access to our
> information based on our own roles and permissions. We store files related
> to our application on the file system where our application is running.
> These associated files are served out by a web server. Our goal is to come
> up with a scheme where we could apply our security model to control access
> to these files via the web server. For example someone associates a PDF
> with some meta data. We don¹t want the user to be able to bookmark the
> underlying URL and email it to their friends for them to download without
> having them authenticated by our service.
>
> We are looking at a couple of different ideas.
>
> 1. Create a servlet filter to sit in front of the resources requests and
> somehow tie that into our application logic
> 2. Create a regular proxy type of servlet that can accept requests and
> validate them using our security model
> 3. Figure out a way to secure the filesystem using a Proxy server of some
> type.
>
> Any other thoughts or ideas are appreciated. Thanks in advance
>
>
>
Filter and container enforced security is mainly good for pattern based
criteria. Are you looking to give permissions based on a name pattern,
like *.pdf, or somedir/*.pdf? Otherwise you need a database of
permissions and mappings, such as what Jaas/SecurityManager based
applications rely on.
On top of that, you options may be limited by how your security model
works. For example, you /could/ use a seperate servlet ala web.xml, but
if your security model relies on all requests going through one servlet,
you're better off with a filter.
Savy?
--Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Securing File System Resources ?
Posted by Ryan Slack <ry...@evine.ca>.
Dov Rosenberg wrote:
> Our application has its own security model that controls access to our
> information based on our own roles and permissions. We store files related
> to our application on the file system where our application is running.
> These associated files are served out by a web server. Our goal is to come
> up with a scheme where we could apply our security model to control access
> to these files via the web server. For example someone associates a PDF
> with some meta data. We don¹t want the user to be able to bookmark the
> underlying URL and email it to their friends for them to download without
> having them authenticated by our service.
>
> We are looking at a couple of different ideas.
>
> 1. Create a servlet filter to sit in front of the resources requests and
> somehow tie that into our application logic
> 2. Create a regular proxy type of servlet that can accept requests and
> validate them using our security model
> 3. Figure out a way to secure the filesystem using a Proxy server of some
> type.
>
> Any other thoughts or ideas are appreciated. Thanks in advance
>
>
>
Filter and container enforced security is mainly good for pattern based
criteria. Are you looking to give permissions based on a name pattern,
like *.pdf, or somedir/*.pdf? Otherwise you need a database of
permissions and mappings, such as what Jaas/SecurityManager based
applications rely on.
On top of that, you options may be limited by how your security model
works. For example, you /could/ use a seperate servlet ala web.xml, but
if your security model relies on all requests going through one servlet,
you're better off with a filter.
Savy?
--Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Securing File System Resources ?
Posted by Dov Rosenberg <do...@conviveon.com>.
We would prefer the file was a one off access so they couldn't send the link
to their buddies. In most cases the user would be authenticated via either a
SSO solution or our own.
Thanks again for the feedback.
On 12/13/05 8:31 AM, "ALEX HYDE" <al...@btinternet.com> wrote:
> Version 1 is the way I did.
>
> Things I had to bare in mind are:
> - are you actually logging users in or are they authorised on a per
> individual file basis
> - can the user re-access the file or is it a one off access?
>
> Gluck
>
> David Smith <dn...@cornell.edu> wrote: Either one or two are excellent choices
> with 1 being the best IMHO. It
> could be as simple as some other servlet places a flag in the session
> that essentially says this user is good for downloading this file for
> this session. The servlet filter sees that and offers the file, or
> failing to see the the flag, redirects the user to a friendly error page.
>
> -David
>
> Dov Rosenberg wrote:
>
>> Our application has its own security model that controls access to our
>> information based on our own roles and permissions. We store files related
>> to our application on the file system where our application is running.
>> These associated files are served out by a web server. Our goal is to come
>> up with a scheme where we could apply our security model to control access
>> to these files via the web server. For example someone associates a PDF
>> with some meta data. We don¹t want the user to be able to bookmark the
>> underlying URL and email it to their friends for them to download without
>> having them authenticated by our service.
>>
>> We are looking at a couple of different ideas.
>>
>> 1. Create a servlet filter to sit in front of the resources requests and
>> somehow tie that into our application logic
>> 2. Create a regular proxy type of servlet that can accept requests and
>> validate them using our security model
>> 3. Figure out a way to secure the filesystem using a Proxy server of some
>> type.
>>
>> Any other thoughts or ideas are appreciated. Thanks in advance
>>
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Securing File System Resources ?
Posted by ALEX HYDE <al...@btinternet.com>.
Version 1 is the way I did.
Things I had to bare in mind are:
- are you actually logging users in or are they authorised on a per individual file basis
- can the user re-access the file or is it a one off access?
Gluck
David Smith <dn...@cornell.edu> wrote: Either one or two are excellent choices with 1 being the best IMHO. It
could be as simple as some other servlet places a flag in the session
that essentially says this user is good for downloading this file for
this session. The servlet filter sees that and offers the file, or
failing to see the the flag, redirects the user to a friendly error page.
-David
Dov Rosenberg wrote:
>Our application has its own security model that controls access to our
>information based on our own roles and permissions. We store files related
>to our application on the file system where our application is running.
>These associated files are served out by a web server. Our goal is to come
>up with a scheme where we could apply our security model to control access
>to these files via the web server. For example someone associates a PDF
>with some meta data. We don¹t want the user to be able to bookmark the
>underlying URL and email it to their friends for them to download without
>having them authenticated by our service.
>
>We are looking at a couple of different ideas.
>
>1. Create a servlet filter to sit in front of the resources requests and
>somehow tie that into our application logic
>2. Create a regular proxy type of servlet that can accept requests and
>validate them using our security model
>3. Figure out a way to secure the filesystem using a Proxy server of some
>type.
>
>Any other thoughts or ideas are appreciated. Thanks in advance
>
>
>
>
>
--
=======================================
David Smith
Network Operations Supervisor
Department of Entomology
College of Agriculture & Life Sciences
Cornell University
2132 Comstock Hall
Ithaca, NY 14853
Phone: 607.255.9571
Fax: 607.255.0939
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.
Re: Securing File System Resources ?
Posted by David Smith <dn...@cornell.edu>.
Either one or two are excellent choices with 1 being the best IMHO. It
could be as simple as some other servlet places a flag in the session
that essentially says this user is good for downloading this file for
this session. The servlet filter sees that and offers the file, or
failing to see the the flag, redirects the user to a friendly error page.
-David
Dov Rosenberg wrote:
>Our application has its own security model that controls access to our
>information based on our own roles and permissions. We store files related
>to our application on the file system where our application is running.
>These associated files are served out by a web server. Our goal is to come
>up with a scheme where we could apply our security model to control access
>to these files via the web server. For example someone associates a PDF
>with some meta data. We don¹t want the user to be able to bookmark the
>underlying URL and email it to their friends for them to download without
>having them authenticated by our service.
>
>We are looking at a couple of different ideas.
>
>1. Create a servlet filter to sit in front of the resources requests and
>somehow tie that into our application logic
>2. Create a regular proxy type of servlet that can accept requests and
>validate them using our security model
>3. Figure out a way to secure the filesystem using a Proxy server of some
>type.
>
>Any other thoughts or ideas are appreciated. Thanks in advance
>
>
>
>
>
--
=======================================
David Smith
Network Operations Supervisor
Department of Entomology
College of Agriculture & Life Sciences
Cornell University
2132 Comstock Hall
Ithaca, NY 14853
Phone: 607.255.9571
Fax: 607.255.0939
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Securing File System Resources ?
Posted by Carl Olivier <ca...@unysen.co.uk>.
Hi.
I have used option 1 in your list with no problem. Others seem ok, but I
have not tried them - have an innate paranoia about proxies I guess.
Rgds,
Carl
-----Original Message-----
From: Dov Rosenberg [mailto:dov.rosenberg@conviveon.com]
Sent: 13 December 2005 00:10
To: WebObjects Dev; Tapestry users; Tomcat Users List
Subject: Securing File System Resources ?
Our application has its own security model that controls access to our
information based on our own roles and permissions. We store files related
to our application on the file system where our application is running.
These associated files are served out by a web server. Our goal is to come
up with a scheme where we could apply our security model to control access
to these files via the web server. For example someone associates a PDF
with some meta data. We don¹t want the user to be able to bookmark the
underlying URL and email it to their friends for them to download without
having them authenticated by our service.
We are looking at a couple of different ideas.
1. Create a servlet filter to sit in front of the resources requests and
somehow tie that into our application logic 2. Create a regular proxy type
of servlet that can accept requests and validate them using our security
model 3. Figure out a way to secure the filesystem using a Proxy server of
some type.
Any other thoughts or ideas are appreciated. Thanks in advance
--
Dov Rosenberg
Conviveon/Inquira
Knowledge Management Experts
http://www.conviveon.com
http://www.inquira.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org