[
https://issues.jboss.org/browse/TEIIDSB-92?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIIDSB-92:
---------------------------------------
The f-m-p issue is already known. The suggestion is either to use the spring-boot name,
or remove the explicit name from the fragment (it will still be spring-boot in that
case).
I've swtiched this over to pg, but am running into issues. With the simple jdbc
client, it's using the connection.isvalid method that issues an empty prepared
statement that we are not handling. There also appears to be another issue. I'll get
both of those addressed.
Provide an openshfit example of a secure transport
--------------------------------------------------
Key: TEIIDSB-92
URL:
https://issues.jboss.org/browse/TEIIDSB-92
Project: Teiid Spring Boot
Issue Type: Sub-task
Components: OpenShift
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Attachments: screenshot-1.png
Until we have kerberos support, usage of the pg transport will likely need to be secure
to prevent plain-text username/password being sent unencrypted.
It should also be a general option to enable secure transports from our ui. External
exposure is covered in TEIIDSB-86.
We should use the private key from either based upon a self-signed certificate or using
service signing certificates. I'll provide an example demonstrating one of those
approaches.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)