problem when changing of server

[Scott Battaglia]

If you are running CAS over a non-SSL port, the secure cookie will not be
sent back to the browser.  This means that each redirect to CAS will cause a
request for credentials.

-Scott

On 2/1/07, Leonardo Otoni de Assis <leo at powerlogic.com.br> wrote:
>
> Hi everybody!
>
> I have a cas server implemented with "cas client for java" and be
> working...
> I do a copy of my server with application protected by cas client and
> starts this in differents ports (the app server is tomcat 559 with jsdk
> 1.5) and the same working too.
>
> Both, tomcat1 and tomcat2 redirect's correctly to cas server and then
> returns for one of then after user's login.
>
> My environment:
>
> The tomcat1 listen on: http://plcbhdesev05:8001;
> The tomcat2 listen on: http://plcbhdesev05:8002;
> The cas server listen on http://plcbhdesev05:8080;
>
> If I call tomcat1, log the user in cas server and turn to tomcat1 and
> them, call tomcat2, changing only the server port, I come back to the
> cas server login page.
> If the user have a ticket, why the cas client redirect me to the cas
> server login page?
>
> Thanks,
>
> --
>
> Leonardo Otoni de Assis
> Desenvolvimento Java - Produto eCompany
> Powerlogic Consultoria e Sistemas S/A
> (31) 3286-1691
> leo at powerlogic.com.br
>
>
> --
> Esta mensagem foi verificada pelo sistema de antivírus e
> acredita-se estar livre de perigo.
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20070201/86d906f4/attachment.html