[Freeipa-devel] kerberos auth issue

[Karl MacMillan]

On Fri, 2007-08-03 at 09:04 -0700, Kevin McCarthy wrote:
> Rob Crittenden wrote:
> > Part of the problem I'm having is that rpcclient.py does a bit of data 
> > massaging. We can move some of this to the server side, it probably belonds 
> > there anyway (such as including extra attributes when adding a user). This 
> > move will be done later.
> >
> > But with other stuff some data conversion happens and that has to be in the 
> > client.
> 
> 
> > As a test I copied rpcclient.py to webclient.py and updated my basic TG gui 
> > to use webclient.py instead. All I did was replace the server. calls with 
> > funcs. calls (effectively skipping the XML-RPC call). The one call I tested 
> > worked with no changes to the GUI code except changing the API names.
> >
> > So. I think that if we expand on this idea we can still have a more-or-less 
> > unified client API, but one goes through XML-RPC and one doesn't. The trick 
> > will be telling which is which. This is where I'm getting hung up.
> >
> > So simply copying rpcclient.py to webclient.py is obviously wrong, code 
> > duplication up the wazoo.
> 
> It sounds like you want two layers on the client
> 

I don't think so (but may be wrong) - I think it is better to have
separate objects for each 'transport' in separate libraries with a
shared data model.

That way rpcclient.py doesn't have all sorts of cruft that should never
be seen on a client (like all of the local authentication). It also
makes it easier for us to make changes to the server without having to
update clients.

Karl