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

Smart Card and RSA SecurID Authentication stops after upgrading to vCenter Server 7.0 (78057)

Last Updated: 4/13/2020Categories: TroubleshootingTotal Views: 15113Language:
Chinese (Simplified)JapaneseEnglish

9 like this article

Subscribe to get an email
newsletter with new updates

9 people found this helpful Please provide article feedback:

Symptoms

There are two primary symptoms of this issue:

During the upgrade process, you are see:

Smart card authentication may stop workking. Smart card settings may not be preserved, and smart card authentication may stop working.

or

RSA SecurID authentication may stop workking. RSA SecurID settings may not be preserved, and RSA SecurID authentication may stop working.

After upgrading, smart card or RSA SecurID authentication stops working and authentication to vCenter Server 7.0 fails with these authentication methods.

Purpose

This article describes how to handle smart card or RSA SecurID authentication when upgrading to vCenter Server 7.0.

Cause

During upgrade to vCenter Server 7.0, some configuration files may not be copied from the source vCenter Server or Platform Service Controller machine to the new vCenter Server 7.0 appliance. If this occurs, these authentication methods will stop working when the upgrade is completed. When this issue occurs, it will not prevent upgrade to vCenter Server 7.0 but will result in inability to log in with smart card or RSA SecurID once the upgrade is complete.

Resolution

VMware is aware of this issue and are working on a permanent solution. At this time, review the "Workaround" section below.

Workaround

After upgrade to the new vCenter Server 7.0 appliance is complete, it is necessary to configure smart card or RSA SecurID.

Smart Card

The XML  element beginning with tag <http> in the Reverse Proxy configuration file (/etc/vmware-rhttpproxy/conf.xml) needs to be configured to request the client certificate. See Configure the Reverse Proxy to Request Client Certificates .

Example:

<http>
<!-- Num of max proxy connections -->
<maxConnections> 2048 </maxConnections>
<requestClientCertificate>true</requestClientCertificate>
<!-- CA file, needed to scan all certificates in it and list them as acceptable CAs: -->
<clientCAListFile>/usr/lib/vmware-sso/vmware-sts/conf/clienttrustCA.pem</clientCAListFile>
<!-- Maximum size of a client certificate in case it is requested. -->
<clientCertificateMaxSize>4096</clientCertificateMaxSize>
</http>

The settings present on the pre-upgraded system at either /etc/vmware-rhttpproxy/conf.xml OR C:\ProgramData\VMware\vCenterServer\cfg\vmware-rhttpproxy\config.xml along with the file listed in tag <clientCAListFile> could be used on the newly upgraded appliance.

In the above example, the file /usr/lib/vmware-sso/vmware-sts/conf/clienttrustCA.pem needs to be copied to the newly upgraded appliance.

RSA SecurID

Multiple site IDs were possibly present before the upgrade or additional site IDs were created as part of the upgrade leading to the newly upgraded appliance being part of a site that is not configured for RSA SecurID.

See Set Up RSA SecurID Authentication .

The file sdconf.rec (required for configuring RSA SecurID) can be recovered from the pre-upgraded system at either /etc/vmware-sso/<tenant>/sdconf.rec or on Windows at %VMWARE_CFG_DIR%\sso\<tenant>\sdconf.rec. Assuming product defaults (tenant is vsphere.local, installed to C:\) then the appliance location would be /etc/vmware-sso/vsphere.local/sdconf.rec and on Windows at C:\ProgramData\VMware\vCenterServer\cfg\sso\vsphere.local\sdconf.rec

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
アレイから削除された後、動的に検出されたターゲットがユーザー インターフェイスに残る (78041)

KB
•
如何在 ADFS 2016 中为 vCenter Server 启用 OpenID Connect (78029)

KB
•
lsuv2-lsiv2 ドライバ プラグインから得られるスロット番号は、lsi_mr3 AERO コントローラ、および lsi_msgpt3 TRI モードのコントローラでは正しくありません。 (78127)

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 vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

VMware Tools 11.x

Take Our Survey

Support Assistant