commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CONFIGURATION-391) Double file permissions required in WAS 6.1
Date Thu, 24 Mar 2016 20:13:26 GMT

     [ https://issues.apache.org/jira/browse/CONFIGURATION-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oliver Heger updated CONFIGURATION-391:
---------------------------------------
    Fix Version/s:     (was: 2.0)
                   2.x

> Double file permissions required in WAS 6.1
> -------------------------------------------
>
>                 Key: CONFIGURATION-391
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-391
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.5
>         Environment: - WebSphere AS 6.1with J2EE securit enabled
> - AIX
>            Reporter: St├ęphane Van Espen
>             Fix For: 2.x
>
>
> We are using Commons Configuration as follows: 
> {code}
> final PropertiesConfiguration config = new PropertiesConfiguration("velocity.properties");
> {code}
> _Noteworthy points_:
> - properties files  are embedded in JARs
> - Application is deployed in WAS 6.1, where J2EE security is activated (was.policy)
> *Problem is the following*:
> Two entries are necessary in _was.policy_ in order to make the application work.
> Example:
> {code}
> permission java.io.FilePermission "velocity.properties","read";
> permission java.io.FilePermission "/home/wasadmin/velocity.properties","read";
> {code}
> The first entry is valid.
> The second entry (with "/*home*/*wasadmin*/...") is wrong but necesarry in order to make
WebSphere happy.
> We would like to remove this second entry (useless and less secure) from our was.policy.
> What could be the cause of this issue ?
> Thank you,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message