On Jun 22, 2016 19:12, "Volker Braun" <vbraun.n...@gmail.com> wrote: > > The authentication changed, we used to have http digest (browser popup window, with realm) and now its the trac builtin one. This breaks the git-trac script as it tries to authenticate over http digest. I can fix it up but first let me ask: Is that going to stay?
This was a requested feature. I did worry that it could break any script that was relying on HTTP authentication but nobody indicated as much. It should be possible to login over xmlrpc or by posting to /login and storing the resulting session cookie. Conceivably it would not be hard to provide an alternative HTTP digest backend for login as well. > On Monday, June 20, 2016 at 5:18:49 PM UTC+2, Erik Bray wrote: >> >> Hi all, >> >> As decided toward the end of another recent thread [1] I willl be >> taking down the server at UW which hosts both trac.sagemath.org and >> git.sagemath.org, starting around 8:00 A.M. CEST. There are at least >> three reasons for this: >> >> 1. Mitigate issues related to reliance upon university IT >> infrastructure over which we have little control [2][3] or influence >> 2. Move to tier 1 cloud-based hosting for greater ease of deployment >> and (hopefully) better reliability >> 3. Address current and ongoing preformance / access issues with the >> Trac site, which are possibly related to 1 >> >> An additional change to be aware of is that access to >> trac.sagemath.org, as well as the git web interface at >> git.sagemath.org will be switched to HTTPS *only*. HTTP redirects >> will be set up, but please update any URLs nonetheless. >> >> Other than that, with a little luck you should notice few or any >> differences. Please keep in mind though that the current Sage Trac >> infrastructure has a layer of grime and mold over it, and it's >> entirely possible I've missed a few spots while shining it up. So if >> anything isn't working after the migration please be patient and >> cooperate by sending notice either to >> sagemat...@googlegroups.com, or to me personally*. >> >> Best, >> Erik >> >> * The offer to e-mail me personally about such issues expires some >> indeterminate amount of time after the migration is completed. I want >> to be on-call for migration-related issues, but in general support >> issues should be sent to one of the mailing lists where they can be >> handled by the best personal available at the moment. >> >> [1] https://groups.google.com/d/msg/sage-devel/EKhgXsdKMhY/52fKpHDBAQAJ >> [2] https://groups.google.com/d/msg/sage-devel/Xw6CNq1lyiI/aeyT5TluDQAJ >> [3] https://groups.google.com/d/msg/sage-devel/Xw6CNq1lyiI/APzgctSUDQAJ > > -- > You received this message because you are subscribed to the Google Groups "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
