Postby noritaka » Mon Mar 17, 2008 8:49 am
Thanks for the reply.
We use CAS SSO for web sso, I think that to achieve this goal, the webmail of scalix must send a Ticket, in place of the password, like in horde imp :
[quote]
Next, the behavior of the webmail was modified to take into account the versatility of this new kind of password. Indeed, PTs are manipulated in the same way that passwords are, although their validity is limited. In other words, the webmail can use a PT several times thanks to the IMAP cache, but a PT stored in the IMAP cache can be erased (because of the garbage collector of the IMAP cache), supplanted in the cache by another PT (if another webmail instance is running for the same user), or simply replaced by the user’s password if the user concurrently accesses a traditional mail client. In all of these situations, the next connection with the PT would be refused by the IMAP server. To get around this problem, the webmail was modified to allow a new PT to be acquired from the CAS server, in order to make a second attempt at an IMAP connection.
Obviously, using CAS client libraries are not as simple as was implied in 5.1.1 (“Writing a PHP CAS clientâ€