<div dir="ltr">I reimaged & registered a XO-1.75 and a XO-4 with 13.2.0 to a XS-0.7 schoolserver. Afterwards I opened Browse, and was able to open <a href="http://schoolserver/" target="_blank">http://schoolserver/</a> to login to Moodle without problems.<br>
<br>This does not mean that there is not a bug with 13.2.0, XS, and/or XSCE; but one thing you could try is to fully stop and restart the Browse activity after registering if the first login attempt does not work. Sometimes I have found this helps.<br>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 6, 2013 at 11:14 AM, Gonzalo Odiard <span dir="ltr"><<a href="mailto:gonzalo@laptop.org" target="_blank">gonzalo@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I don't have a school server to try.<div>You should fill a ticket on <a href="http://bugs.sugarlabs.org" target="_blank">bugs.sugarlabs.org</a></div>
<div>cced: Manuel Quiñones, who maintain Browse activity.</div><span><font color="#888888"><div><br>
</div><div>Gonzalo</div></font></span></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 6, 2013 at 12:08 PM, Jerry Vonau <span dir="ltr"><<a href="mailto:jerry@laptop.org.au" target="_blank">jerry@laptop.org.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Think it's more of a question of looking for confirmation. Is anybody else seeing this behavior on 13.2.0-13 on XO-1s when used with any version of school-servers? I'm at a loss trying to explain why this is occurring to Anna. With the noted behavior where would you file the bug report? OLPC is what I'm thinking but looking if someone else might be impacted also or can confirm this.<span><font color="#888888"><br>
<br>Jerry</font></span><div><div><br><br><div class="gmail_quote">On 6 August 2013 05:12, Gonzalo Odiard <span dir="ltr"><<a href="mailto:gonzalo@laptop.org" target="_blank">gonzalo@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">There are a ticket filled?<div><br></div><div>Gonzalo</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Tue, Aug 6, 2013 at 4:27 AM, Jerry Vonau <span dir="ltr"><<a href="mailto:jerry@laptop.org.au" target="_blank">jerry@laptop.org.au</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Great piece of deductive testing Anna, way to go. Forwarding for further investigation.<br>
<br>Jerry<br><br><div class="gmail_quote">
---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Anna</b> <span dir="ltr"><<a href="mailto:aschoolf@gmail.com" target="_blank">aschoolf@gmail.com</a>></span><br>
Date: 5 August 2013 15:02<br>Subject: [XSCE] Re: Client side Moodle transparent auth broken in 13.2.0 stable<br>To: xsce-devel <<a href="mailto:xsce-devel@googlegroups.com" target="_blank">xsce-devel@googlegroups.com</a>><br>
<br><br>
<div dir="ltr">I just realized that someone will probably ask what's the most recent build where Moodle transparent auth did work. Lucky for me, I just had to test one older. Moodle transparent auth DOES work in 13.2.0-12.<div>
<br></div><div>So whatever broke client side Moodle transparent auth should be confined to 13.2.0-13.</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 5, 2013 at 2:19 PM, Anna <span dir="ltr"><<a href="mailto:aschoolf@gmail.com" target="_blank">aschoolf@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I very recently upgraded my little herd of XOs to the latest stable build 13.2.0-13. Unfortunately, something in that build has broken Moodle's transparent authentication. When a registered client goes to <a href="http://schoolserver/moodle" target="_blank">http://schoolserver/moodle</a>, all it gets is the login page.</div>
<div><br></div><div>Now, that's not unheard of, you can usually just click the "Home" button and get automatically logged in. But when I've seen that before, the XO's SN is filled out in the Username field on the login page. The 13.2.0-13 XO doesn't show that. No matter what you click on in the Moodle login page, it never logs in.</div>
<div><br></div><div>To verify it was a client side issue, I flashed an XO-1 with 13.1.0 stable, and registered first to be admin. I also registered a 13.2.0-13 as the second client. On the 13.1.0, I can go to the Moodle homepage and it automatically logged me in. I tried again to access the Moodle homepage on the 13.2.0-13 XO-1, but yep, still just got the login page. On the admin XO, I went to Site Administration -> Users -> Accounts -> Browse list of users and saw both XOs listed. It indicated that the 13.2.0-13 client had never logged in.</div>
<div><br></div><div>So, the user account is being created on the server for the 13.2.0-13 XO upon registration, but client side transparent authentication is not working.</div><div><br></div><div>To verify the 13.2.0-13 XO's Browse Activity is accepting cookies, I went to <a href="http://www.bu.edu/htbin/computing/browsers/troubleshooting/cookietest.pl" target="_blank">http://www.bu.edu/htbin/computing/browsers/troubleshooting/cookietest.pl</a> and the test was successful.</div>
<div><br></div><div>Now, I have successfully tested Moodle transparent auth with previous iterations of 13.2.0, perhaps 8 or 9? So whatever change on 13.2.0 that broke transparent auth must have been relatively recent.</div>
<div><br></div><div>I took a look at the Browse Activity version between the two clients:</div><div>13.1.0 = Browse 149</div><div>13.2.0-13 = Browse 149.3</div><div><br></div><div>I knew it wouldn't make a difference, but I also tested the 13.2.0-13 as first registration and it doesn't care that its the admin user. And also tested with a fresh flash to make sure there wasn't something sticky in there from a previous registration gumming things up.</div>
<div><br></div><div>I've tested this with the XSCE installed a couple days ago (xs-config-0.8.4.123.gda5e8e3-1) and the latest DXS from this morning. I also remembered I have an XS 0.6 (duh, Anna) and the results were the same. I don't have an XS 0.7 installation, but I would expect the same results.</div>
<div><br></div><div>Since this is a client side issue, I'm not sure where to go from here as far as troubleshooting.</div><span><font color="#888888"><div><br></div><div>Anna </div></font></span></div>
</blockquote></div><br></div>
</div></div></div><br>
<br></div></div>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org" target="_blank">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
<br></blockquote></div><br></div></div>