[Freedombox-pkg-team] Bug#1100995: Bug#1100995: freedombox: Radicale stopped working after upgrade to radicale version 3.5.0-1

[Petter Reinholdtsen]

[Sunil Mohan Adapa]
> I have submitted a patch to fix the auth/type configuration with
> radicale 3.5. This ensures that new installs on trixie will not face
> any issues. Both James and I have confirmed that just changing
> auth/type in sufficient to make it work properly. However, there is
> more to this issue:

Aha.  Why did you go with remote_user?  The new http_x_remote_user
option seem to be a better fit when reading
/etc/apache2/conf-enabled/radicale2-freedombox.conf, with its
'RequestHeader set X-Remote-User expr=%{REMOTE_USER}' setting.

My file also had "type = owner_write" in /etc/radicale/config which was
lost when upgrading.  I notice your merge request do not touch this
part.  Is it no longer needed?

> 2) Another problem is the authentication issues that you are 
> experiencing. Even when auth/type is configured correctly in radicale 
> LDAP authentication to view the web interface fails repeatedly (and then 
> fail2ban complained). I have briefly experienced this. However, during 
> repeated testing later, I could not reproduce the issue. Could you 
> please try the following debugging:
>
> Set "LogLevel debug" or "LogLevel trace5" in <Location /radicale> 
> section in /etc/apache2/conf-available/radicale2-freedombox.conf. 
> Restart Apache and watch journalctl -f when trying to login into 
> radicale interface.

I am not sure what happened, but when I had a look now, the calendar
sync is back in operation, so no debugging needed.  Thank you for the
recipe, I will try to keep it in mind for the next time this break. :)

-- 
Happy hacking
Petter Reinholdtsen