Andrew,

I don't think we've evaluated this solution enough to determine whether 
it should be in CVS or not.

The solution in the patch exposes a different login endpoint for 
authentication, which I'm not convinced is the best solution.  It 
appears there are three ways to handle this scenario:

1.  Expose a different URL endpoint with a different flow for handling 
the POST scenario
2.  Expose a request parameter such as returnMethod (defaults to GET) 
which would cause the web flow to choose either a normal redirect or a 
JavaScript POST.
3.  Add post capabilities on the client applicaion side (either as part 
of the CAS client or inform people to handle it locally in their 
application)

[there may be other scenarios, these are just the ones I thought of off 
the top of my head]

Each scenario has its strengths and weaknesses.  Until we've evaluated 
the best method for handling this I'd rather not commit anything into 
CVS at this point.  Anything committed to CVS would need to be supported 
in the future, regardless of whether we found a better solution or not.

-Scott

Andrew Petro wrote:
> Jeff, 
>
> I appreciate your positive attitude, but I think it would be best if we got
> this patch into CAS source control and kept it up to date and as
> no-heroics-required as possible.
>
> In that vein, where would be appropriate for this to go into CVS, Scott?
> Should CAS ship this example?  Stick it under a contrib directory?
>
> Andrew
>
>   
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
>> Behalf Of Jeffrey M Goodwin
>> Sent: Monday, July 10, 2006 7:49 AM
>> To: Yale CAS mailing list
>> Subject: RE: Redirect to Service with POST
>>
>> Hi Scott,
>>
>> I agree.  I am in the process of doing so right now.  I am just so new
>> to both CAS and spring's web flow api it is taking a bit longer than I
>> had hoped.  Oh well, I guess it is a good introduction to both
>> technologies.
>>
>> Thanks,
>> Jeff
>>     
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>   
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to