Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade
Joe, Mark, et al Thanks for your input. I'll confirm the AREA plugin is being loaded and see if there are indicators for errors. -- Shyam From: Joe D'Souza To: arslist@ARSLIST.ORG Sent: Wed, April 21, 2010 10:02:18 AM Subject: Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade ** Shyam, That's the same thing I would ask that Mark did. It appears as though the AREA plugin is not being called at all in the logs if that is all you see in your plugin log file. Joe -Original Message- >From: Action Request System > discussion list(ARSList) [mailto:arsl...@arslist.org]on Behalf Of > Walters, Mark >Sent: Wednesday, April 21, 2010 10:21 > AM >To: arslist@ARSLIST.ORG >Subject: Re: AREA LDAP issue > after upgrading to AR Server 7.1.0 Patch 9 upgrade > >** > > > >Are > there any entries from the AREA plugin at all? Are you sure it’s being > loaded? > >Mark > >From:Action > Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On > Behalf Of Shyam Attavar >Sent: 21 April 2010 15:19 >To: > arslist@ARSLIST.ORG >Subject: Re: AREA LDAP issue after upgrading to > AR Server 7.1.0 Patch 9 upgrade > >** >I have set the log > level to Finest for plugin logs and I only see the following entries... I > don't see any failures in the log. > > 56671136>ARDBC > /* Wed Apr 21 > 2010 06:59:12.9027 */+GLEWF > ARDBCGetListEntryWithFields -- vendor > REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin > Setttings > >/* > Wed Apr 21 2010 06:59:12.9027 > */-GLEWF > OK > ARDBC > /* Wed Apr 21 > 2010 06:59:12.9030 */+CT > ARDBCCommitTransaction > -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION > 56671136>ARDBC > /* Wed Apr 21 > 2010 06:59:12.9030 > */-CT > OK > ARDBC > /* Wed Apr 21 > 2010 06:59:13.0009 */+GLEWF > ARDBCGetListEntryWithFields -- vendor > REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin > Setttings > >/* > Wed Apr 21 2010 06:59:13.0010 > */-GLEWF > OK > ARDBC > /* Wed Apr 21 > 2010 06:59:13.0027 */+CT > ARDBCCommitTransaction > -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION > 56671136>ARDBC > /* Wed Apr 21 > 2010 06:59:13.0028 > */-CT > OK > >I do see the > following in aruser.log: > > LOGIN > FAILED loginid (password) > >I also see the > following in arapi.log during log-in time: > > 0089148320>Fast > > > > /* Wed Apr 21 2010 07:15:11.5996 */+GSIARGetServerInfo > -- as user 436557 from Remedy User (protocol 13) at IP address > ipaddress > > 390620 > > > /* Wed Apr 21 2010 07:15:11.6036 > */-GSI > FAIL > >But nothing in any > of the logs indicate what could be causing the authentication > failure. > >Any other configurations to > check? > >Thanks, >-- >Shyam > >From:Joe D'Souza > >To: arslist@ARSLIST.ORG >Sent: > Tue, April 20, 2010 6:31:17 PM >Subject: Re: AREA LDAP issue after > upgrading to AR Server 7.1.0 Patch 9 upgrade > >** >Shyam, > >Enable the > plugin log and set it to Fine and see what you get when you are trying to > authenticate using the plugin.. > >Joe >-Original >>Message- >>From: Action Request System discussion list(ARSList) >>[mailto:arsl...@arslist.org]on Behalf Of Shyam >>Attavar >>Sent: Tuesday, April 20, 2010 7:49 PM >>To: >>arslist@ARSLIST.ORG >>Subject: AREA LDAP issue after upgrading to AR >>Server 7.1.0 Patch 9 upgrade >>** >>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_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"
Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade
Shyam,
That's the same thing I would ask that Mark did. It appears as though the
AREA plugin is not being called at all in the logs if that is all you see in
your plugin log file.
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org]on Behalf Of Walters, Mark
Sent: Wednesday, April 21, 2010 10:21 AM
To: arslist@ARSLIST.ORG
Subject: Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9
upgrade
**
Are there any entries from the AREA plugin at all? Are you sure it's
being loaded?
Mark
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Shyam Attavar
Sent: 21 April 2010 15:19
To: arslist@ARSLIST.ORG
Subject: Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9
upgrade
**
I have set the log level to Finest for plugin logs and I only see the
following entries... I don't see any failures in the log.
/* Wed Apr 21 2010 06:59:12.9027 */+GLEWF
ARDBCGetListEntryWithFields -- vendor
REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin Setttings
/* Wed Apr 21 2010 06:59:12.9027 */-GLEWF
OK
/* Wed Apr 21 2010 06:59:12.9030 */+CT
ARDBCCommitTransaction -- vendor
REMEDY.ARDBC.SERVER.ADMINISTRATION
/* Wed Apr 21 2010 06:59:12.9030 */-CT
OK
/* Wed Apr 21 2010 06:59:13.0009 */+GLEWF
ARDBCGetListEntryWithFields -- vendor
REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin Setttings
/* Wed Apr 21 2010 06:59:13.0010 */-GLEWF
OK
/* Wed Apr 21 2010 06:59:13.0027 */+CT
ARDBCCommitTransaction -- vendor
REMEDY.ARDBC.SERVER.ADMINISTRATION
/* Wed Apr 21 2010 06:59:13.0028 */-CT
OK
I do see the following in aruser.log:
LOGIN FAILED loginid (password)
I also see the following in arapi.log during log-in time:
/* Wed Apr 21 2010 07:15:11.5996 */+GSIARGetServerInfo -- as user
436557 from Remedy User (protocol 13) at IP address ipaddress
/* Wed Apr 21 2010 07:15:11.6036 */-GSI FAIL
But nothing in any of the logs indicate what could be causing the
authentication failure.
Any other configurations to check?
Thanks,
--
Shyam
--
From: Joe D'Souza
To: arslist@ARSLIST.ORG
Sent: Tue, April 20, 2010 6:31:17 PM
Subject: Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9
upgrade
**
Shyam,
Enable the plugin log and set it to Fine and see what you get when you are
trying to authenticate using the plugin..
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org]on Behalf Of Shyam Attavar
Sent: Tuesday, April 20, 2010 7:49 PM
To: arslist@ARSLIST.ORG
Subject: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9
upgrade
**
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 at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
Re: {Remedy ARS} AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade
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 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"
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 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"
Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade
Are there any entries from the AREA plugin at all? Are you sure it's being loaded? Mark From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Shyam Attavar Sent: 21 April 2010 15:19 To: arslist@ARSLIST.ORG Subject: Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade ** I have set the log level to Finest for plugin logs and I only see the following entries... I don't see any failures in the log. /* Wed Apr 21 2010 06:59:12.9027 */+GLEWF ARDBCGetListEntryWithFields -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin Setttings /* Wed Apr 21 2010 06:59:12.9027 */-GLEWF OK /* Wed Apr 21 2010 06:59:12.9030 */+CTARDBCCommitTransaction -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION /* Wed Apr 21 2010 06:59:12.9030 */-CT OK /* Wed Apr 21 2010 06:59:13.0009 */+GLEWF ARDBCGetListEntryWithFields -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin Setttings /* Wed Apr 21 2010 06:59:13.0010 */-GLEWF OK /* Wed Apr 21 2010 06:59:13.0027 */+CTARDBCCommitTransaction -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION /* Wed Apr 21 2010 06:59:13.0028 */-CT OK I do see the following in aruser.log: LOGIN FAILED loginid (password) I also see the following in arapi.log during log-in time: /* Wed Apr 21 2010 07:15:11.5996 */+GSIARGetServerInfo -- as user 436557 from Remedy User (protocol 13) at IP address ipaddress /* Wed Apr 21 2010 07:15:11.6036 */-GSI FAIL But nothing in any of the logs indicate what could be causing the authentication failure. Any other configurations to check? Thanks, -- Shyam From: Joe D'Souza To: arslist@ARSLIST.ORG Sent: Tue, April 20, 2010 6:31:17 PM Subject: Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade ** Shyam, Enable the plugin log and set it to Fine and see what you get when you are trying to authenticate using the plugin.. Joe -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org]on Behalf Of Shyam Attavar Sent: Tuesday, April 20, 2010 7:49 PM To: arslist@ARSLIST.ORG Subject: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade ** 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 _attend WWRUG10 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _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"
Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade
I have set the log level to Finest for plugin logs and I only see the following entries... I don't see any failures in the log. /* Wed Apr 21 2010 06:59:12.9027 */+GLEWF ARDBCGetListEntryWithFields -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin Setttings /* Wed Apr 21 2010 06:59:12.9027 */-GLEWF OK /* Wed Apr 21 2010 06:59:12.9030 */+CTARDBCCommitTransaction -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION /* Wed Apr 21 2010 06:59:12.9030 */-CT OK /* Wed Apr 21 2010 06:59:13.0009 */+GLEWF ARDBCGetListEntryWithFields -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin Setttings /* Wed Apr 21 2010 06:59:13.0010 */-GLEWF OK /* Wed Apr 21 2010 06:59:13.0027 */+CTARDBCCommitTransaction -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION /* Wed Apr 21 2010 06:59:13.0028 */-CT OK I do see the following in aruser.log: LOGIN FAILED loginid (password) I also see the following in arapi.log during log-in time: /* Wed Apr 21 2010 07:15:11.5996 */+GSIARGetServerInfo -- as user 436557 from Remedy User (protocol 13) at IP address ipaddress /* Wed Apr 21 2010 07:15:11.6036 */-GSI FAIL But nothing in any of the logs indicate what could be causing the authentication failure. Any other configurations to check? Thanks, -- Shyam From: Joe D'Souza To: arslist@ARSLIST.ORG Sent: Tue, April 20, 2010 6:31:17 PM Subject: Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade ** Shyam, Enable the plugin log and set it to Fine and see what you get when you are trying to authenticate using the plugin.. Joe -Original Message- >From: Action Request System > discussion list(ARSList) [mailto:arsl...@arslist.org]on Behalf Of Shyam > Attavar >Sent: Tuesday, April 20, 2010 7:49 PM >To: > arslist@ARSLIST.ORG >Subject: AREA LDAP issue after upgrading to AR > Server 7.1.0 Patch 9 upgrade > >** > > >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_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"
Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade
Shyam, Enable the plugin log and set it to Fine and see what you get when you are trying to authenticate using the plugin.. Joe -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org]on Behalf Of Shyam Attavar Sent: Tuesday, April 20, 2010 7:49 PM To: arslist@ARSLIST.ORG Subject: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade ** 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 at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade
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 at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
