From 075028e74f4d11c8b0d3bb3e857e4811b148a4e1 Mon Sep 17 00:00:00 2001 Message-Id: <075028e74f4d11c8b0d3bb3e857e4811b148a4e1@dist-git> From: John Ferlan Date: Mon, 5 Nov 2018 07:48:38 -0500 Subject: [PATCH] docs: Enhance polkit documentation to describe secondary connection https://bugzilla.redhat.com/show_bug.cgi?id=1631608 (RHEL 8.0) https://bugzilla.redhat.com/show_bug.cgi?id=1631606 (RHEL 7.7) Since commit 8259255 usage of a primary connection driver for a virConnect has been modified to open (virConnectOpen) and use a connection to the specific driver in order to handle the API calls to/for that driver. This causes some confusion and issues for ACL polkit rule scripts to know exactly which driver by name will be used. Add some documentation describing the processing of the primary and secondary connection as well as the list of the connect_driver names used for each driver. Signed-off-by: John Ferlan ACKed-by: Michal Privoznik (cherry picked from commit 4f1107614dc1384c4aa7a5582a16aecba8b9310f) Reviewed-by: Jiri Denemark --- docs/aclpolkit.html.in | 117 +++++++++++++++++++++++++++++++++++++++++ docs/libvirt.css | 1 + 2 files changed, 118 insertions(+) diff --git a/docs/aclpolkit.html.in b/docs/aclpolkit.html.in index ee00b98461..ac54f125da 100644 --- a/docs/aclpolkit.html.in +++ b/docs/aclpolkit.html.in @@ -287,6 +287,123 @@ +

Hypervisor Driver connect_driver

+

+ The connect_driver parameter describes the + client's remote Connection Driver + name based on the URI used for the + connection. +

+

+ Since 4.1.0, when calling an API + outside the scope of the primary connection driver, the + primary driver will attempt to open a secondary connection + to the specific API driver in order to process the API. For + example, when hypervisor domain processing needs to make an + API call within the storage driver or the network filter driver + an attempt to open a connection to the "storage" or "nwfilter" + driver will be made. Similarly, a "storage" primary connection + may need to create a connection to the "secret" driver in order + to process secrets for the API. If successful, then calls to + those API's will occur in the connect_driver context + of the secondary connection driver rather than in the context of + the primary driver. This affects the connect_driver + returned from rule generation from the action.loookup + function. The following table provides a list of the various + connection drivers and the connect_driver name + used by each regardless of primary or secondary connection. + The access denied error message from libvirt will list the + connection driver by name that denied the access. +

+ +

Connection Driver Name

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Connection Driverconnect_driver name
bhyvebhyve
esxESX
hypervHyper-V
interfaceinterface
libxlxenlight
lxcLXC
networknetwork
nodedevnodedev
nwfilterNWFilter
openvzOPENVZ
phypPHYP
qemuQEMU
secretsecret
storagestorage
umlUML
vboxVBOX
vmwareVMWARE
vzvz
xenapiXenAPI
+

User identity attributes

diff --git a/docs/libvirt.css b/docs/libvirt.css index b2ed33926a..e590b33cfb 100644 --- a/docs/libvirt.css +++ b/docs/libvirt.css @@ -393,6 +393,7 @@ table.acl { table.acl tr, table.acl td { padding: 0.3em; + border: 1px solid #ccc; } table.acl thead { -- 2.19.1