On 16/06/12 10:18, J.-M. Kubek wrote:
Le vendredi 15 juin 2012 à 15:24 -0300, Federico Alberto Sayd a écrit :
Hello
[.... Snipp ... ]
However the certificate in the cas server is valid and recognized by any
browser and connection to server tested with openssl, also, the
certificate is installed in the dovecot server and configured in the
pam_cas.conf configuration file.
Is the cas server able to recognize the mail server certificate ?
The problem is that the imap server never starts the connection with the
cas server because don't recognize the certificate of the cas server
although I declare the certificate file of cas server in the pam_cas
configuration.
SOGo connects with CAS server and receive a ticket from CAS. All the
serves (SOGo, CAS, IMAP) share the same wildcard certificate for my
domain. CAS docummentation insist in the use of ssl in all connections.
Anyone knows if there is a alternative to pam_cas to authenticate a imap
server? The module is in the legacy section of CAS downloads. Since SOGo
supports CAS and this implies that the imap server should be casifyed,
the existence of a stable and maintained cas-auth mechanism for imap is
not just a little detail.
What are the logs on the cas side ?
Regards,
J.-M.
Anyone running SOGo+CAS+Dovecot?
Any clue is appreciated
Thanks
Federico
PS: Script cas-proxy-validate.py isn't in the sogo v. 1.3.16 package for
Debian. I think that such file should be in the /usr/share/doc/sogo dir;
I had to download it from the mtn repository
--
[email protected]
https://inverse.ca/sogo/lists
