[
https://issues.apache.org/jira/browse/DERBY-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238691#comment-13238691
]
Kim Haase commented on DERBY-5636:
----------------------------------
This is odd -- I committed the patch 4+ hours ago, but the commit message has
not shown up yet. I got an error when I did an svn update recently, but not any
more.
Anyhow, I committed patch DERBY-5636.diff to documentation trunk at revision
1305386. It's in my log ...
I will move on to making the fixes to "Notes on the Derby security features"
and will file a second patch. Thanks very much for the suggestions, Rick.
> Improve the overview of Derby's security mechanisms
> ---------------------------------------------------
>
> Key: DERBY-5636
> URL: https://issues.apache.org/jira/browse/DERBY-5636
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-5636.diff, DERBY-5636.stat, DERBY-5636.zip
>
>
> The documentation on Derby's security mechanisms is scattered across several
> manuals. This makes it hard for developers to figure out which security
> mechanisms are relevant for a given application. Here are 3 places where
> security documentation appears:
> 1) In the Developer's Guide section titled "Derby and security"
> 2) In the Admin Guide section titled "Derby Network Server advanced topics"
> 3) In the Reference Manual section titled "Derby properties" as well as the
> syntax sections on GRANT, REVOKE, CREATE/DROP ROLE, and CREATE
> FUNCTION/PROCEDURE.
> It would be good to add a section which points the developer at all of this
> material. It might be sufficient to rewrite the top level "Derby and
> security" page of the Developer's Guide. The following white paper may help
> organize our thoughts about this:
> http://www.oracle.com/technetwork/java/javadb/securitywhitepaper10-159253.pdf
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
