Re: Authentication: Whose responsibility?

[Ryan Hoegg]

Andrew Evers wrote:

But I think we should revisit authentication now that we have abstracted
the transport from the XML-RPC client. As I go through implementing
(cleanly) my new XmlRpcTransport, I took a look at the authentication
piece of DefaultXmlRpcTransport and LiteXmlRpcTransport.

It isn't there!

Well, I'm not sure whether there should be a setBasicAuthentication() method
on XmlRpcTransport, maybe a setAuthenticationInfo(Properties authInfo), and
some standard properties (like USERNAME, PASSWORD).

As far as {Default, Lite}XmlRpcTransport are concerned, there is no reason
why they can't have a setBasicAuthentication method. This can be called
after
creating the transport and before passing it to anything else.

Andrew.

We could leave the XmlRpcTransport interface as it is, and just put setBasicAuthentication on any Transports that want to support it. Currently I need some way to pass authentication credentials from XmlRpcClient to its transport because I deprecated XmlRpcClient.setBasicAuthentication but did not remove it. Removing it would remove the need for the interface to support authentication.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net