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

Kim Haase updated DERBY-2361:
-----------------------------

    Attachment: rrefattribsecmech.dita
                DERBY-2361.zip
                DERBY-2361.diff

Thanks, Sunitha, for the information about the attribute values.

I'm attaching DERBY-2361.diff and DERBY-2361.zip, along with the new source 
file ref/rrefattribsecmech.dita to document the connection URL attribute. The 
diffs include changes to adminguide/cadminapps49914.dita and 
cadminapps811631.dita. Some of the cadminapps49914 changes are formatting 
corrections; I hope that's all right. The diffs also add the new 
rrefattribsecmech.dita file to the map file for the Reference Manual. I have 
done an svn add for this file.

Please let me know what additional changes are needed.

> 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.

Reply via email to