Anonymous_User Absent Member.
Absent Member.
183 views

Problem with ancient AD driver


Hi,
Having a problem with an ancient version of IDM (can't be upgraded). For
no obvious reason the AD connector appears to have stopped connecting to
AD. The key appears to be within

DirXML: [11/06/13 15:02:13.68]: ADDriver: Connect using ldap_bind:
user=ABC, domain=, password=***, method=negotiate, server=localhost,
sign=no, seal=no ssl=yes
DirXML: [11/06/13 15:02:15.78]: Loader: Received document from
publicationShim
DirXML: [11/06/13 15:02:15.78]: Loader: XML Document:
DirXML: [11/06/13 15:02:15.78]: <nds ndsversion="8.7" dtdversion="1.1">
<source>
<product version="3.1.1" asn1id="" build="20060706_164400"
instance="\CWN\CWN\VCH\Resource\NIDMDriverSet\ADCWNADDriver">AD</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<status level="retry" type="driver-general">
<message>unable to connect to Active Directory</message>
<ldap-err ldap-rc="81" ldap-rc-name="LDAP_SERVER_DOWN">
<client-err ldap-rc="81" ldap-rc-name="LDAP_SERVER_DOWN">Server
Down</client-err>
</ldap-err>
</status>
</input>
</nds>
DirXML: [11/06/13 15:02:15.78]: Loader: Received 'publisher reply'
document
DirXML: [11/06/13 15:02:15.78]: Loader: XML Document:
DirXML: [11/06/13 15:02:15.78]: <nds dtdversion="3.0" ndsversion="8.x">
<source>
<product version="3.0.0.20051118 ">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<output>
<status event-id="0" level="success"></status>
</output>
</nds>

but its somewhat cryptic. LDAP is certainly running so I suspect a
problem with the user id it's connecting with but thats a guess and I
don't want to start resetting passwords etc without knowing what the
issue is first.

Pete


--
peteh
------------------------------------------------------------------------
peteh's Profile: https://forums.netiq.com/member.php?userid=6246
View this thread: https://forums.netiq.com/showthread.php?t=49167

Labels (1)
0 Likes
1 Reply
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: Problem with ancient AD driver

peteh wrote:

>
> Hi,
> Having a problem with an ancient version of IDM (can't be upgraded).
> For no obvious reason the AD connector appears to have stopped
> connecting to AD. The key appears to be within
>
> DirXML: [11/06/13 15:02:13.68]: ADDriver: Connect using ldap_bind:
> user=ABC, domain=, password=***, method=negotiate, server=localhost,
> sign=no, seal=no ssl=yes


Your configuration specifies that you should bind to AD via SSL,
however I suspect that the SSL certificate used has expired or is
invalid for some other reason. This prevents the bind from succeeding

Do you really need to bind using SSL? If your Remote Loader runs on
your domain controller you shouldn't need to use SSL.

I'd suggest you turn off SSL in the driver configuration and see if
that helps.


--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.