Details

    • Target Release:
    • Story Points:
      2
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      Cause: ODBC transport was not properly configured in the standalone-openshift.xml
      Consequence: It was not possible to securely connect to the ODBC transport
      Fix: Both odbc and secure-odbc transports are now configured in standalone-openshift.xml when the ssl keystore is provided
      Result: It is now possible to connect to the JDV container with secured ODBC protocol
      Show
      Cause: ODBC transport was not properly configured in the standalone-openshift.xml Consequence: It was not possible to securely connect to the ODBC transport Fix: Both odbc and secure-odbc transports are now configured in standalone-openshift.xml when the ssl keystore is provided Result: It is now possible to connect to the JDV container with secured ODBC protocol
    • Sprint:
      CLOUD Maintenance Sprint 10

      Description

      Need ODBC secure socket binding setting injected into the datavirt openshift templates.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  bdecoste William Decoste
                  Reporter:
                  chanduakkin Chandra Akkinepalli
                  Tester:
                  Petr Nehyba
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: