[teiid-issues] [JBoss JIRA] (TEIID-2319) Default socket encryption for JDBC transport using mode=login is not being set in configuration file

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Tue Dec 4 13:21:21 EST 2012


    [ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739398#comment-12739398 ] 

Steven Hawkins commented on TEIID-2319:
---------------------------------------

Van that's not the issue.  The salient stuff here is that:

1. The default for the transport is LOGIN, so config/script changes are not needed.
2. As Ramesh states clearly, Configuration != Documentation - so we do not want to embellish the provided teiid standalone xml/cli unnecessarily
3. As Ted states, users should typically not modify the xml configuration directly.  The documentation should avoid recommending that approach.
4. Default values are still valid to document as the user may need to switch back to that value if they've changed to a non-default.

So from here the question is just what documentation changes, if any, are needed clarify socket encryption.  All other doc related issues should probably spawn a different issue/forum topic.
                
> 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