[
https://issues.apache.org/jira/browse/DERBY-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5636:
-----------------------------
Attachment: DERBY-5636-2.zip
DERBY-5636-2.stat
DERBY-5636-2.diff
I'm attaching DERBY-5636-2.diff, DERBY-5636-2.stat, and DERBY-5636-2.zip, this
time with the following changes:
M src/devguide/cdevcbabejdfj.dita
M src/devguide/cdevcsecure10983.dita
M src/devguide/cdevbabejgjd.dita
M src/devguide/cdevcsecure871387.dita
M src/devguide/rdevcsecure871422.dita
M src/devguide/rdevcsecure871406.dita
M src/devguide/rdevcsecure871439.dita
The substantive changes are to "Notes on the Derby security features",
cdevcsecure10983.dita. The other fixes clean up obsolete language and links in
the security policy topics.
Any and all fixes to these are welcome. Thanks again, 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-2.diff, DERBY-5636-2.stat, DERBY-5636-2.zip,
> 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
