Hello Onkar, If you are able to make the connection using port 389, then making the modifications to your connection should not be that difficult.
I never had much luck using the LDP LDAP browser. We had the most success using Softerra LDAP Browser 4.5 (http://www.ldapadministrator.com/download.htm if you want to try that and click on LDAP Browser 4.5 as LDAP Administrator 2014.1 is a paid software). It is a much more robust LDAP browser. LDP kept telling me it had authentication failures. However, when I configured Softera LDAP Browser, it was able to connect to the SSL connection without issues. You might try that instead to make your connection and ensure you can connect properly. Prior to configuring anything inside Remedy, I would ensure you have proper connection to the LDAP server first. Then, you can move from there.\ You might need to use the fully qualified DN, such as cn=username,ou=my group,dc=mycomany,dc=com, for the username parameter. I hope this helps you in some way, Kevin Eldridge From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of onkar shinde Sent: Monday, December 22, 2014 6:54 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: Getting plugin LDAP error 12 while integrating a LDAP server ** Hi Kelvin, Yes, I have also configured the AREA LDAP configuration, but in my case AREA is also not working. During AREA logging in by LDAP user, I get following error 05:19:47,492 ERROR [pool-4-thread-14] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <AREA.LDAP>Ldap Authentication failed!javax.naming.InvalidNameException: [LDAP: error code 34 - Invalid DN] Also through Pentaho client I am able to pull all People data without any issues, by providing the same LDAP user inputs. Is there any settings or pre-requirement to configure these 2 plugins from Remedy side. Because I choose simple method to connect to LDAP server through LDP exe utility. Otherwise it couldn't connect. I need to also provide whole DN, as username like uid=<userid>,ou=<>,dc=<clients name of domain>,dc=com Anyone has faced this issue please advise. Thanks. On Tue, Dec 16, 2014 at 9:24 PM, Kevin Eldridge <kevin.eldri...@itsmuniversity.net<mailto:kevin.eldri...@itsmuniversity.net>> wrote: ** Hello Oscar, I forgot to mention that we had to enable the AREA LDAP Configuration to get this to work properly. I was unable to access the ARDBC from Dev Studio until after I did this. I copied most of the settings from the ARDBC configuration information to set this up. Once I did this, saved the settings in AR Server, and restarted AR Services, I was able to access the ARSYS.ARDBC.LDAP from the New Vendor Form. Hopefully, this helps you, Kevin Eldridge _ARSlist: "Where the Answers Are" and have been for 20 years_ -- Regards, Onkar Shinde Senior Software Engineer Vyom Labs Pvt. Ltd. BSM Solutions & Services || ITIL Consulting & Training Telephone: +91-20-6632-1000 Mobile: +91-7709008719 Email: onkar.shi...@vyomlabs.com<mailto:onkar.shi...@vyomlabs.com> Web: www.vyomlabs.com<http://www.vyomlabs.com> _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
