On 11-02-11 9:29 AM, [email protected] wrote:
HelloIt seems that I found a bug I explain Sogo configures with <key>SOGoIMAPServer</key> <string>imaps://imap.ece.fr</string> with CAS (ssl) On my cas server, the service is imap instead of imaps 2011-02-11 15:09:37,126 INFO [org.jasig.cas.CentralAuthenticationServiceImpl] - <Granted service ticket [ST-244572-yNpKd0ZXH1XSP7qdgTBWcWsDmb1xO5Lmbpj-20] for service [imap://imap.ece.fr] for user [https://srv-webSOGO1.ece.fr/SOGo/casProxy]> So the ticket is INVALID when Sogo connect on the IMAPS Server DEBUG: auth_pam: pam_authenticate failed: authentication error Feb 11 15:26:31 imaps PAM_cas[89736]: authentication failure ^M ^M <cas:serviceResponse xmlns:cas='http://www.yale.edu/tp/cas'>^M <cas:authenticationFailure code='INVALID_SERVICE'>^M le ticket 'ST-244572-yNpKd0ZXH1XSP7qdgTBWcWsDmb1xO5Lmbpj-20' ne correspond pas au service demandé^M</cas:authenticationFailure>^M</cas:serviceResponse> (this is normal because the service is imaps://imap.ece.fr and the ticket on the cas server is for service imap://imap.ece.fr Is it a bug ?
Likely.
How could I change this (to have sogo ask the good service : imaps://imap.ece.Fr )
File a bug report or toy around with the CAS code in SoObjects/SOGo. Regards, -- Ludovic Marcotte [email protected] :: +1.514.755.3630 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- [email protected] https://inverse.ca/sogo/lists
