[
https://issues.apache.org/jira/browse/DERBY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474945
]
John H. Embretsen commented on DERBY-2361:
------------------------------------------
My 2 cents:
I would say document all possible security mechanisms (with examples), even the
defaults - it won't hurt. Just mark the defaults as defaults in certain
scenarios. The defaults may change in the future, and having all options
documented will save us some work when that happens.
Also, I think the following page needs to be updated to also mention the
STRONG_PASSWORD_SUBSTITUTE_SECURITY mechanism (but perhaps that is something
for another Jira):
http://db.apache.org/derby/docs/dev/adminguide/cadminapps811631.html
> 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
>
> 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.
