Error while starting ID Provider Driver

[shajipappan]

Hi Guys,

I have installed and deployed ID Provider driver into the IDV. But after that when i am trying to start the driver, the driver gets started but soon after it gets shutdown.
The error which i am getting in the log is : "LDAP: error code 49 - NDS error: failed authentication (-669)". Error is showing as "Error initializing ID Server"
I have given the correct IP, username and Password of my e-directory(LDAP) server. But still i am facing this issue.
Can anyone help me in this issue?

[aburgemeister]

As always, please post the trace, in this case the startup trace, at level
three (3) or higher so we can see what actually happens and when.

LDAP 49 means either your username or password is wrong when binding via
LDAP, so while you believe it is correct in reality it is not according to
the computer, but at least your IP is probably correct (unless you are
accidentally pointing to the wrong LDAP environment, which would likely
have different credentials causing this error).

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

[al_b]

shajipappan;2481003 wrote:
Hi Guys,

I have installed and deployed ID Provider driver into the IDV. But after that when i am trying to start the driver, the driver gets started but soon after it gets shutdown.
The error which i am getting in the log is : "LDAP: error code 49 - NDS error: failed authentication (-669)". Error is showing as "Error initializing ID Server"
I have given the correct IP, username and Password of my e-directory(LDAP) server. But still i am facing this issue.
Can anyone help me in this issue?

Hi shajipappan,
Please confirm, that you able to login to the same LDAP server (ip/port) with same username and password from external LDAP client.
Some "undocumented" feature: better do not use in LDAP password "_" and "$".
Are you use LDAP or LDAPS connectivity? (port 389 or 636)

Post the trace here (level 3+).
It will provide information, that will be able to help troubleshoot your issue.

By the way, you can enable DirXML and LDAP trace and use it together.

[lhaeger]

shajipappan wrote:

> I have given the correct IP, username and Password of my
> e-directory(LDAP) server. But still i am facing this issue.

That's quite unlikely, give the unambiguous error message... 🙂

> Can anyone help me in this issue?

Enable LDAP tracing on the server and see what really happens when you start
the driver.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)

[shajipappan]

The issue is resolved now. The issue was with the username DN and also with the policy container DN.
For policy container in Driver configuration,instead of "CN=id-policies,OU=ID-Provider,OU=Driver_Set,OU=IDM,OU=Services,OU=Vale" i used the DN ""CN=id-policies,CN=ID-Provider,CN=Driver_Set,OU=IDM,OU=Services,OU=Vale".
After this the driver was started and the policies were initialized upon starting.
Thank you guys for your support

[geoffc]

On 5/17/2018 7:04 AM, shajipappan wrote:
>
> The issue is resolved now. The issue was with the username DN and also
> with the policy container DN.
> For policy container in Driver configuration,instead of
> "CN=id-policies,OU=ID-Provider,OU=Driver_Set,OU=IDM,OU=Services,OU=Vale"
> i used the DN
> ""CN=id-policies,CN=ID-Provider,CN=Driver_Set,OU=IDM,OU=Services,OU=Vale".
> After this the driver was started and the policies were initialized upon
> starting.
> Thank you guys for your support

It is appreciated when you come back and report what fixed the issue.
Thank you.