I’ve briefly discussed the issue with @chris.adams this morning as planned on IRC . Here is an extract from the logs:
dcaliste Since 3.4.0 changes in account creation, I think the login / password are checked on the root of the server before going further and retrieving calendar list... 09:03
dcaliste On some servers, the authentication on root is forbidden. 09:03
dcaliste So account creation is failing. 09:03
dcaliste Restoration from storage is failing also for the same reason I guess. 09:04
chriadam eek. 09:04
chriadam so we need to fallback to trying on ... either caldav calendars path, or carddav addressbooks path, or webdav home set path? 09:05
dcaliste Yes, that was my first guess, but there is an issue doing so : the caldav path may be guessed. 09:06
dcaliste So not available at that point. 09:06
chriadam what do you mean by "guessed"? do you mean, looked up via the .well-known endpoint, or something else? 09:06
dcaliste See the kolab issue, there is no webdav path, and caldav and carddav paths are different. 09:07
dcaliste Yes, looked up via .well-known. 09:07
dcaliste (well in the kolab report the .well-known seems to fail but that's another story, more related to server side I think). 09:08
dcaliste So the situation is : 09:09
dcaliste - server root / webdavpath may be forbidden and refused for authentication. 09:09
dcaliste - server root/ webdav path/.well-known may be the solution to try to authenticate 09:10
dcaliste - using the caldav path or the carddav one may not be possible, because not provided by the user at that point. 09:10
chriadam thanks. I've created JB#52704 for this, and will poke Bea to investigate further 09:11
dcaliste Thank you, the solution is not easy in my opinion and relies a lot on server implementation, difficult to find a universal solution. But thanks. I'll keep an eye on the repo and will comment if I can give constructive opinion. 09:12
chriadam yeah, trying to support all different possible servers is ... hard ;-) but we'll do the best we can. thanks very much for bringing it to my attention 09:13
dcaliste No problem, the workaround to create separated accounts puting the *DAV path in the webDAV path to cheat the code highlight the issue but is a bit ugly... 09:14
chriadam yeah definitely shouldn't be required.
He agreed that the workaround is not a proper solution and opened an internal bug on the topic. The bug tracker and the repo it is dealing with are both closed in Jolla. So we cannot have direct access at how they will deal with the bug, but at least developpers know about it. We may ask for advances in a later community meeting for instance.