Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1756

Revert change in client that defaults the secmec to eusridpwd.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.2.1.6, 10.3.1.4
    • 10.2.1.6, 10.3.1.4
    • Network Client
    • None
    • Regression

    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.

      Attachments

        1. Derby1756.2.diff.txt
          12 kB
          Sunitha Kambhampati
        2. derby1756.diff.txt
          13 kB
          Sunitha Kambhampati
        3. derby1756.stat.txt
          0.3 kB
          Sunitha Kambhampati

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-1517 Derby Network Client to handle list of SECMEC(s) returned by existing/released DRDA Derby Network Servers

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-962 Upgrade default security mechanism in client to use encrypted userid password if client can support it.

          • Major - Major loss of function.
          • Closed

          Activity

            People

              skambha Sunitha Kambhampati
              skambha Sunitha Kambhampati
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: