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-4503) Documentation needs note on purpose of built-in authentication mechanism
Date Wed, 06 Jan 2010 23:18:54 GMT

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

Kim Haase resolved DERBY-4503.

          Resolution: Fixed
       Fix Version/s:
    Issue & fix info:   (was: [Patch Available])

Committed fixes to trunk and to 10.5, 10.4, 10.3, 10.2, and 10.1 branches. 

Marking as fixed in the latest released version for each since that is presumably what is
available on the documentation page.

> Documentation needs note on purpose of built-in authentication mechanism
> ------------------------------------------------------------------------
>                 Key: DERBY-4503
>                 URL: https://issues.apache.org/jira/browse/DERBY-4503
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:,,,,,,,,,,,,,,
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>             Fix For:,,,,
>         Attachments: DERBY-4503-10.1-2.diff, DERBY-4503-10.1-2.zip, DERBY-4503-10.1.diff,
DERBY-4503-10.1.stat, DERBY-4503-10.1.zip, DERBY-4503-10.2-2.diff, DERBY-4503-10.2-2.zip,
DERBY-4503-10.2.diff, DERBY-4503-10.2.stat, DERBY-4503-10.2.zip, DERBY-4503-10.3-2.diff, DERBY-4503-10.3-2.zip,
DERBY-4503-10.3.diff, DERBY-4503-10.3.stat, DERBY-4503-10.3.zip, DERBY-4503-10.4-2.diff, DERBY-4503-10.4-2.zip,
DERBY-4503-10.4.diff, DERBY-4503-10.4.stat, DERBY-4503-10.4.zip, DERBY-4503-10.5-2.diff, DERBY-4503-10.5-2.zip,
DERBY-4503-10.5.diff, DERBY-4503-10.5.stat, DERBY-4503-10.5.zip, DERBY-4503-trunk-2.diff,
DERBY-4503-trunk-2.zip, DERBY-4503-trunk.diff, DERBY-4503-trunk.stat, DERBY-4503-trunk.zip
> The Derby documentation does not make it clear that Derby's built-in authentication mechanism
is intended for development and testing use but should not be deployed in production systems.
Such systems should use LDAP or a user-written mechanism.
> This should be fixed in the trunk and in the documentation for releases 10.1 through
> The note needs to be added to one topic in the Admin Guide, two topics in the Reference
Manual (the Tuning Guide in 10.4 and earlier releases), and a varying number of topics in
the Developer's Guide, ranging from 7 in 10.1 through 10.3 to 13 in the trunk.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message