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

Kim Haase resolved DERBY-5769.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
    Issue & fix info:   (was: Patch Available)

Thanks again, Rick. 

Committed patch DERBY-5769-2.diff to documentation trunk at revision 1340150. 
                
> 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
>             Fix For: 10.9.0.0
>
>         Attachments: DERBY-5769-2.diff, DERBY-5769-2.zip, DERBY-5769.diff, 
> DERBY-5769.stat, DERBY-5769.zip
>
>
> 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

        

Reply via email to