The behavior you are expecting is what should be happening, and is the behavior we have with our Google Apps domain. I would start with checking your browser cookie jar to make sure you have the proper CAS cookies.
Good to see you have basic SAML auth working. Pat On Dec 22, 2009, at 2:59 PM, Curtis Garman wrote: > What is the expected behavior of google and cas once all is configured > correctly? I got my keys and certificate generated and configured things on > google's side. When I hit google with > https://mail.google.com/a/<google-domain> (without logging into cas > elsewhere), I'm getting redirected to cas...good...I can log in to cas and be > directed to my google account...as I expected should happen. However, when i > log in to uportal and click on a link to google (same as above), I'm also > being directed to cas and prompted for my username and password. I was > expecting that cas would detect my cas ticket that was generated when I > logged in to the portal, user the cas ticket to determine username and > complete the saml request from google without me having to know it was > happening. Is there something simple I'm still missing? > > -- > Curtis Garman > Web Programmer > Heartland Community College > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
