Anonymous | Login | Signup for a new account | 12-17-2024 10:58 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0003657 | [Resin] | minor | always | 08-28-09 09:04 | 08-31-09 15:13 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.2 | Product Version | |||||
Product Build | |||||||||
Summary | 0003657: JSP CodeSource for security manager | ||||||||
Description |
(rep by Kai Virkki) We are trying to use SecurityManager with Resin 3.1.9 and run into the following problem: CodeSource.getLocation() returns null for compiled JSPs. This means that we cannot use a specific codebase in grant clause in our policy file, for example: grant codeBase "file:/path_to_resin/runtime/work/-" { OR grant codeBase "file:/path_to_resin/webapp/JSP-source/-" { ...some jsp-specific permissions }; Instead, we have to use a universal grant clause: grant { ..some jsp-specific permissions. Unfortunately, these will be applied to all code!!! }; Is there a way to make JSPs have a proper CodeSource? |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |