You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2010/01/04 23:12:54 UTC
[jira] Created: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
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.5.3.0, 10.5.2.0, 10.5.1.1, 10.4.2.0, 10.4.1.3, 10.3.3.0, 10.3.2.1, 10.3.1.4, 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0
Reporter: Kim Haase
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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797270#action_12797270 ]
Kim Haase commented on DERBY-4503:
----------------------------------
Committed patch DERBY-4503-10.4-2.diff to 10.4 branch at revision 896639.
> 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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797346#action_12797346 ]
Kim Haase commented on DERBY-4503:
----------------------------------
Committed patch DERBY-4503-10.2-2.diff to 10.2 branch at revision 896694.
> 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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Issue & fix info: [Patch Available] (was: [Known fix])
> 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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.3-2.zip
DERBY-4503-10.3-2.diff
Attaching DERBY-4503-10.3-2.diff and DERBY-4503-10.3-2.zip, containing revised patch and HTML files for 10.3.
> 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-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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.2.zip
DERBY-4503-10.2.stat
DERBY-4503-10.2.diff
Attaching DERBY-4503-10.2.diff, DERBY-4503-10.2.stat, and DERBY-4503-10.2.zip, adding notes to topics that discuss the built-in security mechanism in the 10.2 documentation.
> 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.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.
[jira] Resolved: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-4503.
------------------------------
Resolution: Fixed
Fix Version/s: 10.1.3.1
10.2.2.0
10.3.3.0
10.4.2.0
10.5.3.0
Issue & fix info: (was: [Patch Available])
Committed fixes to trunk and to 10.5, 10.4, 10.3, 10.2, and 10.1 branches.
Marking as fixed in the latest released version for each since that is presumably what is available on the documentation page.
> 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
> Fix For: 10.5.3.0, 10.4.2.0, 10.3.3.0, 10.2.2.0, 10.1.3.1
>
> 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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.2-2.zip
DERBY-4503-10.2-2.diff
Attaching DERBY-4503-10.2-2.diff and DERBY-4503-10.2-2.zip, containing revised patch and HTML files for 10.2.
> 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-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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.4-2.zip
DERBY-4503-10.4-2.diff
Attaching DERBY-4503-10.4-2.diff and DERBY-4503-10.4-2.zip, containing revised patch and HTML files for 10.4.
> 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-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.
[jira] Closed: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase closed DERBY-4503.
----------------------------
Changes appear in latest alpha manuals, so closing issue.
> 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
> Fix For: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.5.4.0, 10.6.0.0
>
> 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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797382#action_12797382 ]
Kim Haase commented on DERBY-4503:
----------------------------------
Committed patch DERBY-4503-10.1-2.diff to 10.1 branch at revision 896710.
> 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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.4.zip
DERBY-4503-10.4.stat
DERBY-4503-10.4.diff
Attaching DERBY-4503-10.4.diff, DERBY-4503-10.4.stat, and DERBY-4503-10.4.zip, adding notes to topics that discuss the built-in security mechanism in the 10.4 documentation.
> 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.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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.5-2.zip
DERBY-4503-10.5-2.diff
Attaching DERBY-4503-10.5-2.diff and DERBY-4503-10.5-2.zip, containing revised patch and HTML files for 10.5 docs.
> 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-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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.1.zip
DERBY-4503-10.1.stat
DERBY-4503-10.1.diff
Attaching DERBY-4503-10.1.diff, DERBY-4503-10.1.stat, and DERBY-4503-10.1.zip, adding notes to topics that discuss the built-in security mechanism in the 10.1 documentation.
No change is planned for the 10.0 documentation, since this release probably has few if any users at this point, and since I don't know how to generate this documentation. If anyone knows how to do it and thinks it would be worthwhile, please say so.
> 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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.1-2.zip
DERBY-4503-10.1-2.diff
Attaching DERBY-4503-10.1-2.diff and DERBY-4503-10.1-2.zip, containing revised patch and HTML files for 10.1.
I forgot to mention that for some releases (trunk down to 10.3, I recall) I also corrected a typo in the table in rdevcsecure557.dita (noticed a missing space).
> 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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797258#action_12797258 ]
Kim Haase commented on DERBY-4503:
----------------------------------
Committed patch DERBY-4503-10.5-2.diff to 10.5 branch at revision 896627.
> 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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796817#action_12796817 ]
Kim Haase commented on DERBY-4503:
----------------------------------
Thanks. I also notice odd spacing in one of the reference/tuning files. I'm making formatting changes that fix these (I hope). Will post revised patches.
> 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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.5.zip
DERBY-4503-10.5.stat
DERBY-4503-10.5.diff
Attaching DERBY-4503-10.5.diff, DERBY-4503-10.5.stat, and DERBY-4503-10.5.zip, adding notes to topics that discuss the built-in security mechanism in the 10.5 documentation.
> 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.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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Fix Version/s: 10.6.0.0
10.5.4.0
> 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
> Fix For: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.5.4.0, 10.6.0.0
>
> 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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797308#action_12797308 ]
Kim Haase commented on DERBY-4503:
----------------------------------
Committed patch DERBY-4503-10.3-2.diff to 10.3 branch at revision 896665.
> 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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-trunk.zip
DERBY-4503-trunk.stat
DERBY-4503-trunk.diff
Attaching DERBY-4503-trunk.diff, DERBY-4503-trunk.stat, and DERBY-4503-trunk.zip, adding notes to topics that discuss the built-in security mechanism in the trunk documentation.
> 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-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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-trunk-2.zip
DERBY-4503-trunk-2.diff
Attaching revised patch and HTML files for trunk.
Caveat: the formatting fixes are not visible without the stylesheet, which is not included in the zip file. When the stylesheet is included, there generally aren't any visible problems in the HTML in the unfixed files, but there are issues with the HTML-single and PDFs.
Some of the releases don't include the stylesheets -- which means that they'll look bad even with the formatting fixes. But that's a separate issue, I guess.
> 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-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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797193#action_12797193 ]
Rick Hillegas commented on DERBY-4503:
--------------------------------------
Thanks, Kim. With the style sheet these look great.
> 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.
[jira] Updated: (DERBY-4503) Documentation needs note on purpose of
built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4503:
-----------------------------
Attachment: DERBY-4503-10.3.zip
DERBY-4503-10.3.stat
DERBY-4503-10.3.diff
Attaching DERBY-4503-10.3.diff, DERBY-4503-10.3.stat, and DERBY-4503-10.3.zip, adding notes to topics that discuss the built-in security mechanism in the 10.3 documentation.
> 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.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.
[jira] Commented: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (DERBY-4503) Documentation needs note on purpose
of built-in authentication mechanism
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-4503:
--------------------------------
Assignee: Kim Haase
> 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
>
> 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.