@@ -412,6 +412,7 @@ pve_groups: [] # List of group definitions to manage in PVE. See section on User
412
412
pve_users: [] # List of user definitions to manage in PVE. See section on User Management.
413
413
pve_storages: [] # List of storages to manage in PVE. See section on Storage Management.
414
414
pve_datacenter_cfg: {} # Dictionary to configure the PVE datacenter.cfg config file.
415
+ pve_domains_cfg: {} # List of realms to use as authentication sources in the PVE domains.cfg config file.
415
416
```
416
417
417
418
To enable clustering with this role, configure the following variables appropriately:
@@ -462,6 +463,36 @@ In order for live reloading of network interfaces to work via the PVE web UI,
462
463
you need to install the ` ifupdown2 ` package. Note that this will remove
463
464
` ifupdown ` . You can specify this using the ` pve_extra_packages ` role variable.
464
465
466
+ You can set realms / domains as authentication sources in the ` domains.cfg ` configuration file.
467
+ If this file is not present, only the ` Linux PAM ` and ` Proxmox VE authentication server ` realms
468
+ are available. Supported types are ` pam ` , ` pve ` , ` ad ` and ` ldap ` .
469
+ One realm should have the ` default: 1 ` property to mark it as the default:
470
+
471
+ ```
472
+ pve_domains_cfg:
473
+ - name: pam
474
+ type: pam
475
+ comment: Linux PAM standard authentication
476
+ - name: pve
477
+ type: pve
478
+ comment: Proxmox VE authentication server
479
+ - name: AD
480
+ type: ad
481
+ comment: Active Directory authentication
482
+ domain: yourdomain.com
483
+ server1: dc01.yourdomain.com
484
+ default: 1
485
+ secure: 1
486
+ server2: dc02.yourdomain.com
487
+ - name: LDAP
488
+ type: ldap
489
+ base_dn: CN=Users,dc=yourdomain,dc=com
490
+ server1: ldap1.yourdomain.com
491
+ user_attr: uid
492
+ secure: 1
493
+ server2: ldap2.yourdomain.com
494
+ ```
495
+
465
496
## Dependencies
466
497
467
498
This role does not install NTP, so you should configure NTP yourself, e.g. with
0 commit comments