[Engine-devel] Adding Authentication mechanism to oVirt

Alon Bar-Lev alonbl at redhat.com
Wed Dec 12 23:32:18 UTC 2012



----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "Thierry Kauffmann" <thierry.kauffmann at univ-montp2.fr>, "Yaniv Kaul" <ykaul at redhat.com>, "engine-devel"
> <engine-devel at ovirt.org>
> Sent: Thursday, December 13, 2012 1:27:15 AM
> Subject: Re: Adding Authentication mechanism to oVirt
> 
> On 12/12/2012 06:53 PM, Alon Bar-Lev wrote:
> > I believe the GSSAPI can be dropped, I see no advantage of using
> > it.
> 
> how would upgrade/backward compatibility look like?
> 
> 

We have the user/password, so there should be no problem we can test if authentication succeeds in methods based on some order... but we cross this when we reach the point.
Asking the user for transport/authentication scheme during upgrade is something that can also be done.

We can keep the GSSAPI around of course... Not something I would like to do.

Alon



More information about the Devel mailing list