[DERBY-4503] Documentation needs note on purpose of built-in authentication mechanism

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 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
• Fix Version/s: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.5.3.1, 10.6.1.0
• Component/s: Documentation
• Assignee: Camilla Haase
• Reporter: Camilla Haase
• Created: 04/Jan/10 22:11
• Updated: 05/Jul/10 16:39
• Resolved: 06/Jan/10 23:17

Description

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.