Feature Request V13 Host Management UI, AD authentication test

[sdolcourt]

Case 03552510 as the inspiration for this feature request

Currently Host Settings | Network only shows name of joined domain, does not include any information about the domain controller that was selected as a target, when the domain join process was effected. I would requet that the G/TUI display the DC that the VSA is talking to, for its AD communication.

There is no obvious means to test an AD account against AD, to determine if AD authentication will work. Sorry, I haven't looked within the TUI or SSH to see what's available for VSA domain join, or continuing management.

Feature request is an AD account authentication test, and output success or failure to the UI for copy, or perhaps to a log.

Veeam is not Actifio, different products each. But the configuration elements of which Actifio linked to AD, allowed input of TCP port (389, 636, 3268, 3269), TLS enable checkbox, input fields for privileged user DN to bind to AD, search by base DN, and username attribute, e.g. samaccountname. Checkbox for allow caching credential if directory not available. Naturally, input fields for password and confirm password of privileged user DN. And....the all important test button. Gotta have the test button. It's all about the test button. Clickity click, the test button.

In our situation, we have a privileged user DN located in a child domain to bind to AD, but the search by base DN is the forest root.

If I have failed to find in documentation the process used by VSA to join and work with AD, my regrets. But I don't recall anything detailed about how Veeam uses AD, it's just join VSA to the domain, and start using UPN formatted accounts. Request is documentation (if not already existing) exactly detailing how Veeam is interacting with AD.

[Dima P.]

Hello Seth,

Naturally, input fields for password and confirm password of privileged user DN. And....the all important test button. Gotta have the test button. It's all about the test button. Clickity click, the test button.

Good request, thank you!

If I have failed to find in documentation the process used by VSA to join and work with AD, my regrets. But I don't recall anything detailed about how Veeam uses AD, it's just join VSA to the domain, and start using UPN formatted accounts. Request is documentation (if not already existing) exactly detailing how Veeam is interacting with AD.

Domain joined VSA enable Kerberos authentication, allows you to use users from AD for Veeam B&R user roles and perform the domain discovery for workload protection (for example agent management allows creating Active Directory based protection groups). Thank you!

[sdolcourt]

Thank you, Dima!