I just rebuilt a 7.0.01.001 AR Server from scratch - this time with
32-bit instead of 64-bit Win2K3 just in case that was the problem with
SSL and several other application functions.  I still get server crashes
when I try to login via AREA with the AREA configuration set to use SSL
certificates. It works fine if I don't use SSL, or if I use SSL by
setting up a local host connection with sTunnel.

There never has been a line in my ar.cfg that reads:
   Plugin: arealdap.dll
There is a line for each of the four connections I have defined that
reads:
   AREA-Hub-Plugin: arealdap.dll
As well as a single line that reads:
   Plugin: areahub.dll

Christopher Strauss, Ph.D.
Remedy Database Administrator
University of North Texas Computing Center
http://remedy.unt.edu/helpdesk/
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of harrylee
Sent: Monday, March 12, 2007 1:26 PM
To: arslist@ARSLIST.ORG
Subject: Re: [9295] LDAP issue with 7.0.1 Patch 1?

This has been resolved.

The issue was that in the ar.cfg file there was a line that interfered
with the LDAP plugin.
Plugin: arealdap.dll
Plugin: areahub.dll

The first line was interfering with the multiLDAP check.
Once arealdap.dll was removed, things were working as normal.



strauss wrote:
> 
> Our issue was that on 7.0.1 and 7.0.1.001 the SSL certificate function

> of AREA that had been working in 7.0 stopped working. It is still 
> broken.
> 
> Christopher Strauss, Ph.D.
> Remedy Database Administrator
> University of North Texas Computing Center 
> http://remedy.unt.edu/helpdesk/ -----Original Message-----
> From: Action Request System discussion list(ARSList) 
> [mailto:[EMAIL PROTECTED] On Behalf Of harrylee
> Sent: Wednesday, March 07, 2007 2:40 PM
> To: arslist@ARSLIST.ORG
> Subject: LDAP issue with 7.0.1 Patch 1?
> 
> Hi,
> 
> Does anyone have an issue with their AREA LDAP authenication after 
> patching to patch 1 for ARsystem 7.0.1?
> My place here as 2 LDAPs we authenticate to.  One Edirectory and an 
> Active Directory.
> ED is the first place Remedy checks then it is AD.
> However, since the patch it seems that Remedy can't/won't check AD 
> which is the 2nd place to check.
> I redid the Area LDAP config and still not working.
> 
> Anyone else encountering this?
> 
> --
> View this message in context:
> http://www.nabble.com/LDAP-issue-with-7.0.1-Patch-1--tf3364778.html#a9
> 36
> 1630
> Sent from the ARS (Action Request System) mailing list archive at 
> Nabble.com.
> 
> ______________________________________________________________________
> __
> _______
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
> ARSlist:"Where the Answers Are"
> 
> ______________________________________________________________________
> _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
> ARSlist:"Where the Answers Are"
> 
> 

--
View this message in context:
http://www.nabble.com/LDAP-issue-with-7.0.1-Patch-1--tf3364778.html#a944
0234
Sent from the ARS (Action Request System) mailing list archive at
Nabble.com.

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to