Thanks jleleu.
Before I can update uportal CAS client to V 3.2.1, I changed the CAS server's
code to disable service match validate.
It's not a safe way, but as a temp approch it works.
Thanks for your help,I will update all my CAS client to V 3.2.1 and find a
right way to ending this encoding problem.
> Hi,
>
> If you want to url encode the service, you should encode all the url, not
> only the parameters as you did for JIRA service. Nonetheless, I'm not sure it
> will solve your problem as it fails for service ticket validation.
>
> The way I see things : for service ticket validation, the url encoding is
> done and it's ok but unfortunately, for proxy ticket request (/proxy), the
> url encoding is not done which makes url truncated and proxy ticket
> validation fails.
> I don't know the old Yale CAS client, I don't know if it can come from here.
> Maybe someone has heard about a problem with proxying using this client...
>
> I would try to upgrade to the JASIG CAS client v 3.2.1 in uportal.
>
> If you can't do that, turn on DEBUG logs on edu.yale.its.tp.cas.client
> package in uportal, make a test and post your logs ?
>
> Best regards,
> J~{(&~}r?me
>
> --
> 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
--
mist <[email protected]>
--
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
