[OPEN-ILS-DEV] Can't connect with client

[Bill Erickson]

On 3/18/07, Bill Ott <bott at grpl.org> wrote:
>
> Don McMorris wrote:
> > How do the logs look? Any changes there?
>
> Tons of data in the osrfsys.log, lots of new cstore debug messages on
> startup, but no errors.  Here is the run of the osrfsys.log during a
> client login attempt.  I only see INFO and DEBG messages, but hopefully
> there will be something telling in the mix.


[snip]

The login process is a two-part, CHAP-style authentication.  The first step
is to request a challenge key from the server.  The second step is to send
the challenge response to the server.

The two methods that do this are "open-ils.auth.authenticate.init" and "
open-ils.auth.authenticate.complete".

The chunk of logs provided shows a successful call to the the first method,
open-ils.auth.authenticate.init.

Here is a small chunk that shows the server responding to the client with
the challenge key:

osrfMessage--*/{"threadTrace": "1","type":"RESULT","payload":/*--S
osrfResult--*/{"status":"OK","statusCode":"200","content":"083585426204e5cbca49f671a296c4c0"}/*--E
osrfResult--*/}/*--E osrfMessage--*/,/*--S
osrfMessage--*/{"threadTrace":"1","type":"STATUS","payload":/*--S
osrfConnectStatus--*/{"status":"Request
Complete","statusCode":"205"}/*--E osrfConnectStatus--*/}/*--E
osrfMessage--*/]


After this, there should be an additional pile of logs detailing the "
open-ils.auth.authenticate.complete" method call.  That's where things are
failing.

For the sake of clarity, you may wish to direct the chopchop logs to a
different file, since chopchop probably isn't the problem and it has verbose
logs.


-bill


-- 
Bill Erickson
PINES Systems Developer
Georgia Public Library Service
billserickson at gmail.com
http://open-ils.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.georgialibraries.org/pipermail/open-ils-dev/attachments/20070318/d81488f4/attachment-0001.html