[jboss-jira] [JBoss JIRA] (WFCORE-1145) Review of HostController / Application Server Remoting connections

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-1145:
------------------------------------------

I incorrectly asked this on WFCORE-1147.

"If there is a return channel, why would we get stdin involved?"

My question was specifically in reference to how this helps with WFCORE-1135, since the return channel connected to an ephemeral socket is AFAIK the same basic thing as we already have. I can certainly see using on the HC a different socket from the externally accessible one and only allowing it to be bound to localhost would be helpful. 

> Review of HostController / Application Server Remoting connections
> ------------------------------------------------------------------
>
>                 Key: WFCORE-1145
>                 URL: https://issues.jboss.org/browse/WFCORE-1145
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>              Labels: affects_elytron
>             Fix For: 3.0.0.Alpha1
>
>
> Where an application server connects back to it's host controller in domain mode it used the same Remoting connector exposed possibly for native domain management access.
> The problem with this is that as soon as any security restrictions are placed on the connector exposed by the host controller then the application servers require something to work with this - this is even though we are only ever talking about loopback communication between two process on the same machine.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)