[cas-dev] Google SAML SSO

[Patrick Berry]

I made some changes to casPostResponseView.jsp to deal with PeopleSoft.
Oooooh....I think I see what's happening.  Ugh.  I tacked on $ticket to the
form action.

Well, this is going to have a potentially large amount of suck...


On Thu, Sep 18, 2008 at 9:18 AM, Scott Battaglia
<scott.battaglia at gmail.com>wrote:

> Pat,
>
> Did you guys make any recent changes to the CAS software?
>
> The code for the Google Accounts stuff is here:
>
> http://developer.ja-sig.org/source/browse/jasigsvn/cas3/branches/cas-3-2_maintenance/cas-server-core/src/main/java/org/jasig/cas/authentication/principal/GoogleAccountsService.java?r=43968
>
> As long as the GoogleAccountsArgumentExtractor is configured everything
> should just *work* (in theory ;-))
>
> -Scott
>
> -Scott Battaglia
> PGP Public Key Id: 0x383733AA
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>
>
> On Thu, Sep 18, 2008 at 11:22 AM, Patrick Berry <pberry at gmail.com> wrote:
>
>> We're still in development for CAS 3 and Google Apps, but recently our SSO
>> link went haywire.
>> The Google Team came back with this:
>>
>> Hi Patrick,
>>>
>>> Looking at the log, it looks like the SAML response is being submitted
>>> to:
>>> https://www.google.com/a/mail.csuchico.edu/acs&ticket=
>>>
>>> instead of the correct ACS URL:
>>>
>>> https://www.google.com/a/mail.csuchico.edu/acs
>>>
>>> Is this a configuration item in JA-SIG CAS which you have control over?
>>>
>>> Regards,
>>>
>>> Alex
>>> Google Apps API Team
>>>
>>
>> Now, it's being generous when I say I'm completely ignorant of how CAS 3
>> does SAML.  Where might I start looking for where this is all being
>> generated?
>>
>> Thanks,
>> Pat
>>
>> _______________________________________________
>> cas-dev mailing list
>> cas-dev at tp.its.yale.edu
>> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>>
>>
>
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20080918/3d2ad245/attachment.html