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

Revert change in client that defaults the secmec to eusridpwd.

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None
    • Bug behavior facts:
      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.diff.txt
          13 kB
          Sunitha Kambhampati
        2. derby1756.stat.txt
          0.3 kB
          Sunitha Kambhampati
        3. Derby1756.2.diff.txt
          12 kB
          Sunitha Kambhampati

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: