[
https://issues.apache.org/jira/browse/DERBY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476547
]
John H. Embretsen commented on DERBY-2361:
------------------------------------------
Kim, your comments make sense to me. I leave it to your own judgment to decide
how to proceed with the nits I listed.
Regarding general cleanup of the security topics, I think there is already an
issue covering client/server aspects, although the description and comments are
slightly outdated at the moment: DERBY-474 ("Improve Network Server security
documentation").
Also, I agree that a wiki page won't be a substitute for whatever is or should
be in the manuals, but it could be a useful starting point if, for example,
developers want to work on this documentation task but are reluctant to do it
because of the overhead (or learning curve?) associated with working with Dita
source, etc.
> Documentation should give examples for using the different security mechanisms
> ------------------------------------------------------------------------------
>
> Key: DERBY-2361
> URL: https://issues.apache.org/jira/browse/DERBY-2361
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.2.2.0
> Reporter: Andrew McIntyre
> Assigned To: Kim Haase
> Attachments: DERBY-2361.diff, DERBY-2361.zip, rrefattribsecmech.dita
>
>
> The Derby Server and Administration guide talks about the different security
> mechanisms, but does not give examples of how these can be used via
> connection URLs, it only mentions the client DataSource field names.
> http://db.apache.org/derby/docs/10.2/adminguide/cadminapps49914.html
> The documentation should give examples of how to use the different security
> mechanisms via connection URLs, and perhaps an example of how the client
> field names would be used programmatically.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
