Repository navigation
Description
TL;DR
Using the Debian package radicale with [auth] configured to type = pam, having installed python3-pam, Radicale runs into a dependency error. My guess is that Debian's python3-pam is not the pam module Radicale requires. I am not familiar with how Python modules are identified in general, so more information on which PAM module exactly Radicale requires would be helpful.
If my guess is correct, then this might not be a radicale issue at all, but an issue for the Debian packager of the Python PAM module.
Steps to reproduce
Reproducing may require Debian Trixie, because it could be a packaging problem and not problem with Radicale per se.
- Install:
apt update && apt install radicale python3-pam - set up radicale to use PAM: edit
/etc/radicale/config, go to the[auth]section and settype = pam. - start radicale
systemctl start radicale systemctl status radicale→ failed (status=1/FAILURE)
In the logs:
radicale[xxx]: [xxx] [CRITICAL] An exception occurred during server startup: PAM authentication requires the Python pam module
Investigation reveals that the Debian python3-pam package provides a module named PAM (all caps), while Radicale expects the module to be called pam (lowercase) (cf. /usr/lib/python3/dist-packages/radicale/auth/pam.py, line 42: import pam).
I assumed this was still the right module, just named differently, so I tried fixing the import statement :
42c42
< import pam
---
> import PAM as pamThe next problem might be unrelated, but I had to run mkdir /var/lib/radicale/collections/collection-root && chgrp radicale /var/lib/radicale/collections/collection-root before the server was able to start.
After this, the server runs, but any authentication attempt results in a 500 internal server error, that translates to this in the log:
nov. 07 15:18:51 radicale[xxx]: [xxx/Thread-15 (process_request_thread)] [ERROR] An exception occurred during PROPFIND request on '/': module 'PAM' has no attribute 'authenticate'
Proposed solutions
My own solution was to let the reverse proxy take care of authentication, so no PAM. From then on, Radicale worked like a charm.
However, if you need to authenticate with PAM and use Debian, I have no idea what the right step might be. My guess is that the PAM module provided by python3-pam is not the same module Radicale depends on.
Activity
pbiering commentedon Nov 7, 2026
According to my Debian reference installation here:
both versions are hopeless outdated, Fedora 44 has
either trigger related package managers to update or install from PIP or as container or change OS.
pbiering commentedon Nov 7, 2026
see also https://github.com/Kozea/Radicale/wiki/Installing-on-Debian-or-Ubuntu-Linux
pbiering commentedon Nov 7, 2026
https://packages.debian.org/search?keywords=radicale -> version for Trixie and lower are not up-to-date (and insecure btw. nowadays).