You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The As Built Report for vSphere is unable to determine privileges of user running the report if they receive privileges via a group (eg Active Directory group) rather than directly assigned.
To Reproduce
Steps to reproduce the behavior:
Run the As Built Report against a vCenter
Output includes messages such as "Insufficient user privileges to report vCenter Server licensing"
Expected behavior
As built report should be aware of privileges allocated via AD group.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please provide the following information about the system from which you are trying to generate a report):
OS: Windows 2012R2
Windows PowerShell version 5.1
3rd party PowerShell module name and version PowerCLI 12.4.1
AsBuiltReport Core module version 1.2.0
AsBuiltReport Report module name and version AsBuiltReport.VMware.vSphere 1.3.3.1
Additional context
Code in Invoke-AsBuiltReport.VMware.vSphere.ps1 beginning line 50 can be changed to instead check the effective user privileges rather than looking for directly assigned role.
For example, to get a list of the effective privileges at the top level in vCenter, you could use code like this. Then you can compare that list against the expected required privilege for a given piece of information (eg Global.Licenses for the ESXi licenses"
Describe the bug
The As Built Report for vSphere is unable to determine privileges of user running the report if they receive privileges via a group (eg Active Directory group) rather than directly assigned.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
As built report should be aware of privileges allocated via AD group.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please provide the following information about the system from which you are trying to generate a report):
Additional context
Code in Invoke-AsBuiltReport.VMware.vSphere.ps1 beginning line 50 can be changed to instead check the effective user privileges rather than looking for directly assigned role.
For example, to get a list of the effective privileges at the top level in vCenter, you could use code like this. Then you can compare that list against the expected required privilege for a given piece of information (eg Global.Licenses for the ESXi licenses"
The text was updated successfully, but these errors were encountered: