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 2010/01/04 23:22:54 UTC
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-trunk.zip
DERBY-4503-trunk.stat
DERBY-4503-trunk.diff
Attaching DERBY-4503-trunk.diff, DERBY-4503-trunk.stat, and DERBY-4503-trunk.zip, adding notes to topics that discuss the built-in security mechanism in the trunk documentation.
> 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: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Attachments: 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 10.5.
> 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.