Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Active Directory Authentication Sources in vRealize Operations (68131)

Last Updated: 10/12/2021Categories: InformationalTotal Views: 6032Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

In previous versions of vRealize Operations it's been possible to login by providing only the username without the domain suffix when the userPrincipalName option has been selected in the Active Directory authentication source.
This caused massive reads per login from the database when there were large numbers of imported AD users, since the whole user list would be retrieved from the database and iteration was done over the complete list to find the required user.

Starting in vRealize Operations 7.5, a single query per login is performed using the full format, [email-masked], which positively affects performance.
The limitation coming with this change means that the login will only be successful if the username's domain suffix matches the domain name specified in the Base DN option. Otherwise, the full username with domain suffix is required during login.

Solution

This is expected behavior in vRealize Operations 7.5 and later when authenticating with Active Directory sources when the Common Name option is configured to use userPrincipalName.
When authenticating, use the format [email-masked].

Alternatively, to authenticate using short name (username only), configure the Active Directory Authentication Source to use samAccountName for the Common Name option.

Log into the vRealize Operations UI with the local admin user.

Navigate to Administration > Access > Authentication Sources.

Select the Active Directory source and click Edit.

Expand Details, and set Common Name to samAccountName.

Click OK.

You will need to re-import the Active Directory Users and Groups after setting Common Name to samAccountName.

Note: This will import a new user ID into the database.  Custom content (dashboards, reports, alerts, etc) owned by the previous user account will not be visible on the new user account.  Once the old user account is deleted from vRealize Operations, the custom content can be recovered under Administration > Management > Orphaned Content and assigned to the new user.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
ホストがクラスタから移動（削除）されると、「信頼できるインフラストラクチャ ホストの廃止 (Trusted Infrastructure Host Decommission)」というアラームがトリガされる (77146)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Manager

VMware vRealize Operations

Related Versions:

VMware vRealize Operations Manager 7.5.x

VMware vRealize Operations 8.x

Take Our Survey

Support Assistant