10:32 a.m.
I'm trying to find a way to regression-test a program which uses
libvirt authentication (virConnectAuth, virConnectAuthPtr). Ideally
the test:/// driver would be able to fake authentication demands, but
it doesn't seem to be able to do that.
Any suggestions? Would this feature belong in the test driver or
elsewhere?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
8:12 a.m.
On Wed, Jan 08, 2014 at 04:32:12PM +0000, Richard W.M. Jones wrote:
I'm trying to find a way to regression-test a program which uses
libvirt authentication (virConnectAuth, virConnectAuthPtr). Ideally
the test:/// driver would be able to fake authentication demands, but
it doesn't seem to be able to do that.
Any suggestions? Would this feature belong in the test driver or
elsewhere?
I'd guess we could easily add auth to the test driver. Either the XML
doc for the test driver could allow you to fully specify auth parameters
it should try to collect or perhaps URI parameters could be abused.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
8:15 a.m.
On 01/10/2014 07:12 AM, Daniel P. Berrange wrote:
On Wed, Jan 08, 2014 at 04:32:12PM +0000, Richard W.M. Jones wrote:
>
> I'm trying to find a way to regression-test a program which uses
> libvirt authentication (virConnectAuth, virConnectAuthPtr). Ideally
> the test:/// driver would be able to fake authentication demands, but
> it doesn't seem to be able to do that.
>
> Any suggestions? Would this feature belong in the test driver or
> elsewhere?
I'd guess we could easily add auth to the test driver. Either the XML
doc for the test driver could allow you to fully specify auth parameters
it should try to collect or perhaps URI parameters could be abused.
In fact, Rich did the former (XML describes the parameters to collect):
commit e093351209a4937631ec70d6007b096c6754dcce
Author: Richard W.M. Jones <rjones(a)redhat.com>
Date: Wed Jan 8 18:32:48 2014 +0000
test driver: Add authentication to test driver.
There is no easy way to test authentication against libvirt. This
commit modifies the test driver to allow simple username/password
authentication.
You modify the test XML by adding:
<node>
...
<auth>
<user password="123456">rich</user>
<user>jane</user>
</auth>
</node>
If there are any /node/auth/user elements, then authentication is
required by the test driver (if none are present, then the test driver
will work as before and not require authentication).
In the example above, two phony users are added:
rich password: 123456
jane no password required
The test driver will demand a username. If the password attribute is
present (or if the username entered is wrong), then the password is
also asked for and checked:
$ virsh -c test://$(pwd)/testnode.xml list
Enter username for localhost: rich
Enter rich's password for localhost: ***
Id Name State
----------------------------------------------------
1 fv0 running
2 fc4 running
Signed-off-by: Richard W.M. Jones <rjones(a)redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
3969
days inactive
3971
days old
2 comments
3 participants
participants (3)
-
Daniel P. Berrange -
Eric Blake -
Richard W.M. Jones