[jira] Commented: (DERBY-4503) Documentation needs note on purpose of built-in authentication mechanism

["Rick Hillegas (JIRA)" <ji...@apache.org>]

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

Rick Hillegas commented on DERBY-4503:
--------------------------------------

Thanks for these patches, Kim. The wording of the warning looks good to me.

I looked at the html output. The formatting of the warning looks a little odd on a couple of the files. It would look better to me if there were an additional line break before the warning. In some cases, perhaps the warning could be merged into the preceding paragraph instead:

trunk and 10.5:

  cdevsetprop824451.html

trunk, 10.5, 10.4, 10.3, 10.2, 10.1:

  rdevsecure557.html
  tdevsecure81850.html
  tdevsecure82556.html

Thanks!


> 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.diff, DERBY-4503-10.1.stat, DERBY-4503-10.1.zip, DERBY-4503-10.2.diff, DERBY-4503-10.2.stat, DERBY-4503-10.2.zip, DERBY-4503-10.3.diff, DERBY-4503-10.3.stat, DERBY-4503-10.3.zip, DERBY-4503-10.4.diff, DERBY-4503-10.4.stat, DERBY-4503-10.4.zip, DERBY-4503-10.5.diff, DERBY-4503-10.5.stat, DERBY-4503-10.5.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.