[teiid-issues] [JBoss JIRA] (TEIID-2319) Default socket encryption for JDBC transport using mode=login is not being set in configuration file
Van Halbert (JIRA)
jira-events at lists.jboss.org
Tue Dec 4 10:55:21 EST 2012
[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739314#comment-12739314 ]
Van Halbert commented on TEIID-2319:
------------------------------------
You are right there are 3 options, but from a usability and documentation (which is realize is semantics on this) is to only indicate the 2 options to change (why add login when it disappears from the config file) and explain the default behavior in documentation when the either of enabled/disabled are not specified.
> Default socket encryption for JDBC transport using mode=login is not being set in configuration file
> ----------------------------------------------------------------------------------------------------
>
> Key: TEIID-2319
> URL: https://issues.jboss.org/browse/TEIID-2319
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Critical
>
> Referencing TEIID-2108, the login traffic should be encrypted by default. The standalone-teiid-xml does not specify <ssl mode="login" />, nor does the teiid-domain-mode-install.cli show to be adding this setting.
--
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
More information about the teiid-issues
mailing list