I wrote:
As an aside I got the auth/index.php working, returning the correct credentials in the xml after a single successful login on the chromebook. The chromebook client still insists upon demanding a password on every refresh of the calendar even though the password and username are correct in auth/index.php :/ .
On 10. nov. 2014 18:09, Ján Máté replied: This cannot be caused by the auth module itself. If your setup works without the auth module and you set exactly the same values in the auth module config (as you used in config.js) it MUST work. The XML from the auth module is appended to the globalAccountSettings only once after the login - then the client use the globalAccountSettings (the auth module is never requested again during the "session").
Bug in Chrome OS browser I suspect. Google Chrome Beta on linux is less fussy, so we'll just have to wait for an update to Chrome OS I believe (or switch the chromebook to linux, taking on a whole new support responsibility on that thing ... )