Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 17 May 2012 20:12:03 +0000 (UTC)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <559982308.10644.1337285523530.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (DERBY-5769) Notes deprecating BUILTIN
 authentication need fixing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kim Haase created DERBY-5769:
--------------------------------

             Summary: Notes deprecating BUILTIN authentication need fixing
                 Key: DERBY-5769
                 URL: https://issues.apache.org/jira/browse/DERBY-5769
             Project: Derby
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 10.9.0.0
            Reporter: Kim Haase
            Assignee: Kim Haase


In reviewing a DERBY-5767 patch, Rick Hillegas noticed that in the derby.authentication.provider topic, "In the second, longer paragraph of the BUILTIN bullet, we recommend LDAP and user-supplied schemes as alternatives to BUILTIN, but we don't recommend NATIVE. Did we decide to not recommend NATIVE here or should this be adjusted to include it beside the other safe schemes? Thanks."

In several topics, the notes were not modified to recommend NATIVE authentication the same way they were elsewhere: "It is strongly recommended that production systems rely on NATIVE authentication, an external directory service such as LDAP, or a user-defined class for authentication." These notes need to be tidied up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira