]>
Commit | Line | Data |
---|---|---|
80c0adcb | 1 | [[chapter_user_management]] |
3c8533f2 | 2 | ifdef::manvolnum[] |
b2f242ab DM |
3 | pveum(1) |
4 | ======== | |
5f09af76 DM |
5 | :pve-toplevel: |
6 | ||
3c8533f2 DM |
7 | NAME |
8 | ---- | |
9 | ||
10 | pveum - Proxmox VE User Manager | |
11 | ||
12 | ||
49a5e11c | 13 | SYNOPSIS |
3c8533f2 DM |
14 | -------- |
15 | ||
16 | include::pveum.1-synopsis.adoc[] | |
17 | ||
18 | ||
19 | DESCRIPTION | |
20 | ----------- | |
21 | endif::manvolnum[] | |
3c8533f2 DM |
22 | ifndef::manvolnum[] |
23 | User Management | |
24 | =============== | |
5f09af76 | 25 | :pve-toplevel: |
194d2f29 | 26 | endif::manvolnum[] |
5f09af76 | 27 | |
3c8533f2 DM |
28 | // Copied from pve wiki: Revision as of 16:10, 27 October 2015 |
29 | ||
96942248 | 30 | {pve} supports multiple authentication sources, for example Linux PAM, |
5462c161 | 31 | an integrated Proxmox VE authentication server, LDAP, Microsoft Active |
96942248 | 32 | Directory and OpenID Connect. |
3c8533f2 | 33 | |
96942248 DW |
34 | By using role-based user and permission management for all objects (VMs, |
35 | Storage, nodes, etc.), granular access can be defined. | |
5eba0743 | 36 | |
3c8533f2 | 37 | |
80c0adcb | 38 | [[pveum_users]] |
c80b9ee6 WB |
39 | Users |
40 | ----- | |
41 | ||
42 | {pve} stores user attributes in `/etc/pve/user.cfg`. | |
96942248 | 43 | Passwords are not stored here; users are instead associated with the |
80c0adcb | 44 | <<pveum_authentication_realms,authentication realms>> described below. |
96942248 | 45 | Therefore, a user is often internally identified by their username and |
c80b9ee6 WB |
46 | realm in the form `<userid>@<realm>`. |
47 | ||
48 | Each user entry in this file contains the following information: | |
49 | ||
50 | * First name | |
51 | * Last name | |
52 | * E-mail address | |
53 | * Group memberships | |
96942248 | 54 | * An optional expiration date |
c80b9ee6 WB |
55 | * A comment or note about this user |
56 | * Whether this user is enabled or disabled | |
74662f51 | 57 | * Optional two-factor authentication keys |
c80b9ee6 | 58 | |
96942248 | 59 | CAUTION: When you disable or delete a user, or if the expiry date set is |
f06ba6a6 | 60 | in the past, this user will not be able to log in to new sessions or start new |
96942248 | 61 | tasks. All tasks which have already been started by this user (for example, |
f06ba6a6 | 62 | terminal sessions) will **not** be terminated automatically by any such event. |
8d02d0a2 | 63 | |
c80b9ee6 WB |
64 | |
65 | System administrator | |
66 | ~~~~~~~~~~~~~~~~~~~~ | |
67 | ||
68 | The system's root user can always log in via the Linux PAM realm and is an | |
69 | unconfined administrator. This user cannot be deleted, but attributes can | |
96942248 | 70 | still be changed. System mails will be sent to the email address |
c80b9ee6 WB |
71 | assigned to this user. |
72 | ||
73 | ||
80c0adcb | 74 | [[pveum_groups]] |
c80b9ee6 | 75 | Groups |
a10a91c2 | 76 | ------ |
c80b9ee6 | 77 | |
96942248 DW |
78 | Each user can be a member of several groups. Groups are the preferred |
79 | way to organize access permissions. You should always grant permissions | |
80 | to groups instead of individual users. That way you will get a | |
81 | much more maintainable access control list. | |
c80b9ee6 | 82 | |
181db098 FG |
83 | [[pveum_tokens]] |
84 | API Tokens | |
a10a91c2 | 85 | ---------- |
181db098 | 86 | |
96942248 | 87 | API tokens allow stateless access to most parts of the REST API from another |
710713ea TL |
88 | system, software or API client. Tokens can be generated for individual users |
89 | and can be given separate permissions and expiration dates to limit the scope | |
96942248 | 90 | and duration of the access. Should the API token get compromised, it can be |
710713ea | 91 | revoked without disabling the user itself. |
181db098 FG |
92 | |
93 | API tokens come in two basic types: | |
94 | ||
96942248 DW |
95 | * Separated privileges: The token needs to be given explicit access with ACLs. |
96 | Its effective permissions are calculated by intersecting user and token | |
181db098 | 97 | permissions. |
96942248 | 98 | * Full privileges: The token's permissions are identical to that of the |
181db098 FG |
99 | associated user. |
100 | ||
c6e098a2 TL |
101 | CAUTION: The token value is only displayed/returned once when the token is |
102 | generated. It cannot be retrieved again over the API at a later time! | |
181db098 FG |
103 | |
104 | To use an API token, set the HTTP header 'Authorization' to the displayed value | |
105 | of the form `PVEAPIToken=USER@REALM!TOKENID=UUID` when making API requests, or | |
96942248 | 106 | refer to your API client's documentation. |
c80b9ee6 | 107 | |
23b447be DW |
108 | [[pveum_resource_pools]] |
109 | Resource Pools | |
110 | -------------- | |
111 | ||
112 | [thumbnail="screenshot/gui-datacenter-pool-window.png"] | |
113 | ||
114 | A resource pool is a set of virtual machines, containers, and storage | |
115 | devices. It is useful for permission handling in cases where certain users | |
116 | should have controlled access to a specific set of resources, as it allows for a | |
117 | single permission to be applied to a set of elements, rather than having to | |
96942248 DW |
118 | manage this on a per-resource basis. Resource pools are often used in tandem |
119 | with groups, so that the members of a group have permissions on a set of | |
120 | machines and storage. | |
23b447be | 121 | |
80c0adcb | 122 | [[pveum_authentication_realms]] |
3c8533f2 DM |
123 | Authentication Realms |
124 | --------------------- | |
125 | ||
d6614202 WB |
126 | As {pve} users are just counterparts for users existing on some external |
127 | realm, the realms have to be configured in `/etc/pve/domains.cfg`. | |
128 | The following realms (authentication methods) are available: | |
3c8533f2 | 129 | |
78000a64 DW |
130 | Linux PAM Standard Authentication:: |
131 | ||
132 | Linux PAM is a framework for system-wide user authentication. These users are | |
133 | created on the host system with commands such as `adduser`. If PAM users exist | |
134 | on the {pve} host system, corresponding entries can be added to {pve}, to allow | |
135 | these users to log in via their system username and password. | |
3c8533f2 | 136 | |
78000a64 DW |
137 | {pve} Authentication Server:: |
138 | ||
139 | This is a Unix-like password store, which stores hashed passwords in | |
140 | `/etc/pve/priv/shadow.cfg`. Passwords are hashed using the SHA-256 hashing | |
141 | algorithm. This is the most convenient realm for small-scale (or even | |
142 | mid-scale) installations, where users do not need access to anything outside of | |
143 | {pve}. In this case, users are fully managed by {pve} and are able to change | |
144 | their own passwords via the GUI. | |
d6614202 WB |
145 | |
146 | LDAP:: | |
78000a64 DW |
147 | |
148 | LDAP (Lightweight Directory Access Protocol) is an open, cross-platform protocol | |
149 | for authentication using directory services. OpenLDAP is a popular open-source | |
150 | implementations of the LDAP protocol. | |
151 | ||
152 | Microsoft Active Directory (AD):: | |
153 | ||
154 | Microsoft Active Directory (AD) is a directory service for Windows domain | |
155 | networks and is supported as an authentication realm for {pve}. It supports LDAP | |
156 | as an authentication protocol. | |
157 | ||
158 | OpenID Connect:: | |
159 | ||
160 | OpenID Connect is implemented as an identity layer on top of the OATH 2.0 | |
161 | protocol. It allows clients to verify the identity of the user, based on | |
162 | authentication performed by an external authorization server. | |
163 | ||
164 | Linux PAM Standard Authentication | |
165 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
166 | ||
167 | As Linux PAM corresponds to host system users, a system user must exist on each | |
168 | node which the user is allowed to log in on. The user authenticates with their | |
169 | usual system password. This realm is added by default and can't be removed. In | |
170 | terms of configurability, an administrator can choose to require two-factor | |
171 | authentication with logins from the realm and to set the realm as the default | |
172 | authentication realm. | |
173 | ||
174 | ||
175 | {pve} Authentication Server | |
176 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
177 | ||
178 | The {pve} authentication server realm is a simple Unix-like password store. | |
179 | The realm is created by default, and as with Linux PAM, the only configuration | |
180 | items available are the ability to require two-factor authentication for users | |
181 | of the realm, and to set it as the default realm for login. | |
182 | ||
183 | Unlike the other {pve} realm types, users are created and authenticated entirely | |
184 | through {pve}, rather than authenticating against another system. Hence, you are | |
185 | required to set a password for this type of user upon creation. | |
186 | ||
187 | ||
188 | LDAP | |
189 | ~~~~ | |
190 | ||
191 | You can also use an external LDAP server for user authentication (for examle, | |
192 | OpenLDAP). In this realm type, users are searched under a 'Base Domain Name' | |
193 | (`base_dn`), using the username attribute specified in the 'User Attribute Name' | |
d6614202 | 194 | (`user_attr`) field. |
78000a64 DW |
195 | |
196 | A server and optional fallback server can be configured, and the connection can | |
197 | be encrypted via SSL. Furthermore, filters can be configured for directories and | |
198 | groups. Filters allow you to further limit the scope of the realm. | |
199 | ||
200 | For instance, if a user is represented via the following LDIF dataset: | |
201 | ||
d6614202 WB |
202 | ---- |
203 | # user1 of People at ldap-test.com | |
204 | dn: uid=user1,ou=People,dc=ldap-test,dc=com | |
205 | objectClass: top | |
206 | objectClass: person | |
207 | objectClass: organizationalPerson | |
208 | objectClass: inetOrgPerson | |
209 | uid: user1 | |
210 | cn: Test User 1 | |
211 | sn: Testers | |
212 | description: This is the first test user. | |
213 | ---- | |
78000a64 | 214 | |
d6614202 WB |
215 | The 'Base Domain Name' would be `ou=People,dc=ldap-test,dc=com` and the user |
216 | attribute would be `uid`. | |
78000a64 | 217 | |
3a433e9b | 218 | If {pve} needs to authenticate (bind) to the LDAP server before being |
d6614202 WB |
219 | able to query and authenticate users, a bind domain name can be |
220 | configured via the `bind_dn` property in `/etc/pve/domains.cfg`. Its | |
221 | password then has to be stored in `/etc/pve/priv/ldap/<realmname>.pw` | |
96942248 DW |
222 | (for example, `/etc/pve/priv/ldap/my-ldap.pw`). This file should contain a |
223 | single line with the raw password. | |
78000a64 | 224 | |
96942248 | 225 | To verify certificates, you need to set `capath`. You can set it either |
4ab527b1 TL |
226 | directly to the CA certificate of your LDAP server, or to the system path |
227 | containing all trusted CA certificates (`/etc/ssl/certs`). | |
3a433e9b | 228 | Additionally, you need to set the `verify` option, which can also be done over |
4ab527b1 | 229 | the web interface. |
d6614202 | 230 | |
78000a64 DW |
231 | The main configuration options for an LDAP server realm are as follows: |
232 | ||
233 | * `Realm` (`realm`): The realm identifier for {pve} users | |
234 | ||
235 | * `Base Domain Name` (`base_dn`): The directory which users are searched under | |
236 | ||
237 | * `User Attribute Name` (`user_attr`): The LDAP attribute containing the | |
238 | username that users will log in with | |
239 | ||
240 | * `Server` (`server1`): The server hosting the LDAP directory | |
241 | ||
242 | * `Fallback Server` (`server2`): An optional fallback server address, in case | |
243 | the primary server is unreachable | |
244 | ||
245 | * `Port` (`port`): The port that the LDAP server listens on | |
246 | ||
96942248 | 247 | NOTE: In order to allow a particular user to authenticate using the LDAP server, |
78000a64 DW |
248 | you must also add them as a user of that realm from the {pve} server. This can |
249 | be carried out automatically with <<pveum_ldap_sync, syncing>>. | |
3c8533f2 | 250 | |
3c8533f2 | 251 | |
78000a64 DW |
252 | Microsoft Active Directory (AD) |
253 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
f3ee27eb | 254 | |
78000a64 DW |
255 | To set up Microsoft AD as a realm, a server address and authentication domain |
256 | need to be specified. Active Directory supports most of the same properties as | |
257 | LDAP, such as an optional fallback server, port, and SSL encryption. | |
258 | Furthermore, users can be added to {pve} automatically via | |
259 | <<pveum_ldap_sync, sync>> operations, after configuration. | |
260 | ||
261 | As with LDAP, if {pve} needs to authenticate before it binds to the AD server, | |
262 | you must configure the 'Bind User' (`bind_dn`) property. This property is | |
263 | typically required by default for Microsoft AD. | |
264 | ||
265 | The main configuration settings for Microsoft Active Directory are: | |
266 | ||
267 | * `Realm` (`realm`): The realm identifier for {pve} users | |
268 | ||
269 | * `Domain` (`domain`): The AD domain of the server | |
270 | ||
271 | * `Server` (`server1`): The FQDN or IP address of the server | |
272 | ||
273 | * `Fallback Server` (`server2`): An optional fallback server address, in case | |
274 | the primary server is unreachable | |
275 | ||
276 | * `Port` (`port`): The port that the Microsoft AD server listens on | |
277 | ||
278 | [[pveum_ldap_sync]] | |
279 | Syncing LDAP-Based Realms | |
280 | ~~~~~~~~~~~~~~~~~~~~~~~~~ | |
281 | ||
282 | [thumbnail="screenshot/gui-datacenter-realm-add-ldap.png"] | |
283 | ||
284 | It's possible to automatically sync users and groups for LDAP-based realms (LDAP | |
285 | & Microsoft Active Directory), rather than having to add them to {pve} manually. | |
286 | You can access the sync options from the Add/Edit window of the web interface's | |
287 | `Authentication` panel or via the `pveum realm add/modify` commands. You can | |
288 | then carry out the sync operation from the `Authentication` panel of the GUI or | |
289 | using the following command: | |
290 | ||
291 | ---- | |
292 | pveum realm sync <realm> | |
293 | ---- | |
294 | ||
295 | Users and groups are synced to the cluster-wide configuration file, | |
296 | `/etc/pve/user.cfg`. | |
297 | ||
298 | ||
299 | Sync Configuration | |
300 | ^^^^^^^^^^^^^^^^^^ | |
301 | ||
302 | The configuration options for syncing LDAP-based realms can be found in the | |
303 | `Sync Options` tab of the Add/Edit window. | |
304 | ||
305 | The configuration options are as follows: | |
306 | ||
307 | * `Bind User` (`bind_dn`): Refers to the LDAP account used to query users | |
308 | and groups. This account needs access to all desired entries. If it's set, the | |
309 | search will be carried out via binding; otherwise, the search will be carried | |
310 | out anonymously. The user must be a complete LDAP formatted distinguished name | |
311 | (DN), for example, `cn=admin,dc=example,dc=com`. | |
312 | ||
313 | * Groupname attr. (group_name_attr): Represents the | |
314 | users' groups. Only entries which adhere to the usual character limitations of | |
315 | the `user.cfg` are synced. Groups are synced with `-$realm` attached to the | |
316 | name, in order to avoid naming conflicts. Please ensure that a sync does not | |
317 | overwrite manually created groups. | |
318 | ||
319 | * `User classes` (`user_classes`): Objects classes associated with users. | |
320 | ||
321 | * `Group classes` (`group_classes`): Objects classes associated with groups. | |
322 | ||
323 | * `E-Mail attribute`: If the LDAP-based server specifies user email addresses, | |
324 | these can also be included in the sync by setting the associated attribute | |
325 | here. From the command line, this is achievable through the | |
326 | `--sync_attributes` parameter. | |
327 | ||
328 | * `User Filter` (`filter`): For further filter options to target specific users. | |
329 | ||
330 | * `Group Filter` (`group_filter`): For further filter options to target specific | |
331 | groups. | |
332 | ||
333 | NOTE: Filters allow you to create a set of additional match criteria, to narrow | |
334 | down the scope of a sync. Information on available LDAP filter types and their | |
335 | usage can be found at https://ldap.com/ldap-filters/[ldap.com]. | |
336 | ||
337 | ||
338 | [[pveum_ldap_sync_options]] | |
339 | Sync Options | |
340 | ^^^^^^^^^^^^ | |
341 | ||
342 | [thumbnail="screenshot/gui-datacenter-realm-add-ldap-sync-options.png"] | |
343 | ||
344 | In addition to the options specified in the previous section, you can also | |
345 | configure further options that describe the behavior of the sync operation. | |
346 | ||
347 | These options are either set as parameters before the sync, or as defaults via | |
348 | the realm option `sync-defaults-options`. | |
349 | ||
350 | The main options for syncing are: | |
351 | ||
352 | * `Scope` (`scope`): The scope of what to sync. It can be either `users`, | |
353 | `groups` or `both`. | |
354 | ||
355 | * `Enable new` (`enable-new`): If set, the newly synced users are enabled and | |
356 | can log in. The default is `true`. | |
357 | ||
358 | * `Full` (`full`): If set, the sync uses the LDAP directory as a source of | |
359 | truth, overwriting information set manually in the `user.cfg` and deleting | |
360 | users and groups which are not present in the LDAP directory. If not set, only | |
361 | new data is written to the configuration, and no stale users are deleted. | |
362 | ||
363 | * `Purge ACLs` (`purge`): If set, sync removes all corresponding ACLs when | |
364 | removing users and groups. This is only useful with the option `full`. | |
365 | ||
366 | * `Preview` (`dry-run`): No data is written to the config. This is useful if you | |
367 | want to see which users and groups would get synced to the `user.cfg`. | |
f3ee27eb DM |
368 | |
369 | ||
370 | [[pveum_openid]] | |
96942248 | 371 | OpenID Connect |
f3ee27eb DM |
372 | ~~~~~~~~~~~~~~ |
373 | ||
374 | The main OpenID Connect configuration options are: | |
375 | ||
78000a64 DW |
376 | * `Issuer URL` (`issuer-url`): This is the URL of the authorization server. |
377 | Proxmox uses the OpenID Connect Discovery protocol to automatically configure | |
f3ee27eb DM |
378 | further details. |
379 | + | |
96942248 | 380 | While it is possible to use unencrypted `http://` URLs, we strongly recommend to |
f3ee27eb DM |
381 | use encrypted `https://` connections. |
382 | ||
78000a64 | 383 | * `Realm` (`realm`): The realm identifier for {pve} users |
f3ee27eb | 384 | |
78000a64 | 385 | * `Client ID` (`client-id`): OpenID Client ID. |
f3ee27eb | 386 | |
78000a64 | 387 | * `Client Key` (`client-key`): Optional OpenID Client Key. |
f3ee27eb | 388 | |
78000a64 DW |
389 | * `Autocreate Users` (`autocreate`): Automatically create users if they do not |
390 | exist. While authentication is done at the OpenID server, all users still need | |
391 | an entry in the {pve} user configuration. You can either add them manually, or | |
392 | use the `autocreate` option to automatically add new users. | |
393 | ||
394 | * `Username Claim` (`username-claim`): OpenID claim used to generate the unique | |
395 | username (`subject`, `username` or `email`). | |
f3ee27eb DM |
396 | |
397 | Username mapping | |
398 | ^^^^^^^^^^^^^^^^ | |
399 | ||
96942248 DW |
400 | The OpenID Connect specification defines a single unique attribute |
401 | ('claim' in OpenID terms) named `subject`. By default, we use the | |
f3ee27eb DM |
402 | value of this attribute to generate {pve} usernames, by simple adding |
403 | `@` and the realm name: `${subject}@${realm}`. | |
404 | ||
96942248 | 405 | Unfortunately, most OpenID servers use random strings for `subject`, like |
f3ee27eb | 406 | `DGH76OKH34BNG3245SB`, so a typical username would look like |
96942248 | 407 | `DGH76OKH34BNG3245SB@yourrealm`. While unique, it is difficult for |
f3ee27eb | 408 | humans to remember such random strings, making it quite impossible to |
96942248 | 409 | associate real users with this. |
f3ee27eb DM |
410 | |
411 | The `username-claim` setting allows you to use other attributes for | |
96942248 DW |
412 | the username mapping. Setting it to `username` is preferred if the |
413 | OpenID Connect server provides that attribute and guarantees its | |
f3ee27eb DM |
414 | uniqueness. |
415 | ||
96942248 | 416 | Another option is to use `email`, which also yields human readable |
62547dfa | 417 | usernames. Again, only use this setting if the server guarantees the |
f3ee27eb DM |
418 | uniqueness of this attribute. |
419 | ||
420 | Examples | |
421 | ^^^^^^^^ | |
422 | ||
96942248 | 423 | Here is an example of creating an OpenID realm using Google. You need to |
f3ee27eb | 424 | replace `--client-id` and `--client-key` with the values |
96942248 | 425 | from your Google OpenID settings. |
f3ee27eb DM |
426 | |
427 | ---- | |
428 | pveum realm add myrealm1 --type openid --issuer-url https://accounts.google.com --client-id XXXX --client-key YYYY --username-claim email | |
429 | ---- | |
430 | ||
96942248 DW |
431 | The above command uses `--username-claim email`, so that the usernames on the |
432 | {pve} side look like `example.user@google.com@myrealm1`. | |
f3ee27eb | 433 | |
96942248 DW |
434 | Keycloak (https://www.keycloak.org/) is a popular open source Identity |
435 | and Access Management tool, which supports OpenID Connect. In the following | |
f3ee27eb | 436 | example, you need to replace the `--issuer-url` and `--client-id` with |
96942248 | 437 | your information: |
f3ee27eb DM |
438 | |
439 | ---- | |
440 | pveum realm add myrealm2 --type openid --issuer-url https://your.server:8080/auth/realms/your-realm --client-id XXX --username-claim username | |
441 | ---- | |
442 | ||
96942248 | 443 | Using `--username-claim username` enables simple usernames on the |
f3ee27eb DM |
444 | {pve} side, like `example.user@myrealm2`. |
445 | ||
96942248 DW |
446 | WARNING: You need to ensure that the user is not allowed to edit |
447 | the username setting themselves (on the Keycloak server). | |
f3ee27eb DM |
448 | |
449 | ||
0523992b | 450 | [[pveum_tfa_auth]] |
96942248 | 451 | Two-Factor Authentication |
9e8f2770 WB |
452 | ------------------------- |
453 | ||
74662f51 | 454 | There are two ways to use two-factor authentication: |
2837cf1d | 455 | |
74662f51 | 456 | It can be required by the authentication realm, either via 'TOTP' |
96942248 DW |
457 | (Time-based One-Time Password) or 'YubiKey OTP'. In this case, a newly |
458 | created user needs to have their keys added immediately, as there is no way to | |
74662f51 OB |
459 | log in without the second factor. In the case of 'TOTP', users can |
460 | also change the 'TOTP' later on, provided they can log in first. | |
2837cf1d | 461 | |
96942248 | 462 | Alternatively, users can choose to opt-in to two-factor authentication |
1245cebe WB |
463 | later on, even if the realm does not enforce it. |
464 | ||
465 | Available Second Factors | |
466 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
467 | ||
468 | You can set up multiple second factors, in order to avoid a situation in | |
469 | which losing your smartphone or security key locks you out of your | |
470 | account permanently. | |
471 | ||
472 | The following two-factor authentication methods are available in | |
473 | addition to realm-enforced TOTP and YubiKey OTP: | |
474 | ||
475 | * User configured TOTP | |
476 | (https://en.wikipedia.org/wiki/Time-based_One-Time_Password[Time-based One-Time Password]). | |
477 | A short code derived from a shared secret and the current time, it changes | |
478 | every 30 seconds. | |
479 | * WebAuthn (https://en.wikipedia.org/wiki/WebAuthn[Web Authentication]). | |
480 | A general standard for authentication. It is implemented by various | |
481 | security devices, like hardware keys or trusted platform modules (TPM) | |
482 | from a computer or smart phone. | |
483 | * Single use Recovery Keys. A list of keys which should either be | |
484 | printed out and locked in a secure place or saved digitally in an | |
485 | electronic vault. Each key can be used only once. These are perfect for | |
486 | ensuring that you are not locked out, even if all of your other second | |
487 | factors are lost or corrupt. | |
488 | ||
489 | Before WebAuthn was supported, U2F could be setup by the user. Existing | |
490 | U2F factors can still be used, but it is recommended to switch to | |
491 | WebAuthn, once it is configured on the server. | |
2837cf1d | 492 | |
96942248 | 493 | Realm Enforced Two-Factor Authentication |
2837cf1d WB |
494 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
495 | ||
74662f51 OB |
496 | This can be done by selecting one of the available methods via the |
497 | 'TFA' dropdown box when adding or editing an Authentication Realm. | |
96942248 DW |
498 | When a realm has TFA enabled, it becomes a requirement, and only users |
499 | with configured TFA will be able to log in. | |
9e8f2770 WB |
500 | |
501 | Currently there are two methods available: | |
502 | ||
96942248 | 503 | Time-based OATH (TOTP):: This uses the standard HMAC-SHA1 algorithm, |
74662f51 | 504 | where the current time is hashed with the user's configured key. The |
96942248 | 505 | time step and password length parameters are configurable. |
9e8f2770 | 506 | + |
74662f51 OB |
507 | A user can have multiple keys configured (separated by spaces), and the keys |
508 | can be specified in Base32 (RFC3548) or hexadecimal notation. | |
9e8f2770 | 509 | + |
74662f51 | 510 | {pve} provides a key generation tool (`oathkeygen`) which prints out a random |
96942248 | 511 | key in Base32 notation, that can be used directly with various OTP tools, such |
74662f51 OB |
512 | as the `oathtool` command line tool, or on Android Google Authenticator, |
513 | FreeOTP, andOTP or similar applications. | |
9e8f2770 WB |
514 | |
515 | YubiKey OTP:: | |
516 | For authenticating via a YubiKey a Yubico API ID, API KEY and validation | |
517 | server URL must be configured, and users must have a YubiKey available. In | |
518 | order to get the key ID from a YubiKey, you can trigger the YubiKey once | |
96942248 | 519 | after connecting it via USB, and copy the first 12 characters of the typed |
9e8f2770 | 520 | password into the user's 'Key IDs' field. |
74662f51 | 521 | |
74662f51 OB |
522 | Please refer to the https://developers.yubico.com/OTP/[YubiKey OTP] |
523 | documentation for how to use the | |
9e8f2770 | 524 | https://www.yubico.com/products/services-software/yubicloud/[YubiCloud] or |
96942248 | 525 | https://developers.yubico.com/Software_Projects/Yubico_OTP/YubiCloud_Validation_Servers/[host your own verification server]. |
9e8f2770 | 526 | |
0523992b | 527 | [[pveum_user_configured_totp]] |
96942248 | 528 | User Configured TOTP Authentication |
2837cf1d WB |
529 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
530 | ||
1245cebe WB |
531 | Users can choose to enable 'TOTP' or 'WebAuthn' as a second factor on login, via |
532 | the 'TFA' button in the user list (unless the realm enforces 'YubiKey OTP'). | |
2837cf1d | 533 | |
1245cebe WB |
534 | Users can always add and use one time 'Recovery Keys'. |
535 | ||
536 | [thumbnail="screenshot/gui-datacenter-two-factor.png"] | |
2b59fcfb | 537 | |
96942248 DW |
538 | After opening the 'TFA' window, the user is presented with a dialog to set up |
539 | 'TOTP' authentication. The 'Secret' field contains the key, which can be | |
540 | randomly generated via the 'Randomize' button. An optional 'Issuer Name' can be | |
541 | added to provide information to the 'TOTP' app about what the key belongs to. | |
2837cf1d | 542 | Most 'TOTP' apps will show the issuer name together with the corresponding |
96942248 | 543 | 'OTP' values. The username is also included in the QR code for the 'TOTP' app. |
2837cf1d | 544 | |
96942248 DW |
545 | After generating a key, a QR code will be displayed, which can be used with most |
546 | OTP apps such as FreeOTP. The user then needs to verify the current user | |
2837cf1d | 547 | password (unless logged in as 'root'), as well as the ability to correctly use |
96942248 DW |
548 | the 'TOTP' key, by typing the current 'OTP' value into the 'Verification Code' |
549 | field and pressing the 'Apply' button. | |
2837cf1d | 550 | |
1245cebe WB |
551 | [[user_tfa_setup_totp]] |
552 | === TOTP | |
553 | ||
554 | [thumbnail="screenshot/pve-gui-tfa-add-totp.png"] | |
555 | ||
556 | There is no server setup required. Simply install a TOTP app on your | |
557 | smartphone (for example, https://freeotp.github.io/[FreeOTP]) and use | |
558 | the Proxmox Backup Server web-interface to add a TOTP factor. | |
559 | ||
560 | [[user_tfa_setup_webauthn]] | |
561 | === WebAuthn | |
562 | ||
563 | For WebAuthn to work, you need to have two things: | |
564 | ||
565 | * A trusted HTTPS certificate (for example, by using | |
566 | https://pve.proxmox.com/wiki/Certificate_Management[Let's Encrypt]). | |
567 | While it probably works with an untrusted certificate, some browsers may | |
568 | warn or refuse WebAuthn operations if it is not trusted. | |
569 | * Setup the WebAuthn configuration (see *Datacenter -> Options -> | |
570 | WebAuthn Settings* in the Proxmox VE web interface). This can be | |
571 | auto-filled in most setups. | |
572 | ||
573 | Once you have fulfilled both of these requirements, you can add a WebAuthn | |
574 | configuration in the *Two Factor* panel under *Datacenter -> Permissions -> Two | |
575 | Factor*. | |
576 | ||
577 | [[user_tfa_setup_recovery_keys]] | |
578 | === Recovery Keys | |
579 | ||
580 | [thumbnail="screenshot/pve-gui-tfa-add-recovery-keys.png"] | |
581 | ||
582 | Recovery key codes do not need any preparation; you can simply create a | |
583 | set of recovery keys in the *Two Factor* panel under *Datacenter -> Permissions | |
584 | -> Two Factor*. | |
585 | ||
586 | NOTE: There can only be one set of single-use recovery keys per user at any | |
587 | time. | |
588 | ||
589 | ||
e455949b | 590 | [[pveum_configure_webauthn]] |
1245cebe WB |
591 | Server Side Webauthn Configuration |
592 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
593 | ||
594 | [thumbnail="screenshot/gui-datacenter-webauthn-edit.png"] | |
595 | ||
596 | To allow users to use 'WebAuthn' authentication, it is necessaary to use a valid | |
597 | domain with a valid SSL certificate, otherwise some browsers may warn or refuse | |
598 | to authenticate altogether. | |
599 | ||
600 | NOTE: Changing the 'WebAuthn' configuration may render all existing 'WebAuthn' | |
601 | registrations unusable! | |
602 | ||
603 | This is done via `/etc/pve/datacenter.cfg`. For instance: | |
604 | ||
605 | ---- | |
606 | webauthn: | |
607 | rp=mypve.example.com,origin=https://mypve.example.com:8006,id=mypve.example.com | |
608 | ---- | |
609 | ||
97d63abc | 610 | [[pveum_configure_u2f]] |
96942248 | 611 | Server Side U2F Configuration |
2837cf1d WB |
612 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
613 | ||
1245cebe WB |
614 | NOTE: It is recommended to use WebAuthn instead. |
615 | ||
58df830b | 616 | To allow users to use 'U2F' authentication, it may be necessary to use a valid |
96942248 DW |
617 | domain with a valid SSL certificate, otherwise, some browsers may print |
618 | a warning or reject U2F usage altogether. Initially, an 'AppId' | |
2837cf1d WB |
619 | footnote:[AppId https://developers.yubico.com/U2F/App_ID.html] |
620 | needs to be configured. | |
621 | ||
622 | NOTE: Changing the 'AppId' will render all existing 'U2F' registrations | |
623 | unusable! | |
624 | ||
96942248 | 625 | This is done via `/etc/pve/datacenter.cfg`. For instance: |
2837cf1d WB |
626 | |
627 | ---- | |
628 | u2f: appid=https://mypve.example.com:8006 | |
629 | ---- | |
630 | ||
96942248 DW |
631 | For a single node, the 'AppId' can simply be the address of the web-interface, |
632 | exactly as it is used in the browser, including the 'https://' and the port, as | |
633 | shown above. Please note that some browsers may be more strict than others when | |
634 | matching 'AppIds'. | |
2837cf1d WB |
635 | |
636 | When using multiple nodes, it is best to have a separate `https` server | |
637 | providing an `appid.json` | |
638 | footnote:[Multi-facet apps: https://developers.yubico.com/U2F/App_ID.html] | |
639 | file, as it seems to be compatible with most | |
640 | browsers. If all nodes use subdomains of the same top level domain, it may be | |
96942248 DW |
641 | enough to use the TLD as 'AppId'. It should however be noted that some browsers |
642 | may not accept this. | |
2837cf1d WB |
643 | |
644 | NOTE: A bad 'AppId' will usually produce an error, but we have encountered | |
96942248 DW |
645 | situations when this does not happen, particularly when using a top level domain |
646 | 'AppId' for a node that is accessed via a subdomain in Chromium. For this reason | |
647 | it is recommended to test the configuration with multiple browsers, as changing | |
648 | the 'AppId' later will render existing 'U2F' registrations unusable. | |
2837cf1d | 649 | |
0523992b | 650 | [[pveum_user_configured_u2f]] |
96942248 | 651 | Activating U2F as a User |
2837cf1d WB |
652 | ~~~~~~~~~~~~~~~~~~~~~~~~ |
653 | ||
654 | To enable 'U2F' authentication, open the 'TFA' window's 'U2F' tab, type in the | |
655 | current password (unless logged in as root), and press the 'Register' button. | |
96942248 | 656 | If the server is set up correctly and the browser accepts the server's provided |
2837cf1d | 657 | 'AppId', a message will appear prompting the user to press the button on the |
96942248 DW |
658 | 'U2F' device (if it is a 'YubiKey', the button light should be toggling on and |
659 | off steadily, roughly twice per second). | |
2837cf1d WB |
660 | |
661 | Firefox users may need to enable 'security.webauth.u2f' via 'about:config' | |
662 | before they can use a 'U2F' token. | |
9e8f2770 | 663 | |
80c0adcb | 664 | [[pveum_permission_management]] |
04f44730 | 665 | Permission Management |
3c8533f2 DM |
666 | --------------------- |
667 | ||
04f44730 | 668 | In order for a user to perform an action (such as listing, modifying or |
96942248 | 669 | deleting parts of a VM's configuration), the user needs to have the |
04f44730 WB |
670 | appropriate permissions. |
671 | ||
672 | {pve} uses a role and path based permission management system. An entry in | |
181db098 | 673 | the permissions table allows a user, group or token to take on a specific role |
96942248 | 674 | when accessing an 'object' or 'path'. This means that such an access rule can |
181db098 FG |
675 | be represented as a triple of '(path, user, role)', '(path, group, |
676 | role)' or '(path, token, role)', with the role containing a set of allowed | |
677 | actions, and the path representing the target of these actions. | |
04f44730 | 678 | |
5eba0743 | 679 | |
80c0adcb | 680 | [[pveum_roles]] |
853d288b WB |
681 | Roles |
682 | ~~~~~ | |
683 | ||
684 | A role is simply a list of privileges. Proxmox VE comes with a number | |
96942248 | 685 | of predefined roles, which satisfy most requirements. |
853d288b | 686 | |
96942248 | 687 | * `Administrator`: has full privileges |
853d288b | 688 | * `NoAccess`: has no privileges (used to forbid access) |
96942248 DW |
689 | * `PVEAdmin`: can do most tasks, but has no rights to modify system settings (`Sys.PowerMgmt`, `Sys.Modify`, `Realm.Allocate`) |
690 | * `PVEAuditor`: has read only access | |
853d288b WB |
691 | * `PVEDatastoreAdmin`: create and allocate backup space and templates |
692 | * `PVEDatastoreUser`: allocate backup space and view storage | |
693 | * `PVEPoolAdmin`: allocate pools | |
694 | * `PVESysAdmin`: User ACLs, audit, system console and system logs | |
695 | * `PVETemplateUser`: view and clone templates | |
96942248 | 696 | * `PVEUserAdmin`: manage users |
853d288b | 697 | * `PVEVMAdmin`: fully administer VMs |
96942248 | 698 | * `PVEVMUser`: view, backup, configure CD-ROM, VM console, VM power management |
853d288b | 699 | |
96942248 | 700 | You can see the whole set of predefined roles in the GUI. |
853d288b | 701 | |
96942248 | 702 | You can add new roles via the GUI or the command line. |
5e6b02ff TL |
703 | |
704 | [thumbnail="screenshot/gui-datacenter-role-add.png"] | |
96942248 DW |
705 | From the GUI, navigate to the 'Permissions -> Roles' tab from 'Datacenter' and |
706 | click on the 'Create' button. There you can set a role name and select any | |
707 | desired privileges from the 'Privileges' drop-down menu. | |
853d288b | 708 | |
96942248 DW |
709 | To add a role through the command line, you can use the 'pveum' CLI tool, for |
710 | example: | |
853d288b WB |
711 | [source,bash] |
712 | ---- | |
96942248 DW |
713 | pveum role add PVE_Power-only --privs "VM.PowerMgmt VM.Console" |
714 | pveum role add Sys_Power-only --privs "Sys.PowerMgmt Sys.Console" | |
853d288b WB |
715 | ---- |
716 | ||
717 | ||
3c8533f2 DM |
718 | Privileges |
719 | ~~~~~~~~~~ | |
720 | ||
721 | A privilege is the right to perform a specific action. To simplify | |
722 | management, lists of privileges are grouped into roles, which can then | |
96942248 | 723 | be used in the permission table. Note that privileges cannot be directly |
0e1fda70 | 724 | assigned to users and paths without being part of a role. |
3c8533f2 | 725 | |
96942248 | 726 | We currently support the following privileges: |
3c8533f2 DM |
727 | |
728 | Node / System related privileges:: | |
729 | ||
730 | * `Permissions.Modify`: modify access permissions | |
96942248 DW |
731 | * `Sys.PowerMgmt`: node power management (start, stop, reset, shutdown, ...) |
732 | * `Sys.Console`: console access to node | |
733 | * `Sys.Syslog`: view syslog | |
734 | * `Sys.Audit`: view node status/config, Corosync cluster config, and HA config | |
735 | * `Sys.Modify`: create/modify/remove node network parameters | |
736 | * `Group.Allocate`: create/modify/remove groups | |
737 | * `Pool.Allocate`: create/modify/remove a pool | |
696ebb3c | 738 | * `Pool.Audit`: view a pool |
96942248 | 739 | * `Realm.Allocate`: create/modify/remove authentication realms |
3c8533f2 | 740 | * `Realm.AllocateUser`: assign user to a realm |
96942248 | 741 | * `User.Modify`: create/modify/remove user access and details. |
3c8533f2 DM |
742 | |
743 | Virtual machine related privileges:: | |
744 | ||
96942248 | 745 | * `VM.Allocate`: create/remove VM on a server |
3c8533f2 DM |
746 | * `VM.Migrate`: migrate VM to alternate server on cluster |
747 | * `VM.PowerMgmt`: power management (start, stop, reset, shutdown, ...) | |
748 | * `VM.Console`: console access to VM | |
749 | * `VM.Monitor`: access to VM monitor (kvm) | |
750 | * `VM.Backup`: backup/restore VMs | |
751 | * `VM.Audit`: view VM config | |
752 | * `VM.Clone`: clone/copy a VM | |
96942248 | 753 | * `VM.Config.Disk`: add/modify/remove disks |
3a433e9b | 754 | * `VM.Config.CDROM`: eject/change CD-ROM |
3c8533f2 | 755 | * `VM.Config.CPU`: modify CPU settings |
96942248 DW |
756 | * `VM.Config.Memory`: modify memory settings |
757 | * `VM.Config.Network`: add/modify/remove network devices | |
758 | * `VM.Config.HWType`: modify emulated hardware types | |
3c8533f2 | 759 | * `VM.Config.Options`: modify any other VM configuration |
96942248 | 760 | * `VM.Snapshot`: create/delete VM snapshots |
3c8533f2 DM |
761 | |
762 | Storage related privileges:: | |
763 | ||
96942248 | 764 | * `Datastore.Allocate`: create/modify/remove a datastore and delete volumes |
3c8533f2 | 765 | * `Datastore.AllocateSpace`: allocate space on a datastore |
96942248 | 766 | * `Datastore.AllocateTemplate`: allocate/upload templates and ISO images |
3c8533f2 DM |
767 | * `Datastore.Audit`: view/browse a datastore |
768 | ||
5eba0743 | 769 | |
b8eeec52 WB |
770 | Objects and Paths |
771 | ~~~~~~~~~~~~~~~~~ | |
772 | ||
96942248 DW |
773 | Access permissions are assigned to objects, such as virtual machines, |
774 | storages or resource pools. | |
b8eeec52 | 775 | We use file system like paths to address these objects. These paths form a |
96942248 | 776 | natural tree, and permissions of higher levels (shorter paths) can |
b8eeec52 WB |
777 | optionally be propagated down within this hierarchy. |
778 | ||
7d48940b | 779 | [[pveum_templated_paths]] |
b8eeec52 WB |
780 | Paths can be templated. When an API call requires permissions on a |
781 | templated path, the path may contain references to parameters of the API | |
782 | call. These references are specified in curly braces. Some parameters are | |
96942248 | 783 | implicitly taken from the API call's URI. For instance, the permission path |
b8eeec52 WB |
784 | `/nodes/{node}` when calling '/nodes/mynode/status' requires permissions on |
785 | `/nodes/mynode`, while the path `{path}` in a PUT request to `/access/acl` | |
786 | refers to the method's `path` parameter. | |
787 | ||
788 | Some examples are: | |
789 | ||
790 | * `/nodes/{node}`: Access to {pve} server machines | |
791 | * `/vms`: Covers all VMs | |
792 | * `/vms/{vmid}`: Access to specific VMs | |
96942248 DW |
793 | * `/storage/{storeid}`: Access to a specific storage |
794 | * `/pool/{poolname}`: Access to resources contained in a specific <<pveum_pools,pool>> | |
b8eeec52 WB |
795 | * `/access/groups`: Group administration |
796 | * `/access/realms/{realmid}`: Administrative access to realms | |
797 | ||
798 | ||
3c8533f2 DM |
799 | Inheritance |
800 | ^^^^^^^^^^^ | |
801 | ||
5eba0743 | 802 | As mentioned earlier, object paths form a file system like tree, and |
96942248 DW |
803 | permissions can be inherited by objects down that tree (the propagate flag is |
804 | set by default). We use the following inheritance rules: | |
3c8533f2 | 805 | |
74936daf WB |
806 | * Permissions for individual users always replace group permissions. |
807 | * Permissions for groups apply when the user is member of that group. | |
96942248 | 808 | * Permissions on deeper levels replace those inherited from an upper level. |
3c8533f2 | 809 | |
96942248 | 810 | Additionally, privilege separated tokens can never have permissions on any |
181db098 | 811 | given path that their associated user does not have. |
5eba0743 | 812 | |
80c0adcb | 813 | [[pveum_pools]] |
3c8533f2 DM |
814 | Pools |
815 | ~~~~~ | |
816 | ||
96942248 DW |
817 | Pools can be used to group a set of virtual machines and datastores. You can |
818 | then simply set permissions on pools (`/pool/{poolid}`), which are inherited by | |
819 | all pool members. This is a great way to simplify access control. | |
3c8533f2 | 820 | |
74936daf | 821 | |
96942248 DW |
822 | Which Permissions Do I Need? |
823 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
74936daf WB |
824 | |
825 | The required API permissions are documented for each individual | |
96942248 | 826 | method, and can be found at https://pve.proxmox.com/pve-docs/api-viewer/. |
74936daf | 827 | |
96942248 | 828 | The permissions are specified as a list, which can be interpreted as a |
74936daf WB |
829 | tree of logic and access-check functions: |
830 | ||
831 | `["and", <subtests>...]` and `["or", <subtests>...]`:: | |
832 | Each(`and`) or any(`or`) further element in the current list has to be true. | |
833 | ||
834 | `["perm", <path>, [ <privileges>... ], <options>...]`:: | |
7d48940b | 835 | The `path` is a templated parameter (see |
87ba80b0 | 836 | <<pveum_templated_paths,Objects and Paths>>). All (or, if the `any` |
7d48940b | 837 | option is used, any) of the listed |
74936daf WB |
838 | privileges must be allowed on the specified path. If a `require-param` |
839 | option is specified, then its specified parameter is required even if the | |
840 | API call's schema otherwise lists it as being optional. | |
841 | ||
842 | `["userid-group", [ <privileges>... ], <options>...]`:: | |
470d4313 | 843 | The caller must have any of the listed privileges on `/access/groups`. In |
96942248 | 844 | addition, there are two possible checks, depending on whether the |
74936daf WB |
845 | `groups_param` option is set: |
846 | + | |
847 | * `groups_param` is set: The API call has a non-optional `groups` parameter | |
848 | and the caller must have any of the listed privileges on all of the listed | |
849 | groups. | |
850 | * `groups_param` is not set: The user passed via the `userid` parameter | |
851 | must exist and be part of a group on which the caller has any of the listed | |
852 | privileges (via the `/access/groups/<group>` path). | |
853 | ||
854 | `["userid-param", "self"]`:: | |
855 | The value provided for the API call's `userid` parameter must refer to the | |
96942248 DW |
856 | user performing the action (usually in conjunction with `or`, to allow |
857 | users to perform an action on themselves, even if they don't have elevated | |
858 | privileges). | |
74936daf WB |
859 | |
860 | `["userid-param", "Realm.AllocateUser"]`:: | |
861 | The user needs `Realm.AllocateUser` access to `/access/realm/<realm>`, with | |
470d4313 | 862 | `<realm>` referring to the realm of the user passed via the `userid` |
74936daf WB |
863 | parameter. Note that the user does not need to exist in order to be |
864 | associated with a realm, since user IDs are passed in the form of | |
865 | `<username>@<realm>`. | |
866 | ||
867 | `["perm-modify", <path>]`:: | |
7d48940b DM |
868 | The `path` is a templated parameter (see |
869 | <<pveum_templated_paths,Objects and Paths>>). The user needs either the | |
96942248 | 870 | `Permissions.Modify` privilege or, |
74936daf WB |
871 | depending on the path, the following privileges as a possible substitute: |
872 | + | |
873 | * `/storage/...`: additionally requires 'Datastore.Allocate` | |
874 | * `/vms/...`: additionally requires 'VM.Allocate` | |
875 | * `/pool/...`: additionally requires 'Pool.Allocate` | |
876 | + | |
877 | If the path is empty, `Permission.Modify` on `/access` is required. | |
878 | ||
3c8533f2 DM |
879 | Command Line Tool |
880 | ----------------- | |
881 | ||
882 | Most users will simply use the GUI to manage users. But there is also | |
87ba80b0 | 883 | a fully featured command line tool called `pveum` (short for ``**P**roxmox |
4f6e7e05 WB |
884 | **VE** **U**ser **M**anager''). Please note that all Proxmox VE command |
885 | line tools are wrappers around the API, so you can also access those | |
87ba80b0 | 886 | functions through the REST API. |
3c8533f2 | 887 | |
96942248 | 888 | Here are some simple usage examples. To show help, type: |
3c8533f2 DM |
889 | |
890 | [source,bash] | |
891 | pveum | |
892 | ||
893 | or (to show detailed help about a specific command) | |
894 | ||
895 | [source,bash] | |
9135e321 | 896 | pveum help user add |
3c8533f2 DM |
897 | |
898 | Create a new user: | |
899 | ||
900 | [source,bash] | |
9135e321 | 901 | pveum user add testuser@pve -comment "Just a test" |
3c8533f2 | 902 | |
96942248 | 903 | Set or change the password (not all realms support this): |
3c8533f2 DM |
904 | |
905 | [source,bash] | |
906 | pveum passwd testuser@pve | |
907 | ||
908 | Disable a user: | |
909 | ||
910 | [source,bash] | |
9135e321 | 911 | pveum user modify testuser@pve -enable 0 |
3c8533f2 DM |
912 | |
913 | Create a new group: | |
914 | ||
915 | [source,bash] | |
9135e321 | 916 | pveum group add testgroup |
3c8533f2 DM |
917 | |
918 | Create a new role: | |
919 | ||
920 | [source,bash] | |
9135e321 | 921 | pveum role add PVE_Power-only -privs "VM.PowerMgmt VM.Console" |
3c8533f2 DM |
922 | |
923 | ||
924 | Real World Examples | |
925 | ------------------- | |
926 | ||
5eba0743 | 927 | |
3c8533f2 DM |
928 | Administrator Group |
929 | ~~~~~~~~~~~~~~~~~~~ | |
930 | ||
96942248 DW |
931 | It is possible that an administrator would want to create a group of users with |
932 | full administrator rights (without using the root account). | |
3c8533f2 | 933 | |
96942248 | 934 | To do this, first define the group: |
3c8533f2 DM |
935 | |
936 | [source,bash] | |
9135e321 | 937 | pveum group add admin -comment "System Administrators" |
3c8533f2 | 938 | |
96942248 | 939 | Then assign the role: |
3c8533f2 DM |
940 | |
941 | [source,bash] | |
9135e321 | 942 | pveum acl modify / -group admin -role Administrator |
3c8533f2 | 943 | |
96942248 | 944 | Finally, you can add users to the new 'admin' group: |
3c8533f2 DM |
945 | |
946 | [source,bash] | |
9135e321 | 947 | pveum user modify testuser@pve -group admin |
3c8533f2 DM |
948 | |
949 | ||
950 | Auditors | |
951 | ~~~~~~~~ | |
952 | ||
953 | You can give read only access to users by assigning the `PVEAuditor` | |
954 | role to users or groups. | |
955 | ||
96942248 | 956 | Example 1: Allow user `joe@pve` to see everything |
3c8533f2 DM |
957 | |
958 | [source,bash] | |
9135e321 | 959 | pveum acl modify / -user joe@pve -role PVEAuditor |
3c8533f2 | 960 | |
96942248 | 961 | Example 2: Allow user `joe@pve` to see all virtual machines |
3c8533f2 DM |
962 | |
963 | [source,bash] | |
9135e321 | 964 | pveum acl modify /vms -user joe@pve -role PVEAuditor |
3c8533f2 | 965 | |
5eba0743 | 966 | |
3c8533f2 DM |
967 | Delegate User Management |
968 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
969 | ||
96942248 | 970 | If you want to delegate user management to user `joe@pve`, you can do |
3c8533f2 DM |
971 | that with: |
972 | ||
973 | [source,bash] | |
9135e321 | 974 | pveum acl modify /access -user joe@pve -role PVEUserAdmin |
3c8533f2 | 975 | |
96942248 DW |
976 | User `joe@pve` can now add and remove users, and change other user attributes, |
977 | such as passwords. This is a very powerful role, and you most | |
978 | likely want to limit it to selected realms and groups. The following | |
979 | example allows `joe@pve` to modify users within the realm `pve`, if they | |
8c1189b6 | 980 | are members of group `customers`: |
3c8533f2 DM |
981 | |
982 | [source,bash] | |
9135e321 TL |
983 | pveum acl modify /access/realm/pve -user joe@pve -role PVEUserAdmin |
984 | pveum acl modify /access/groups/customers -user joe@pve -role PVEUserAdmin | |
3c8533f2 | 985 | |
0abc65b0 | 986 | NOTE: The user is able to add other users, but only if they are |
96942248 | 987 | members of the group `customers` and within the realm `pve`. |
8c1189b6 | 988 | |
96942248 | 989 | Limited API Token for Monitoring |
181db098 FG |
990 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
991 | ||
a13a971d DW |
992 | Permissions on API tokens are always a subset of those of their corresponding |
993 | user, meaning that an API token can't be used to carry out a task that the | |
994 | backing user has no permission to do. This section will demonstrate how you can | |
995 | use an API token with separate privileges, to limit the token owner's | |
996 | permissions further. | |
997 | ||
998 | Give the user `joe@pve` the role PVEVMAdmin on all VMs: | |
181db098 FG |
999 | |
1000 | [source,bash] | |
9135e321 | 1001 | pveum acl modify /vms -user joe@pve -role PVEVMAdmin |
181db098 FG |
1002 | |
1003 | Add a new API token with separate privileges, which is only allowed to view VM | |
96942248 | 1004 | information (for example, for monitoring purposes): |
181db098 FG |
1005 | |
1006 | [source,bash] | |
1007 | pveum user token add joe@pve monitoring -privsep 1 | |
9135e321 | 1008 | pveum acl modify /vms -token 'joe@pve!monitoring' -role PVEAuditor |
181db098 FG |
1009 | |
1010 | Verify the permissions of the user and token: | |
1011 | ||
1012 | [source,bash] | |
1013 | pveum user permissions joe@pve | |
1014 | pveum user token permissions joe@pve monitoring | |
3c8533f2 | 1015 | |
23b447be DW |
1016 | Resource Pools |
1017 | ~~~~~~~~~~~~~~ | |
3c8533f2 | 1018 | |
23b447be DW |
1019 | An enterprise is usually structured into several smaller departments, and it is |
1020 | common that you want to assign resources and delegate management tasks to each | |
1021 | of these. Let's assume that you want to set up a pool for a software development | |
96942248 | 1022 | department. First, create a group: |
3c8533f2 DM |
1023 | |
1024 | [source,bash] | |
9135e321 | 1025 | pveum group add developers -comment "Our software developers" |
3c8533f2 | 1026 | |
96942248 | 1027 | Now we create a new user which is a member of that group: |
3c8533f2 DM |
1028 | |
1029 | [source,bash] | |
9135e321 | 1030 | pveum user add developer1@pve -group developers -password |
3c8533f2 | 1031 | |
96942248 | 1032 | NOTE: The "-password" parameter will prompt you for a password |
3c8533f2 | 1033 | |
96942248 | 1034 | Then we create a resource pool for our development department to use: |
23b447be DW |
1035 | |
1036 | [source,bash] | |
9135e321 | 1037 | pveum pool add dev-pool --comment "IT development pool" |
23b447be | 1038 | |
96942248 | 1039 | Finally, we can assign permissions to that pool: |
3c8533f2 DM |
1040 | |
1041 | [source,bash] | |
9135e321 | 1042 | pveum acl modify /pool/dev-pool/ -group developers -role PVEAdmin |
3c8533f2 | 1043 | |
96942248 | 1044 | Our software developers can now administer the resources assigned to |
3c8533f2 DM |
1045 | that pool. |
1046 | ||
1047 | ||
1048 | ifdef::manvolnum[] | |
1049 | include::pve-copyright.adoc[] | |
1050 | endif::manvolnum[] | |
1051 |