Hi,
After configuring AD authentication (Proxmox 5) all seemed to work fine. Until I shutdown the AD server specified in the "Server" dialogue (server1). I expected that proxmox would continue to authenticate users as the server specified in the "Fallback Server" dialogue (server2) was still running. However, proxmox could no longer authenticate users. Setting server2 in the "Server" dialogue while server1 remained shutdown resulted in Proxmox successfully authenticating users. It would appear "Fallback Server" dialogue is not configured correctly. I've had a quick look at the auth.log which seems not to log AD authentication, so was also wondering which log might show what is happening?
proxmox-ve: 5.0-25 (running kernel: 4.13.4-1-pve) pve-manager: 5.0-34 (running version: 5.0-34/b325d69e) pve-kernel-4.13.4-1-pve: 4.13.4-25 pve-kernel-4.10.17-2-pve: 4.10.17-20 pve-kernel-4.10.17-3-pve: 4.10.17-23 libpve-http-server-perl: 2.0-6 lvm2: 2.02.168-pve6 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster: 5.0-15 qemu-server: 5.0-17 pve-firmware: 2.0-3 libpve-common-perl: 5.0-20 libpve-guest-common-perl: 2.0-13 libpve-access-control: 5.0-7 libpve-storage-perl: 5.0-16 pve-libspice-server1: 0.12.8-3 vncterm: 1.5-2 pve-docs: 5.0-10 pve-qemu-kvm: 2.9.1-2 pve-container: 2.0-17 pve-firewall: 3.0-3 pve-ha-manager: 2.0-3 ksm-control-daemon: 1.2-2 glusterfs-client: 3.8.8-1 lxc-pve: 2.1.0-2 lxcfs: 2.0.7-pve4 criu: 2.11.1-1~bpo90 novnc-pve: 0.6-4 smartmontools: 6.5+svn4324-1 zfsutils-linux: 0.7.2-pve1~bpo90
After configuring AD authentication (Proxmox 5) all seemed to work fine. Until I shutdown the AD server specified in the "Server" dialogue (server1). I expected that proxmox would continue to authenticate users as the server specified in the "Fallback Server" dialogue (server2) was still running. However, proxmox could no longer authenticate users. Setting server2 in the "Server" dialogue while server1 remained shutdown resulted in Proxmox successfully authenticating users. It would appear "Fallback Server" dialogue is not configured correctly. I've had a quick look at the auth.log which seems not to log AD authentication, so was also wondering which log might show what is happening?
proxmox-ve: 5.0-25 (running kernel: 4.13.4-1-pve) pve-manager: 5.0-34 (running version: 5.0-34/b325d69e) pve-kernel-4.13.4-1-pve: 4.13.4-25 pve-kernel-4.10.17-2-pve: 4.10.17-20 pve-kernel-4.10.17-3-pve: 4.10.17-23 libpve-http-server-perl: 2.0-6 lvm2: 2.02.168-pve6 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster: 5.0-15 qemu-server: 5.0-17 pve-firmware: 2.0-3 libpve-common-perl: 5.0-20 libpve-guest-common-perl: 2.0-13 libpve-access-control: 5.0-7 libpve-storage-perl: 5.0-16 pve-libspice-server1: 0.12.8-3 vncterm: 1.5-2 pve-docs: 5.0-10 pve-qemu-kvm: 2.9.1-2 pve-container: 2.0-17 pve-firewall: 3.0-3 pve-ha-manager: 2.0-3 ksm-control-daemon: 1.2-2 glusterfs-client: 3.8.8-1 lxc-pve: 2.1.0-2 lxcfs: 2.0.7-pve4 criu: 2.11.1-1~bpo90 novnc-pve: 0.6-4 smartmontools: 6.5+svn4324-1 zfsutils-linux: 0.7.2-pve1~bpo90