I don't quite understand your question. I open uportal 
http://localhost:8080/uPortal and I open my application 
http://localhost:8080/application

When I login to uPortal by CAS, it redirects me to
http://localhost:8080/cas/login?service=http://localhost:8080/uPortal/Login

When I open my application http://localhost:8080/Recruiting/test.jsp, it 
redirects me to
https://localhost:8443/cas/login?service=http%3A%2F%2localhost%3A8080%2FRecruiting%2Ftest.jsp

I open the above links can answer your question.


Edward



Scott Battaglia wrote:
> Are you running CAS and uPortal over HTTPS?  Otherwise CAS won't store 
> the cookie.
>
> -Scott
>
> -Scott Battaglia
> PGP Public Key Id: 0x383733AA
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>
> On Tue, Jul 22, 2008 at 11:41 AM, Edward Chen <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     Hi,
>
>     I am still new to this area. Please help
>
>     I have uPortal(quick-start) installed and up and running
>     configured with
>     CAS 3.2 ( LDAP )
>     I have one application up and running with CAS 3.2, and this
>     application
>     is not inside the uPortal
>     Both uPortal and this application are in the same Tomcat server and
>     using the same CAS in the same machine
>
>     The problem is
>     I have to login twice by CAS to uPortal and the application. That
>     means
>     I login to uPortal by CAS, then when I open the application, the CAS
>     login page popped up again and I have to login again
>
>     Now I want to know how to access the application without CAS login
>     again
>     after I login to uPortal or
>     access the uPortal without CAS login again after I login to
>     application
>     *
>     I know that proxying is generally used when one application wants to
>     access another application ON BEHALF of the user. A typical use
>     case for
>     this is a portal (such as uPortal) attempting to access a
>     application.*
>
>     I don't know how to apply proxying into my case and how to do a simple
>     configuration.
>
>     Any advice?
>
>
>     Edward
>     _______________________________________________
>     Yale CAS mailing list
>     [email protected] <mailto:[email protected]>
>     http://tp.its.yale.edu/mailman/listinfo/cas
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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

Reply via email to