db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Morken (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-963) Allow user friendly string values for security mechanism in client connection url.
Date Fri, 30 Jun 2006 21:54:37 GMT
    [ http://issues.apache.org/jira/browse/DERBY-963?page=comments#action_12418721 ] 

Anders Morken commented on DERBY-963:

I've actually had a patch for this in my trunk checkout for a while, but it's been forgotten
and rotting away as I haven't yet, uhm, "found the inspiration" to write regression tests
and doc patches for it. I'll see about it soon. =)

> 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
>         Type: Improvement

>   Components: Newcomer, Network Client
>     Versions:,,,,,,,,,,,
>     Reporter: Sunitha Kambhampati
>     Assignee: Anders Morken
>     Priority: Minor

> 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:
For more information on JIRA, see:

View raw message