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] Assigned: (DERBY-4503) Documentation needs note on purpose of built-in authentication mechanism
Date Mon, 04 Jan 2010 22:12:54 GMT

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

Kim Haase reassigned DERBY-4503:

    Assignee: Kim Haase

> 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
> 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