Loading...

XML

Word

Printable

Details

Type: Feature Request
Resolution: Done
Priority: Major
Fix Version/s: JDV63 1.3.0.GA
Affects Version/s: JDV63 1.2.0.GA
Component/s: None
Labels:
- dev-approved
- qe-approved

Story Points:
2
Affects:

Release Notes
Hierarchy Progress:
0
Hierarchy Progress Bar:

0% 0%
Release Note 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
Target Release:

JDV63 1.3.0.GA
Git Pull Request:
https://github.com/jboss-openshift/cct_module/pull/20, https://github.com/jboss-openshift/application-templates/pull/319

Sprint:
CLOUD Maintenance Sprint 10

SFDC Cases Links:
SFDC Cases Counter:

Description

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

Attachments

Issue Links

relates to

CLOUD-2152 [tracker] Sprint 12 release

Closed

Activity

People

Assignee:: William Decoste (Inactive)

Reporter:: Chandra Akkinepalli

Tester:: Petr Nehyba (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2017/07/07 12:04 PM

Updated:: 2017/11/08 10:43 AM

Resolved:: 2017/08/21 11:57 AM