Please refer BMC Remedy AR System 8.1.00 online documentation.pdf page no : 480 
and further.

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Karthik
Sent: Tuesday, August 20, 2013 7:11 PM
To: [email protected]
Subject: Re: Issue with AREA plugin

**
Thanks both.

LJ,
i killed arplugin.exe and also restarted arsever before, did not help much

Kiran,
certificate is valid till end of 2020. when i list the certificates in the 
keystore, it lists the certificates. Whats the command to validate a 
certificate?

also, how does ARDBC work with the same keystore and certificates in it while 
AREA doesn't?

- Karthik

On 20 August 2013 19:05, Hullule, Kiran 
<[email protected]<mailto:[email protected]>> wrote:
**
Your Java Key Store (path C:\certificate\ldaptruststore.jks) certificate is no 
longer valid or available. Please use java keytool to check the validity of 
this certificate file,.

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]<mailto:[email protected]>] On Behalf Of Karthik
Sent: Tuesday, August 20, 2013 7:01 PM
To: [email protected]<mailto:[email protected]>
Subject: Issue with AREA plugin

**
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_
_ARSlist: "Where the Answers Are" and have been for 20 years_



--
- 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"

Reply via email to