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] [Resolved] (DERBY-5376) Documentation should state authentication/authorization requirements more strongly
Date Mon, 08 Aug 2011 13:56:27 GMT

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

Kim Haase resolved DERBY-5376.

       Resolution: Fixed
    Fix Version/s:

Thanks very much, Dag and Rick.

Committed patch DERBY-5376-2.diff to documentation trunk at revision 1154958. 
Merged to 10.8 doc branch at revision 1154966.

> Documentation should state authentication/authorization requirements more strongly
> ----------------------------------------------------------------------------------
>                 Key: DERBY-5376
>                 URL: https://issues.apache.org/jira/browse/DERBY-5376
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>             Fix For:,
>         Attachments: DERBY-5376-2.diff, DERBY-5376-2.zip, DERBY-5376.diff, DERBY-5376.diff,
DERBY-5376.stat, DERBY-5376.zip
> The Administration Guide and Developer's Guide should state more strongly the importance
of securing a multi-user Derby system by implementing authentication and authorization. I
have found two Admin Guide topics and one Dev Guide topic where this information can most
usefully be added.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message