In relation to https://git.kolab.org/T1133
"Implement canonification within Kolab WAP and pykolab without depending on Cyrus"
this is currently not a requirement for TBits.net, but I want to write it down so I know what the issues are...
/usr/share/roundcubemail/plugins/kolab_auth/kolab_auth_ldap.php, get_user_record, fetches the full e-mail address for the user, but only from the primary domain, because it uses the uid=kolab-service,ou=Special Users,dc=primarydomain,dc=de
The actual authentication with the password of the user happens in /usr/share/roundcubemail/program/lib/Roundcube/rcube_imap.php line 194
against IMAP, and in the end via kolab-saslauth
Question: if get_user_record would not return anything for the user, if it cannot find the uid in the primary domain, then it should work to just authenticate against CyrusIMAP with the patched kolab-saslauth?
In relation to https://git.kolab.org/T1133 "Implement canonification within Kolab WAP and pykolab without depending on Cyrus"
this is currently not a requirement for TBits.net, but I want to write it down so I know what the issues are...
/usr/share/roundcubemail/plugins/kolab_auth/kolab_auth_ldap.php, get_user_record, fetches the full e-mail address for the user, but only from the primary domain, because it uses the uid=kolab-service,ou=Special Users,dc=primarydomain,dc=de
The actual authentication with the password of the user happens in /usr/share/roundcubemail/program/lib/Roundcube/rcube_imap.php line 194 against IMAP, and in the end via kolab-saslauth
Question: if get_user_record would not return anything for the user, if it cannot find the uid in the primary domain, then it should work to just authenticate against CyrusIMAP with the patched kolab-saslauth?