[ww-devel] The library browser not updating problem

[John Jones]

I recall seeing a problem like this in the past.  In that case, the ssl did
not have a signed certificate.  Some web browsers would alert you the first
time you connect to the site, and once you say ok, they remember that the
certificate has been accepted.

Do you have an official signed certificate, or is it home made?

John



On Tue, Aug 26, 2014 at 2:49 PM, Jason Aubrey <aubreyja at gmail.com> wrote:

> Well, at this point I think the error has something to do with how my ssl
> is configured.  Here is some evidence from my apache log with LogLevel info:
>
> There were a lot of errors: 500 Can't connect to
> webwork.math.arizona.edu:443 at
> /opt/webwork/webwork2/lib/WebworkClient.pm line 158
>
> [Tue Aug 26 14:35:13 2014] [info] [client 127.0.0.1] SSL library error 1
> in handshake (server webwork.math.arizona.edu:443)
> [Tue Aug 26 14:35:13 2014] [info] SSL Library Error: 336151576
> error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca
> [Tue Aug 26 14:35:13 2014] [info] [client 127.0.0.1] Connection closed to
> child 0 with abortive shutdown (server webwork.math.arizona.edu:443)
>
> So, you can see (1) that 'it' can't connect to
> webwork.math.arizona.edu:443 and (2) the ssl handshake seems to be dying
> due to an unknown certificate authority.  But if you looked at my server,
> you would see (3) that my certificate authority is in fact well known:
>
>> Issued By
>>
> Common Name (CN) InCommon Server CA
>>
> Organizaton (O) Internet2
>>
> etc...
>>
> Also, there is the fact that (4) my web browsers have no problem
> connecting to the https site.
> So,
> (a) Maybe the perl module(s) running the webservice calls (LWP?) don't
> recognize the certificate authority.
> (b) Maybe the way my redirect to ssl is set up is messing with the web
> service calls. (Permanent redirect to a *:443 vhost)
> (c) Maybe there is some other configuration problem with my ssl set up.
> (d) Maybe this is completely unrelated to the actual problem.
>
> Thanks for any ideas.
> Jason
>
>
> On Mon, Aug 25, 2014 at 7:21 PM, Matt Haught <matt_haught at ncsu.edu> wrote:
>
>> I had a similar problem recently. For me I was missing the
>> perl-LWP-Protocol-https package. In firebug or chrome developer tools
>> go to the net/network tab, open the library browser, pick a subject,
>> and look for a post from instructorXMLHandler. In the response tab I
>> had a nice error telling me what I was missing rather then json code.
>>
>> I also have to patch WebworkWebservice.pm so the library browser will
>> work with shibboleth auth.
>>
>> Matt Haught
>> North Carolina State University
>>
>>
>> On Mon, Aug 25, 2014 at 3:30 PM, Jason Aubrey <aubreyja at gmail.com> wrote:
>> > Hi All,
>> >
>> > A number of people have reported a problem where after an install of
>> ww2.9
>> > the library browser (2) doesn't update or display problems when the
>> subject
>> > is changed.  I'm having this problem on the ww3 branch too.  My web
>> console
>> > says
>> >
>> > SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the
>> JSON
>> > data
>> >
>> > Is there a known solution to this problem yet?
>> >
>> > Thanks,
>> > Jason
>> >
>> >
>> > _______________________________________________
>> > webwork-devel mailing list
>> > webwork-devel at webwork.maa.org
>> > http://webwork.maa.org/mailman/listinfo/webwork-devel
>> >
>> _______________________________________________
>> webwork-devel mailing list
>> webwork-devel at webwork.maa.org
>> http://webwork.maa.org/mailman/listinfo/webwork-devel
>>
>
>
> _______________________________________________
> webwork-devel mailing list
> webwork-devel at webwork.maa.org
> http://webwork.maa.org/mailman/listinfo/webwork-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://webwork.maa.org/pipermail/webwork-devel/attachments/20140826/56fe02af/attachment.html>