[teiid-issues] [JBoss JIRA] (TEIIDSB-86) Plans for secure socket transports

[Steven Hawkins (Jira)]

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

Steven Hawkins commented on TEIIDSB-86:
---------------------------------------

I took some time to investigate moving Teiid JDBC to websockets (which could directly use a route) as there is a netty stack that's available for that.  The short answer is that it's not an easy drop in - at least a couple of days of effort.  We need to add websocket client support to the driver via Netty or https://github.com/TooTallNate/Java-WebSocket and the related server handling into the pipeline.  We need additional encode/decode support to take incoming bytebuffer messages and convert to binary websocket messages (there may be other steps, but that is as far as I got).  On the client side we have to bridge between the websocket onMessage/send and inputstream/outputstream logic or completely re-implement the OioObjectChannel as a websocket version.  Also having our protocol send the handshake from the server side initially is a little awkward.

> Plans for secure socket transports
> ----------------------------------
>
>                 Key: TEIIDSB-86
>                 URL: https://issues.jboss.org/browse/TEIIDSB-86
>             Project: Teiid Spring Boot
>          Issue Type: Quality Risk
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Major
>             Fix For: 1.1.0
>
>
> The Teiid Spring Boot configuration allows for only non-secured pg / JDBC socket transports.  For external client scenarios and even for varying degrees of compliance with intra-cluster traffic, a secure layer may be required.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)