|
Scott, I do the modifications mentioned for you (include ssl suport for
the application servers) and still continue don't working. Well, I like show my environment configurations and later comment the errors. I modify the cas-client.properties located in my protected applications: cas.server.gateway=false cas.server.renew=false cas.server.url="" class="moz-txt-link-freetext" href="https://plcbhdesev05:8443/cas/">https://plcbhdesev05:8443/cas/ cas.server.proxyCallbackUrl=https://plcbhdesev05:8443/cas/proxy/Receptor cas.client.serverName=plcbhdesev05:8444 cas.client.proxyCallbackUrl=https://plcbhdesev05:8444/powerportal/casProxyReceptor Explainig better: plcbhdesev05:8443 => default ssl port of tomcat's cas server; plcbhdesev05:8444 => default ssl port of tomcat's cas client; powerportal => my protected application; casProxyReceptor => I don't now what is this, considering that not exists this severvlet mapping on web.xml of my app; you It could explain this better??? In excution time, debugging cas client, after call the url: https://plcbhdesev05:8444/powerportal I'm redirected to https://plcbhdesev05:8443/cas (login page), until here, this ok, however, after login, in the method getResponseFromURL() from the class AbstractUrlBasedTicketValidator, I get the exception: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated It seems the client don't obtain access in the server to validate the ticket. You would know to say what it can be the error? My properties file is correct? Thanks! Leonardo Otoni de Assis Desenvolvimento Java - Produto eCompany Powerlogic Consultoria e Sistemas S/A (31) 3286-1691 [EMAIL PROTECTED] Scott Battaglia escreveu: 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.
|
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
