db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-963) Allow user friendly string values for security mechanism in client connection url.
Date Mon, 08 Dec 2008 16:34:44 GMT

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

Kathey Marsden reassigned DERBY-963:
------------------------------------

    Assignee:     (was: Anders Morken)

> Allow user friendly string values for security mechanism in client connection url.
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-963
>                 URL: https://issues.apache.org/jira/browse/DERBY-963
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Client, Newcomer
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6
>            Reporter: Sunitha Kambhampati
>            Priority: Minor
>         Attachments: DERBY-963-code-v1.patch
>
>
> Overview:
> DRDA spec specifies the following secmec (securitymechanism) values.
> USRIDONL = 4
> USRIDPWD = 3
> USRSSBPWD = 8
> 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.STRONG_PASSWORD_SUBSTITUTE_SECURITY (0x08)
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message