Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Configure RSA for two factor authentication using SAM Account as LDAP attribute (74577)

Last Updated: 3/31/2020Categories: How toTotal Views: 4235Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

The article provides the steps to configure RSA for vCenter authentication.

Purpose

The steps are consolidated to limit the minimum required steps to successfully configure RSA

Impact / Risks

Ensure there is a valid backup of all the PSC and vCenter server nodes in case of linked mode deployment model

Resolution

Pre-requisites:

Validate that the ldap attribute on the RSA is configured with sAMAccountName

PSC node is configured as standard agent on the RSA Authentication Manager

Validate that the certificates on the RSA node is trusted by the PSC

Download the sdconf.rec from the RSA Authentication Manager

Create the sdopts.rec file in the below format:

USESERVER=<RSA node IP address>
USESERVER=<RSA node IP address>
USESERVER=<RSA node IP address>
USESERVER=<RSA node IP address>
USESERVER=<RSA node IP address>

Note: Please refer to https://community.rsa.com/docs/DOC-46997 for the 'sdopts.rec' configuration

Commands to configure:

./opt/vmware/bin/sso-config.sh -t <SSO Domain> -set_authn_policy -securIDAuthn true
./opt/vmware/bin/sso-config.sh -set_rsa_config -t <SSO Domain> -logLevel DEBUG
./opt/vmware/bin/sso-config.sh -set_rsa_site -t <SSO Domain> -agentName <PSC FQDN> -sdConfFile /root/sdconf.rec -sdOptsFile /root/sdopts.rec
./opt/vmware/bin/sso-config.sh -set_rsa_userid_attr_map -t <SSO Domain> -idsName <Domain name> -ldapAttr sAMAccountName

Validate the Configuration via the below command:

./opt/vmware/bin/sso-config.sh -t vsphere.local -get_rsa_config

Sample Output:

./opt/vmware/bin/sso-config.sh -t vsphere.local -get_rsa_config
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
logonGuide:   Passcode for soft token users:<br>Enter only the generated token code from app<br><br>Passcode for hard token users:<br> Enter pin + generated token code
logLevel:   DEBUG
logFileSize:   1
maxLogFileCount:   10
connTimeOut:   60
readTimeOut:   60
encAlgList:   [AES/16, AES/32, AES/24]
idsUserIDAttributeMaps:   {<Domain Name>=sAMAccountName}
Sites [

[siteID:   66918bc1-41ae-4463-9eaf-b1f7c5dba649
agentName:   <PSC FQDN>
sdConfFile:   Binary value
sdOptsFile:   Binary value
]

Once completed, restart all the services on the PSC and vCenter(external deployment model)

Log in to the web client of the vCenter and validate configuration

Additional Notes:

In case if the RSA is mis-configured, the below steps needs to be followed to clear it.

Connect to the PSC node via JXplorer

Navigate to local->Services->Identitymanager->Tenants-><SSO Domain>

Delete "RSAAgentConfigurations" under the SSO domain

Log in to the PSC via ssh and delete "vsphere.local" under "/etc/vmware-sso/" (the folder name would be same as the SSO domain name)

Reboot the PSC and the vCenter server

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
•
[解決済み] AAGNT-184949：RD クライアントでユニバーサル バーコード加入を使用すると Intelligent Hub の自動起動と加入に失敗する (2961626)

KB
•
HTML5 に類似した VLAN ID がある場合、別の VLAN ID が作成される (75132)

KB
•
[解決済み] AAPP-6478：iOS 12 デバイスで MDM 経由の壁紙設定が断続的に失敗する (2961442)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant