api-viewer: adapt to changes

[pve-docs.git] / pveum.adoc

diff --git a/pveum.adoc b/pveum.adoc
index 0cebe821df877608852dd3330fa5081d2aa9176c..71ea7ef93564603748031640ff8c137e3e18ce58 100644 (file)
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -327,8 +327,9 @@ field before pressing the 'Apply' button.
 Server side U2F configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To allow users to use 'U2F' authentication, the server needs to have a valid
-domain with a valid https certificate. Initially an 'AppId'
+To allow users to use 'U2F' authentication, it may be necessary to use a valid
+domain with a valid https certificate, otherwise some browsers may print
+a warning or reject U2F usage altogether. Initially an 'AppId'
 footnote:[AppId https://developers.yubico.com/U2F/App_ID.html]
 needs to be configured.
 
@@ -448,6 +449,7 @@ Node / System related privileges::
 * `Sys.Modify`: create/remove/modify node network parameters
 * `Group.Allocate`: create/remove/modify groups
 * `Pool.Allocate`: create/remove/modify a pool
+* `Pool.Audit`: view a pool
 * `Realm.Allocate`: create/remove/modify authentication realms
 * `Realm.AllocateUser`: assign user to a realm
 * `User.Modify`: create/remove/modify user access and details.
@@ -536,7 +538,7 @@ What permission do I need?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The required API permissions are documented for each individual
-method, and can be found at http://pve.proxmox.com/pve-docs/api-viewer/
+method, and can be found at https://pve.proxmox.com/pve-docs/api-viewer/
 
 The permissions are specified as a list which can be interpreted as a
 tree of logic and access-check functions: