After Changing OVD 11g LDAP Adapter Ping Protocol from LDAP Back to TCP in ODSM, the Adapter no Longer Shows in ODSM and Log Shows: Error Parsing at line #0: 0.[[ org.xml.sax.SAXParseException: XML-24534: (Error) Element 'pingbindpass' not expected.
Last updated on MARCH 08, 2017
Applies to:Oracle Virtual Directory - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Oracle Virtual Directory (OVD) 11g 188.8.131.52.0 with Oracle Directory Services Manager (ODSM).
Initially set an OVD LDAP adapter with Ping Protocol Setting of LDAP (with credentials) in ODSM and verified it works.
After later changing it back to TCP protocol in ODSM and saving the adapter, plus restarting the processes, the following exception occurs in the wls_ods1-diagnostic.log:
[2015-02-17T19:46:15.086+00:00] [wls_ods1] [ERROR] [OVD-60373] [com.octetstring.vde.config.parsers.ConfigErrorHandler] [tid: SyncProfileMBean] [userId: <anonymous>] [ecid: b12d073c59230935:-72683975:14b98eb32e8:-8000-0000000000000632,0] [APP: odsm#184.108.40.206.0] [DSID: 0000KiOyFKz5i^YVLqATOA1Kst0h000003] Error Parsing at line #0: 0.[[
org.xml.sax.SAXParseException: XML-24534: (Error) Element 'pingbindpass' not expected.
In addition, the LDAP adapter is no longer visible in any ODSM Adapters or Home tabs, though it is still in the adapters.os_xml file and the Data Browser > Client View namespace entry for it still works/expands.
There is no occurence of "pingbindpass" in the adapters.os_xml, which is expected since the protocol was switched back to the TCP default protocol. Also no occurrence of "pingbindpass" can be found in any file in the FMW home.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms