[jboss-jira] [JBoss JIRA] (REMJMX-41) Connection re-authentication options

[Darran Lofthouse (JIRA)]

Darran Lofthouse created REMJMX-41:
--------------------------------------

             Summary: Connection re-authentication options
                 Key: REMJMX-41
                 URL: https://issues.jboss.org/browse/REMJMX-41
             Project: Remoting JMX
          Issue Type: Task
          Components: Connection, Security
            Reporter: Darran Lofthouse
            Assignee: Darran Lofthouse


At the moment this task is just to make a note of this for the future so we can review options some time for AS 7.2.x

There are a couple of places where it is highlighted that a 1:1 relationship between the connection and the authenticated user is not as flexible as some would desire.

A couple of examples are: -
 1 - Clients wishing a single process to run with multiple threads, each representing a different user.
 2 - Server to server comms where an additional authentication step may be needed.

At the moment clients can open multiple connection but a massive benefit of Remoting is the option to re-use the same connection for multiple services.

There are additional options such as adding a protocol specific authentication step within services to adding support for authentication on opening a channel to even some form of sub-connection support within a connection.  Regardless I think we should start reviewing this from Remoting first as that is where there is the potential to solve it once for all services without duplicating a solution across multiple services.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira