Hi Scott,
Thanks for your answer. If you mean using CAS over HTTP instead of HTTPS,
yes, that's the case for now, BUT I set the "httpClient" property to false
in CAS configuration file :
<bean
class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler"
p:httpClient-ref="httpClient" p:requireSecure="false" />
Maybe I didn't understand how the Classic ASP client should work. I try to
read the ASP application calling CASProxier.asp first. Am I right on this
point ?
Could you please give me more information, if you can.
Thanks
David
On Wed, Jan 28, 2009 at 4:21 AM, Scott Battaglia
<scott.battag...@gmail.com>wrote:
> Are you using CAS over HTTP? If so, SSO won't work by default.
>
> -Scott
>
> -Scott Battaglia
> PGP Public Key Id: 0x383733AA
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>
>
> On Tue, Jan 27, 2009 at 9:11 AM, David MARTIN <dmartin....@gmail.com>wrote:
>
>> Here is my problem.
>> With the help of the example provided in the Wiki, I can log on CAS and
>> store the user id in a Session variable. This point works great.
>>
>> But if I've logged from another web application (let's say a Java webapp)
>> and then decide to go to my classic ASP application, I HAVE TO log again.
>> And that's not what I wish (since I want single sign on...)
>>
>> I may have miss something, but if not, I do not know if there is a way to
>> auto log in that case.
>>
>> Thanks for your help.
>>
>> _______________________________________________
>> Yale CAS mailing list
>> cas@tp.its.yale.edu
>> http://tp.its.yale.edu/mailman/listinfo/cas
>>
>>
>
> _______________________________________________
> Yale CAS mailing list
> cas@tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
_______________________________________________
Yale CAS mailing list
cas@tp.its.yale.edu
http://tp.its.yale.edu/mailman/listinfo/cas
