Shyam, Go to your armonitor.cfg file (assuming windows) and make sure your entries for arplugin.exe are correct. When I upgraded from 7.1P2 --> 7.1P7, 2 of my plugin entries were "chopped off". You should be able to compare your Dev and your Prod environments.
I use 3 plugins because I have 3 directories I authenticate users to.. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of remedy lee Sent: Wednesday, April 21, 2010 9:24 AM To: arslist@ARSLIST.ORG Subject: Re: {Remedy ARS} AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade I had an ldap issue with an update to 7.1 patch 3 long ago. It was a little different. I could authenticate with the first ldap in the config but the rest wouldn't work. So not sure if this will help. ===================================================== Found out a little bit of information, well confirmed it actually, concerning the information on page 174 of the Integration Guide. What this means is that you can only have one plugin dll in the ar.cfg file. What I see in your ar.cfg file is this: Plugin: arealdap.dll and Plugin: areahub.dll Since the arealdap.dll is listed first in the ar.cfg file, that is the plugin being used. Please comment out or remove the Plugin: arealdap.dll line that exists at the top of the ar.cfg file, then restart ARServer and test. What I also confirmed was that when using the AREA Hub dll, if a user authentication call fails for any reason, it should still failover to the next LDAP server in the AREALDAP Configuration form list, until it authenticates the user or exhausts the list of directory servers. Let me know if this information helps to resolve the issue. On Apr 20, 7:48 pm, Shyam Attavar <atta...@sbcglobal.net> wrote: > Dear Listers, > > We upgraded our test environment from AR Server 7.1.0 Patch 006 to Patch 009. > As part of the upgrade we upgraded the AREA LDAP plugin as well. After the > upgrade, we are unable to authenticate against LDAP. We can login to the > system by setting a local password in the user form. I have reconfigured the > AREA LDAP entries from the AR System Administration Console, but unable to > resolve the issue. > > Anyone else seen this issue after upgrading to AR Server 7.1.0 Patch 009? if > so, how were you able to resolve the issue? > > Environment: > AR Server on RHEL > Oracle 10gR4 on RHEL > > Thanks in advance, > -- > Shyam > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug10www.wwrug.comARSlist: "Where the Answers Are" > > -- > You received this message because you are subscribed to the Google Groups > "Remedy ARS" group. > To post to this group, send email to arsl...@googlegroups.com. > To unsubscribe from this group, send email to > arslist+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/arslist?hl=en. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
