You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2014/08/18 20:34:18 UTC

[jira] [Updated] (DERBY-6680) Other jar files may need to be granted permission to read derby.ui.* properties

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

Dag H. Wanvik updated DERBY-6680:
---------------------------------

    Summary: Other jar files may need to be granted permission to read derby.ui.* properties  (was: All jar files need to be granted permission to read derby.ui.* properties)

> Other jar files may need to be granted permission to read derby.ui.* properties
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-6680
>                 URL: https://issues.apache.org/jira/browse/DERBY-6680
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.11.1.1
>            Reporter: Rick Hillegas
>            Assignee: Dag H. Wanvik
>
> The following properties may be read by LocalizedResource, a class which is included in derby.jar, derbynet.jar, derbyclient.jar, and derbytools.jar:
> {noformat}
> derby.ui.codeset
> derby.ui.locale
> {noformat}
> A user has tripped across this problem in production. With the user's language settings, the network server fails to come up because the server policy file does not grant the server permission to read these properties. See http://apache-database.10148.n7.nabble.com/Hellow-I-have-some-problem-in-customize-security-policy-with-derby-modified-3-td141002.html
> We should adjust server.policy and template.policy accordingly.



--
This message was sent by Atlassian JIRA
(v6.2#6252)