7.6.04 ITSM on Windows & SQL Server

I'm trying to configure AREA authentication. I have everything configured
enough to make an authentication attempt and the attempt naturally fails.

I do not have a POC at the LDAP server to check my test user's account or
to check logging on the LDAP end.

At this point, I'm not even sure I'm reaching LDAP, successfully binding
and/or hitting the test user's LDAP account.

With plugin logging on and set to "ALL", I get about 730 lines of logging
when I attempt to login with a test user.

Out of those 730 lines of logging, I only get the following two lines that
mention AREA or my user:

<PLGN> <TID: 005436> <RPC ID: 0000000086> <Queue: AREA      > <Client-RPC:
390695> /* Wed Dec 21 2011 18:14:13.9300 */+VL    AREAVerifyLoginCallback
       -- user TRAIN19
<PLGN> <TID: 005436> <RPC ID: 0000000086> <Queue: AREA      > <Client-RPC:
390695> /* Wed Dec 21 2011 18:14:13.9300 */-VL
   FAIL


This is like troubleshooting via braille method. Is there another AREA/LDAP
log or some way to log the bind and auth attempt on the REMEDY side?

I've checked ARSList archives and the BMC KB's and can't find anything that
I haven't already tried. I do see some really nice log examples (Knowledge
Article ID: KA334262) that I *WISH* I could capture on the Remedy Side. I
think they would tell me what I need to know to get this working. For now,
all I can find is those two measly log lines above.

Any suggestions on how to get AREA logging much more verbose on the *REMEDY
SIDE*?

Thanks in advance!
JDHood

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

Reply via email to