[
https://issues.apache.org/jira/browse/DERBY-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647274#comment-13647274
]
Dag H. Wanvik commented on DERBY-6160:
--------------------------------------
I think the Customizing topic need to be updated so it reflects current reality.
It should essentially be the same as the template except that it further
restricts and adds things as discussed in the introductory bullet points, I
believe.
To make things clearer, we could describe the restrictions (FilePermissions)
and additions (SocketPermission) and the omission of the MBeans related
permissions first, then show the entire policy file at the end.
Or, if you like I could have a crack at a draft of the above.
> Fixes needed to documentation topics on security policy permissions
> -------------------------------------------------------------------
>
> Key: DERBY-6160
> URL: https://issues.apache.org/jira/browse/DERBY-6160
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.9.1.0, 10.10.1.1
> Reporter: Kathey Marsden
> Assignee: Kim Haase
> Attachments: DERBY-6160-2.diff, DERBY-6160-2.stat, DERBY-6160-2.zip,
> DERBY-6160.diff, DERBY-6160.stat, DERBY-6160.zip
>
>
> DERBY-5363 added a new required permission RuntimePermission
> "accessUserInformation".
> This should be added to the developer guide information under granting
> permissions to Derby.
> https://builds.apache.org/job/Derby-docs/lastSuccessfulBuild/artifact/trunk/out/devguide/cdevbabejgjd.html
> I am not sure of the context under which it is required if it is just needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
