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

Kim Haase resolved DERBY-6160.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.10.1.2
    Issue & fix info:   (was: Patch Available)

Thanks, Dag! I forgot I'd already created an issue for the template.policy and 
server.policy file -- DERBY-6207. 

I wouldn't have a problem with updating the template to match what we put in 
the admin guide, but am a bit nervous about materially changing the 
server.policy file, since that is apparently the one that Derby actually uses.

Committed patch DERBY-6160-4.diff to documentation trunk at revision 1481853.
Merged to 10.10 doc branch at revision 1481877.

I don't know if it makes sense to merge this patch back farther than 10.10. I 
don't think all the technical changes apply at earlier releases.
                
> 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
>             Fix For: 10.10.1.2
>
>         Attachments: customizing.txt, DERBY-6160-2.diff, DERBY-6160-2.stat, 
> DERBY-6160-2.zip, DERBY-6160-3.diff, DERBY-6160-3.zip, DERBY-6160-4.diff, 
> DERBY-6160-4.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

Reply via email to