I have had weird problems with authentication in the past, and a restart 'fixed' the issue for awhile....I was then able to capture that the plugin was running out of memory, corrupting the in-memory config, requiring a restart.
On Tue, Aug 20, 2013 at 7:30 AM, Karthik <karthik...@gmail.com> wrote: > ** > Team, > > we had configured AREA authentication via SSL a few months back. Suddenly, > since yesterday it has stopped working with below error in the arplugin.log > > +VL AREAVerifyLoginCallback -- user remedy_ldap -- vendor > ARSYS.AREA.HUB (D:\Program Files\BMC > Software\ARSystem\arealdap\areahub.dll) > <ARSYS.AREA.LDAP> <FINEST> AREAVerifyLoginCallback > <ARSYS.AREA.LDAP> <FINER> Connecting via SSL(host=<ad_host_name, port=636, > certPath=C:\certificate\ldaptruststore.jks with Server SSL Authentication > enabled) > <ARSYS.AREA.LDAP> <SEVERE> init: Bad parameter to an ldap routine (LDAPERR > Code 89) > <ARSYS.AREA.LDAP> <SEVERE> init: ldapssl_client_init failed [cert path > C:\certificate\ldaptruststore.jks] > <ARSYS.AREA.LDAP> <SEVERE> Failed to initialize the ldap sdk > -VL FAIL > > user remedy_ldap is the bind user we have configured. > > Weird thing is, it works on ARDBC via LDAP with the same bind user and > certificates, however throws error for AREA. Any ideas? > > we checked and it seems nothing changed on AD. > > -- > - Karthik > _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"
