[
https://issues.apache.org/jira/browse/JSPWIKI-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132929#comment-18132929
]
ASF subversion and git services commented on JSPWIKI-877:
---------------------------------------------------------
Commit 7f472f893d83ff1e3940d1471a23c524dec20240 in jspwiki's branch
refs/heads/master from Arturo Bernal
[ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=7f472f893 ]
JSPWIKI-877 Accept an absolute path for the security policy file
Engine.findConfigFile only looked under WEB-INF and on the classpath, so
jspwiki.policy.file=/some/dir/custom.policy was never found and the wiki failed
to start with "Could not initialize local security policy". The filter
configuration already falls back to a plain file path; the policy file now does
too, as findConfigFile returns the file when its name is the absolute path of an
existing file.
> Allow jspwiki.properties filterConfig and policy.file to have fully qualified
> paths
> -----------------------------------------------------------------------------------
>
> Key: JSPWIKI-877
> URL: https://issues.apache.org/jira/browse/JSPWIKI-877
> Project: JSPWiki
> Issue Type: Bug
> Components: Core & storage
> Affects Versions: 2.10.1
> Reporter: David Vittor
> Assignee: David Vittor
> Priority: Major
> Labels: pull-request-available
> Attachments: JSPWIKI-877.patch
>
>
> Currently adding the following properties does not work:
> * jspwiki.policy.file=C:/temp/jspwiki-custom.policy
> * jspwiki.filterConfig=C:/temp/jspwiki-filters.xml
> The policy file only checks certain locations, and not fully qualified paths.
> The filterConfig has the same problem, but does work in linux, but not in
> windows as this expects a URL, e.g. file:/C:/temp/... but this causes a
> SEVERE filterStart error in tomcat.
> Note: These seem to be inconsistant with UserDatabase and GroupDatabase
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
