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

Kim Haase updated DERBY-6217:
-----------------------------

    Attachment: DERBY-6217.zip
                DERBY-6217.stat
                DERBY-6217.diff

Attaching DERBY-6217.diff, DERBY-6217.stat, and DERBY-6217.zip, with a 
preliminary draft of a new security guide. The material pulled from the 
Developer's Guide has "csecure" in the file name, while the new material and 
the material pulled from the Admin Guide don't. The new material, mostly drawn 
from an updated but unpublished whitepaper, consists mostly of the Part One 
material and most of the topics introducing the sections in Part Two, as well 
as the final "Putting it all together" section. I've left out topics that the 
new material makes redundant.

Please let me know what changes, additions, etc. would be helpful. Thanks very 
much, Rick, for answering questions in email now and then while I was working 
on this.

Once this content is reasonably settled (but before I commit anything) I will 
file another patch that removes the security material from the Admin Guide and 
Developer's Guide and that creates links to the new Security Guide as 
appropriate. 

> Put all of the security documentation in a single, separate user guide
> ----------------------------------------------------------------------
>
>                 Key: DERBY-6217
>                 URL: https://issues.apache.org/jira/browse/DERBY-6217
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-6217.diff, DERBY-6217.stat, DERBY-6217.zip
>
>
> Right now the security documentation is divided among our user guides. This 
> makes is hard for customers to understand Derby's defenses and how to 
> configure all relevant security mechanisms for an application. As 
> demonstrated by the discussion on DERBY-6160, some security mechanisms 
> involve multiple Derby jar files and multiple application tiers. Material for 
> these mechanisms is scattered across the existing user guides. It would be 
> less confusing if all of Derby's security documentation were separated out 
> into a new Security Guide.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to