db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6160) Fixes needed to documentation topics on security policy permissions
Date Wed, 01 May 2013 12:58:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646552#comment-13646552
] 

Kim Haase commented on DERBY-6160:
----------------------------------

Thanks, Dag -- I will omit the JDK 7 reference in the basic policy, so I think that topic
is all set.

I realize I left a dangling sentence in my paragraph about the Customizing topic -- I am still
perplexed by why the customized policy looks so different from the basic one, especially the
derbynet.jar part of it. 

http://db.apache.org/derby/docs/10.10/adminguide/tadminnetservbasic.html
http://db.apache.org/derby/docs/10.10/adminguide/tadminnetservcustom.html

It's hard to know what exactly needs changing.
                
> 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

Mime
View raw message