db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-963) Allow user friendly string values for security mechanism in client connection url.
Date Sun, 12 Nov 2006 18:59:38 GMT
    [ http://issues.apache.org/jira/browse/DERBY-963?page=comments#action_12449165 ] 
Knut Anders Hatlen commented on DERBY-963:

Wow! Almost five months since the patch was submitted, and no comments yet! Sorry about that!

I think the suggested patch looks good. My only comment is that I'm not sure ClientBaseDataSource.getSecurityMechanism(java.util.Properties)
should throw client.am.SqlException since it is part of our public API. java.sql.SQLException
would perhaps have been better. But to be frank, I don't understand why getSecurityMechanism(Properties)
is part of our public API in the first place.

> Allow user friendly string values for security mechanism in client connection url.
> ----------------------------------------------------------------------------------
>                 Key: DERBY-963
>                 URL: http://issues.apache.org/jira/browse/DERBY-963
>             Project: Derby
>          Issue Type: Improvement
>          Components: Newcomer, Network Client
>    Affects Versions:,,,,,,
>            Reporter: Sunitha Kambhampati
>         Assigned To: Anders Morken
>            Priority: Minor
>         Attachments: DERBY-963-code-v1.patch
> Overview:
> DRDA spec specifies the following secmec (securitymechanism) values.
> Currently in the client url, one would have to pass in the integer value for securityMechanism.
> ij>connect 'testdb;securityMechanism=9;user=sa;password=p1';
> when using the datasource, the setSecurityMechanism(int) on the ClientDataSource can
be used.
> Constants are
> ClientDataSource.USER_ONLY_SECURITY (0x04)
> Add support in client to recognize the user friendly names for the securityMechanism
attribute. The values that should be accepted are CLEAR_TEXT_PASSWORD_SECURITY, USER_ONLY_SECURITY,
> --------
> To ensure that the old applications that were written to pass in an integer value for
securityMechanism do not break with the new client , the client should probably support both
the integer values as well as the string values.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message