[
https://issues.jboss.org/browse/TEIID-2616?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2616.
-----------------------------------
Resolution: Done
Added better detection logic for a mismatched protocol - ideally we would simply attempt
ssl after the non-ssl failure, but that it not a simple change with the current logic
(could be refactored so that the objectchannel can have an sslengine engaged after
creation).
Also added an org.teiid.ssl.trustAll property as an undocumented property to allow clients
to make ssl connections without requiring explicit trust of server certificates - this
would typically not be used.
The error should be clearer when making a non-ssl connecting to an
ssl server
-----------------------------------------------------------------------------
Key: TEIID-2616
URL:
https://issues.jboss.org/browse/TEIID-2616
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Driver
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4.1, 8.5
When making a non-ssl connection to an ssl server the message is not indicative of what
the issue may be.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira