[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-1246) Can't authenticate using TransporterClient

[Ron Sigal (JIRA)]

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

Ron Sigal updated JBREM-1246:
-----------------------------

        Fix Version/s:     (was: 2.2.3.SP4)
    Affects Version/s:     (was: 2.2.3.SP3)


> Can't authenticate using TransporterClient
> ------------------------------------------
>
>                 Key: JBREM-1246
>                 URL: https://issues.jboss.org/browse/JBREM-1246
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.5.3.SP1
>            Reporter: Sebastian Dietrich
>            Assignee: Ron Sigal
>              Labels: TransporterClient
>             Fix For: 2.5.3.SP2
>
>
> I'd like to introduce basic authentication in my project which uses TransporterClient to connect to the server. According to the documentation (http://docs.jboss.org/jbossremoting/2.5.3.SP1/html_single/#d0e2251 5.4.11. HTTP(S) Client Invoker - proxy and basic authentication) this is not supported with TransporterClient, but only via response = client.invoke(payload, metadata);
> TransporterClient uses response = remotingClient.invoke(request); (see TransporterClient.class Line 321)
> Unfortunately I can neither subclass TransporterClient (since its constructors are private) nor decorate it (since its invoke method I'd like to change uses private attributes & methods).
> ==> Please provide a way to use basic authentication in TransporterClient
> This could be done easily via a further constructor/factory method which accepts metadata.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira