db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2361) Documentation should give examples for using the different security mechanisms
Date Wed, 21 Feb 2007 19:04:05 GMT

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

Andrew McIntyre commented on DERBY-2361:
----------------------------------------

Looking in ClientBaseDataSource, if password is not supplied, USER_ONLY_SECURITY is the default.
If a password is supplied, then CLEAR_TEXT_PASSWORD is used. It appears from reading the code
that the security mechanism is automatically upgraded to ENCRYPTED_USER_AND_PASSWORD on supported
JVMs, at the moment that is only IBM VMs.

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


Mime
View raw message