Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <9888242.1156402204233.JavaMail.jira@brutus>
Date: Wed, 23 Aug 2006 23:50:04 -0700 (PDT)
From: "Sunitha Kambhampati (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-1756) Revert change in client that defaults
 the secmec to eusridpwd.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Revert change in client that defaults the secmec to eusridpwd.
--------------------------------------------------------------

                 Key: DERBY-1756
                 URL: http://issues.apache.org/jira/browse/DERBY-1756
             Project: Derby
          Issue Type: Bug
          Components: Network Client
    Affects Versions: 10.2.1.0
            Reporter: Sunitha Kambhampati
         Assigned To: Sunitha Kambhampati
             Fix For: 10.2.1.0


With changes to derby-962, the client would default to eusridpwd if the client jvm supports it.  It is not sufficient to only check if client jvm can support eusridpwd  but we need to verify if the server can support the particular secmec.  

There are other existing jiras DERBY-1675,DERBY-1517,DERBY-1755 that will help to address the issue of  upgrading to a better security mechanism.

This jira will change the default security mechanism to 3 as it was before derby-962 changes.


-- 
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