[DERBY-1756] Revert change in client that defaults the secmec to eusridpwd.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.2.1.6, 10.3.1.4
• Component/s: Network Client
• Bug behavior facts: Regression
• Assignee: Sunitha Kambhampati
• Reporter: Sunitha Kambhampati
• Created: 24/Aug/06 00:51
• Updated: 30/Jun/09 15:55
• Resolved: 08/Sep/06 17:43

Description

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.

Issue Links

• relates to: DERBY-1517 Derby Network Client to handle list of SECMEC(s) returned by existing/released DRDA Derby Network Servers
• relates to: DERBY-962 Upgrade default security mechanism in client to use encrypted userid password if client can support it.