IMAP and POP3 with GMail and CAS
Borchers, Kristopher C.
kborchers at sxu.edu
Tue Nov 4 16:25:50 EST 2008
Brent:
Thanks for the reply. That's the direction we thought we would have to
go but were hoping we were wrong.
Thanks for the info!
Kris
Kristopher Borchers
Web Application Developer - Content Analyst
Saint Xavier University
Ph. 773-298-3924
kborchers at sxu.edu <mailto:kborchers at sxu.edu>
www.sxu.edu <http://www.sxu.edu>
Saint Xavier University - Success with Purpose.
Saint Xavier University, a Catholic institution inspired by the heritage
of the Sisters of Mercy, educates men and women to search for truth, to
think critically, to communicate effectively, and to serve wisely and
compassionately in support of human dignity and the common good.
________________________________
From: cas-bounces at tp.its.yale.edu [mailto:cas-bounces at tp.its.yale.edu]
On Behalf Of Brent Putman
Sent: Monday, November 03, 2008 4:41 PM
To: Yale CAS mailing list
Subject: Re: IMAP and POP3 with GMail and CAS
Borchers, Kristopher C. wrote:
We recently launched Gmail at our school and we are receiving complaints
from users that they can not set up IMAP or POP3 for their e-mail
clients. I am assuming this is because we are using CAS and SAML to
authenticate our users and when they try to use IMAP or POP3, the
authentication is failing.
Yes, that is my understanding. The SAML SSO solution only works for the
web-based components, not IMAP, POP, GoogleTalk, etc. The latter are
password-based only.
Has anyone else run into this and found a way to make it work or even
had ideas on how to make it work which I can try to implement?
Someone from the USC middleware group presented on their Google Apps
project at the recent Internet2 meeting. Link to presentation below.
They use Shibboleth for SAML SSO support, not CAS, but same issues, I
imagine. My understanding is that non-web based components are
authenticated by a separate Google password, distinct from the USC
password, which is stored/maintained on Google's systems and managed via
USC provided tools which invoke Google's provisioning API. Or something
along those lines.
http://www.internet2.edu/presentations/fall08/20081015-googleapps-bellin
a.pdf
Don't know for sure whether Google exposes any other authN options which
CAS could leverage for non-web-based apps, but I haven't heard of any.
--Brent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20081104/047df38d/attachment.html
More information about the cas
mailing list