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

"Not Connected" when LDAP connections to generic LDAP are made over SSL (78923)

Last Updated: 8/17/2023Categories: TroubleshootingTotal Views: 3682Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Specifying a generic FQDN resolved by multiple domain controllers for the configuration.

Multiple domain controllers are resolving to the generic name.

Simple mode is selected for configuration.

Configuration with single Domain Controller is successful.

Using Both SSL and Accept all certificates for the generic FQDN fails.

From /opt/vmware/vcloud-director/logs/vcloud-container-debug.log

2020-04-30 15:46:27,062 | ERROR  | pool-jetty-5916143    | LdapProviderImpl        | Error logging into LDAP. | requestId=<REQUEST_ID>,request=POST https://vcloud.example.com/cloud/amfsecure,requestTime=1234567890123,remoteAddress=<IP>:57372,userAgent=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTM...,accept=*/* method=orgService.testLdapConnection
javax.naming.CommunicationException: simple bind failed: example.com:636 [Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching example.com found]
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:219)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2791)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)

at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151)

Cause

This issue is caused when the certificates on the multiple domain controllers doesn't have the generic name in their Subject Alternative Name section.

Resolution

To resolve the issue, verify the certificates from the domain controllers to see if the generic name is included in their certificates.
For example : if you have dc1.example.com and dc2.example.com and you want to connect with example.com FQDN then both of the server needs to have example.com in their certificate SAN field.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
「URL を確認して、やり直してください (Check the URL and try again)」- vCenter 7.0 VAMI の [アップデート] パネル (78906)

KB
•
VMware Intelligent Hub 20.04 for iOS リリースのお知らせ (78889)

KB
•
将 Cloud Director 9.5 迁移到 10.0 的过程中，出现“无法读取或写入配置文件: 密钥库已被篡改，或密码不正确”错误 (78924)

KB
•
将事件从 vRealize Log Insight 导出到 NFS 失败，并显示 "无法添加新的导出任务。错误：NFS 路径语法无效 " (78902)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director for Service Provider

VMware Cloud Director

Related Versions:

VMware Cloud Director for Service Provider 9.x

Take Our Survey

Support Assistant