db-derby-dev mailing list archives

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

Thanks for taking a look at the patch, Knut Anders and John. As you might have noticed in
my "patch - committer feedback - new patch" roundtrip times, I'm not in any particular hurry.
;-) (Actually I've got a final refinement for DERBY-801 tested and ready in my working copy...
just haven't posted it here yet. =)

I'll see if I can throw together an updated patch - as I mentioned earlier, it needs doc and
test suite updates as well to be of any use. =)

> 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: 10.2.1.6, 10.0.2.2, 10.1.1.0, 10.1.3.1, 10.0.2.1, 10.0.2.0, 10.1.2.1
>            Reporter: Sunitha Kambhampati
>         Assigned To: Anders Morken
>            Priority: Minor
>         Attachments: DERBY-963-code-v1.patch
>
>
> Overview:
> DRDA spec specifies the following secmec (securitymechanism) values.
> USRIDONL = 4
> USRIDPWD = 3
> EUSRIDPWD = 9
> Currently in the client url, one would have to pass in the integer value for securityMechanism.
e.g.
> 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.CLEAR_TEXT_PASSWORD_SECURITY (0x03)
> ClientDataSource.USER_ONLY_SECURITY (0x04)
> ClientDataSource.ENCRYPTED_USER_AND_PASSWORD_SECURITY (0x09)
> 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,
ENCRYPTED_USER_AND_PASSWORD_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

        

Mime
View raw message