After digging some more, I found that this issue should have been taken
cared of by the login-webflow.xml.
I found the following snippets in my installation:
<!--
The "redirect" end state allows CAS to properly end the
workflow while still redirecting
the user back to the service required.
-->
<end-state id="redirect"
view="externalRedirect:${externalContext.requestParameterMap['service']}${requestScope.ticket
== null ? '' : (externalContext.requestParameterMap['service'].indexOf('?') !=
-1 ? '&' : '?') + 'ticket=' + requestScope.ticket}" />
However, I am still having redirection problem in my deployment.
Can anyone find any issue with the statement?
Any idea why this rule misbehaves ?
Does anyone have any similar issue with me?
Does anyone confirm that you don't have this issue?
What version of Cas do you use?
Thank you all,
Ezra
On Tue, 2007-10-16 at 17:46 -0700, Ezra Nugroho wrote:
> Halo CAS experts,
>
>
> Currently I am facing the following issue.
>
> Say http://service_url is a url of a casified application.
> When a user logs in to the application using CAS, CAS will redirect to
> the http://service_url again while attaching the service ticket.
>
> Now if the original url has a GET variable (i.e.
> http://service_url?some_var), CAS fails to use the correct separator for
> the ST variable. CAS still uses '?' instead of '&'.
>
> How can this be corrected?
> I scour through the code, and it seems that this functionality is
> handled by Spring. Is it Spring bug?
>
> Btw, I am using cas-sever-3.0.5.
>
>
> Thank you,
> Ezra
>
> _______________________________________________
> 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
