You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org> on 2012/02/21 23:52:50 UTC
[jira] [Updated] (DERBY-1755) Add support to client to be able to
retry a connection request with a server supported secmec.
[ https://issues.apache.org/jira/browse/DERBY-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-1755:
----------------------------------
Urgency: Low
Labels: derby_triage10_9 (was: )
Triage for 10.9. Setting Urgency low. We haven't seen requests for this that I know of.
> Add support to client to be able to retry a connection request with a server supported secmec.
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-1755
> URL: https://issues.apache.org/jira/browse/DERBY-1755
> Project: Derby
> Issue Type: Improvement
> Components: Network Client, Network Server
> Reporter: Sunitha Kambhampati
> Priority: Minor
> Labels: derby_triage10_9
>
> If server does not accept the client sent security mechanism, then as part of response for ACCSEC , the server sends the list of supported secmec back to the client.
> If the client can support the secmec sent by the server, then the client can retry the connection request with a secmec that the server said it supports.
> Some existing clients like the C client already handle this behavior. It would be nice to have the network client be able to make such choices.
> Some related jiras- DERBY-1517,DERBY-1675,DERBY-926
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira