Displaying 5 results from an estimated 5 matches for "sasldblistusers2".
2018 Nov 26
0
Sasl authentication
...and sasl for
authentication, but not use sasl for both.
I configured tls, it was fine. Then I created a user "u" on server and
modified libvirtd.conf.
I set auth_tls = "sasl" there and mech_list: scram-sha-1 in sasl2 config
for libvirt.
The output of sasl:
u@ubuntu2:~$ sudo sasldblistusers2 -f /etc/libvirt/passwd.db
u@ubuntu: userPassword
Then I connect to server using tls and entering as the user u.
Then I have the following message:
Unable to connect to libvirt qemu+tls://u@192.168.246.135/system.
authentication failed: authentication failed
What are the correct steps to set up...
2018 Nov 28
0
Sasl + tls setup
...and sasl for
authentication, but not use sasl for both.
I configured tls, it was fine. Then I created a user "u" on server and
modified libvirtd.conf.
I set auth_tls = "sasl" there and mech_list: scram-sha-1 in sasl2 config
for libvirt.
The output of sasl:
u@ubuntu2:~$ sudo sasldblistusers2 -f /etc/libvirt/passwd.db
u@ubuntu: userPassword
Then I connect to server using tls and entering as the user u.
Then I have the following message:
Unable to connect to libvirt qemu+tls://u@192.168.246.135/system.
authentication failed: authentication failed
What are the correct steps to set up...
2018 Nov 28
0
Sasl+tls setup
...and sasl for
authentication, but not use sasl for both.
I configured tls, it was fine. Then I created a user "u" on server and
modified libvirtd.conf.
I set auth_tls = "sasl" there and mech_list: scram-sha-1 in sasl2 config
for libvirt.
The output of sasl:
u@ubuntu2:~$ sudo sasldblistusers2 -f /etc/libvirt/passwd.db
u@ubuntu: userPassword
Then I connect to server using tls and entering as the user u.
Then I have the following message:
Unable to connect to libvirt qemu+tls://u@192.168.246.135/system.
authentication failed: authentication failed
What are the correct steps to set up...
2009 Oct 14
4
Refactor ovirt-node-image code base for inclusion in Fedora
Main reason for refactor is no ovirt-node-image binary image allowed in fedora.
Removed ks files, now in ovirt-node-recipe, which is subpackage of ovirt-node.
Removed tools, these are now in ovirt-node-recipe which is subpackage of
ovirt-node.
2009 Oct 14
8
Refactor ovirt-node code base for inclusion in Fedora
Main reason for refactor is no ovirt-node-image binary image allowed in fedora.
Moves tools and kickstart files form ovirt-node-image to subpackage ovirt-node-recipe.
Removes old sub packages form ovirt-node, stateless, logos, selinux.
Modifies init scripts to meet Fedora packaging guidelines: added status, reload, and lockfile, rhbz: 514221
Added License file.