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

Ramesh Reddy (JIRA) jira-events at lists.jboss.org
Tue Dec 4 12:30:22 EST 2012


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

Ramesh Reddy commented on TEIID-2319:
-------------------------------------

Van, there are three options (login, enabled, disabled). Whether standalone.xml saves it or not is not a question, it is how AS7 persists configuration, that does not mean that option is not available. As Ted said, no user is editing the standalone.xml directly, they should use one of the client tools. If they are using one of the client tools and going from "disabled" to "login", they need to specify that to change it. Removing from document, saying to user there is only two options is not correct. Even we specify three options on client tools, if the user wants learn what is that "login" option, they would certainly refer back to document.

Configuration != Documentation

IMO, this was not a productive conversation, we should leave document as is.
                
> 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