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.Alpha3 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.