[Engine-devel] Improvement for the oVirt java sdk

Morrissey, Christopher Christopher.Morrissey at netapp.com
Mon Mar 4 15:26:45 UTC 2013


Hi Michael,

Yes, that is the case here. I'm getting the JSESSIONID from the client and passing it to our server so that it can perform REST-API calls back to oVirt under the logged in user's authenticated session.

-Chris

> -----Original Message-----
> From: Michael Pasternak [mailto:mpastern at redhat.com]
> Sent: Sunday, March 03, 2013 4:44 AM
> To: Morrissey, Christopher
> Cc: users at ovirt.org; engine-devel
> Subject: Re: Improvement for the oVirt java sdk
> 
> 
> Hi Christopher,
> 
> In general SDK abstracts the transport layer, therefore all authentication
> internals hidden from the user,
> 
> i.e SESSION based authentication happens implicitly (by default), when you
> initiate SDK entry point,
> 
> the story is different if you want using SSO-like login by reusing JSESSIONID
> from the REST-API for instance, and i can support such scenario,
> 
> but, is this your case?
> 
> On 02/28/2013 10:04 PM, Morrissey, Christopher wrote:
> > Hi Michael,
> >
> > I'm looking to use the oVirt java sdk for connecting into oVirt from
> > our server. However, we have a UI plugin that gets access to a session
> > ID that we should be able to use to connect through the REST API
> > instead of the username and password. Any chance the sdk could be
> updated to take the session ID and create a connection vs. a user name and
> password?
> >
> > -Chris
> >
> > Chris Morrissey
> > Software Engineer
> > NetApp Inc.
> > 919.476.4428
> >
> >
> 
> 
> --
> 
> Michael Pasternak
> RedHat, ENG-Virtualization R&D



More information about the Engine-devel mailing list