Some time ago I finally succeeded in getting a SAML login to SOGo to work
properly. However, while I was able to login to SOGo, the necessary
authentication was not passed the IMAP server (Cyrus). During the process I
received a great amount of help from the group (AUF) whom I believe are
sponsoring the additional SAML features for 2.2.9.

According to the manual, there are two ways to handle the authentication to
the IMAP server, PAM or SASL. I'm receiving errors with both:

SASL: unable to dlopen /usr/lib/sasl2/libsaml.so.0:
/usr/lib/sasl2/libsaml.so.0: undefined symbol:
lasso_provider_verify_saml_signature

PAM: PAM unable to dlopen(/lib/security/pam_saml.so):
/lib/security/pam_saml.so: undefined symbol: lasso_misc_text_node_get_type

The help I received from AUF mentioned that the compiled versions from
Inverse did not expose the appropriate variables in order for this to
function properly (liblasso). Looking at the error messages, I'm inclined
to agree.

The recommendation was to compile the program with necessary patches to
expose those variables. Could these changes be incorporated in the binary
files in the Inverse repository or would the change prevent something else
from working properly?

Steve
-- 
[email protected]
https://inverse.ca/sogo/lists

Reply via email to