You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2014/06/04 20:25:02 UTC
[jira] [Resolved] (DERBY-6217) Put all of the security
documentation in a single, separate user guide
[ https://issues.apache.org/jira/browse/DERBY-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-6217.
------------------------------
Resolution: Fixed
Fix Version/s: 10.11.0.0
Issue & fix info: (was: Patch Available)
> 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
> Fix For: 10.11.0.0
>
> Attachments: DERBY-6217-2.diff, DERBY-6217-3.diff, DERBY-6217-admin.diff, DERBY-6217-admin.stat, DERBY-6217-admin.zip, DERBY-6217-conref.diff, DERBY-6217-dev.diff, DERBY-6217-dev.stat, DERBY-6217-dev.zip, DERBY-6217-fixptrs1.diff, DERBY-6217-fixptrs1.stat, DERBY-6217-fixptrs1.zip, DERBY-6217-fixptrs2.diff, DERBY-6217.diff, DERBY-6217.stat, DERBY-6217.zip, rtoolsijcomref61092.html
>
>
> 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)