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] [Updated] (DERBY-6217) Put all of the security documentation in a single, separate user guide
Date Tue, 03 Jun 2014 19:05:02 GMT

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

Kim Haase updated DERBY-6217:

    Attachment: rtoolsijcomref61092.html

Attaching DERBY-6217-fixptrs2.diff and rtoolsijcomref61092.html, with the correction to the
referenced topic name in a tools topic:

M       src/tools/rtoolsijcomref61092.dita

Will commit shortly.

> 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:
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         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

View raw message