Actions that don't modify a repository (svn up, svn log, svn ls) shouldn't require authentication, whereas actions that do (svn commit, svn delete, svn propedit) should require authentication. This would allow, for example, automated updates of checkouts without having to store passwords on those machines, which still protecting commits.
Originally by: *anonymous
Please note that this is a top issue for the Tiki project: https://tiki.org/Migrate+to+Allura#Issues
Moved to https://trac.sdot.me/trac/siteops/ticket/53434
Also, fixed. Anonymous https is now working on Allura.
Originally by: *anonymous
Hi,
It's nice to see interest on this regression but I'm unclear on the meaning of the change.
What is the meaning of the status "invalid"?
This regression is definitely a valid concern for us and Sourceforge.
It is a pain for us and a lowering of security for SourceForge. Since in practice it encourages the creation of extra accounts with non-confidential (meaning stored left and right) passwords.
Originally by: *anonymous
Ohhh, I was too fast, disregard previous message.
Fix confirmed to be working fine.
Thanks a lot in the name of the Tiki community (we are in the middle of a TikiFest, so word has passed around and beverages are being pulled out)! :)
Sorry, "invalid" isn't a very good term. The issue is valid, but it wasn't the "Allura" team that worked on it which is why I closed out the ticket. Our ops team has completed this work this afternoon.