[
https://issues.apache.org/jira/browse/DERBY-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635459#comment-13635459
]
Kim Haase commented on DERBY-6160:
----------------------------------
Actually, if we are removing derby.storage.jvmInstanceId, we also need to
change the template in the code repository:
/java/drda/org/apache/derby/drda/server.policy
That could be a separate issue, since it's not documentation.
> 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.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
