[jboss-jira] [JBoss JIRA] (WFLY-483) Allow more control over authentication for server to server communication through remote-outbound-connection

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene updated WFLY-483:
------------------------------
    Fix Version/s: 10.0.0.CR2
                       (was: 10.0.0.CR1)


> Allow more control over authentication for server to server communication through remote-outbound-connection
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-483
>                 URL: https://issues.jboss.org/browse/WFLY-483
>             Project: WildFly
>          Issue Type: Sub-task
>          Components: Remoting, Security
>            Reporter: jaikiran pai
>            Assignee: Darran Lofthouse
>              Labels: authentication_service
>             Fix For: 10.0.0.CR2
>
>
> Right now for server to server communication via a remote-outbound-connection, we expect a static username to be specified (along with the security realm). User applications which use this remote-outbound-connection, for example an EJB application, do not have much control over the user/pass information, since the username is static. This further acts a drawback since the username that's used to connect to the remote server will be used as the (application) user who invoked the EJB.
> It would be good to allow more control over the authentication for the remote-outbound-connection.



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