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

    [ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797239#action_12797239
] 

Kim Haase commented on DERBY-4503:
----------------------------------

Thanks, Rick! 

Committed patch DERBY-4503-trunk-2.diff to documentation trunk at revision 896613. 

Branch commits to follow.

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


Mime
View raw message