There is a login sesison timeout config in web.xml. You will get login page
again if you wait for more than 5 minutes.
<session-config>
<!-- Default to 5 minute session timeouts -->
<session-timeout>5</session-timeout>
</session-config>
Cheers,
Qingfeng
2009/9/18 Alok Jain <[email protected]>
> Hi Scott,
>
> Thx for your reply . I am able to successfully set
> up CAS in my local environment . It works fine except for the following
> issue :
>
> If I paste the login URL on my
> browser window and then CAS presents me with the login page and If I provide
> my credentials immediately it logs me in successfully. However If I wait
> for sometime and then provide the credentials, it does not do anything , it
> again presents the login page with the login / password field blank , now
> when I provide the credientials it works fine.
>
>
>
> --Alok
>
>
>
>
>
> *From:* Scott Battaglia [mailto:[email protected]]
> *Sent:* Wednesday, September 16, 2009 12:07 PM
> *To:* [email protected]
> *Subject:* Re: [cas-user] CAS deployed on tomcat and accessed through
> apache over SSL.
>
>
>
> As long as it started up okay you're fine. In 3.1.8 we've changed that
> message to be more informative than what it is. Essentially what that is
> saying below is its trying to load a property from JNDI (it tries to load
> properties in multiple ways) and the property was not in JNDI.
>
> In 3.1.8 we've refined the message to merely say where it found it instead
> of where it didn't find it ;-)
>
> Cheers,
> Scott
>
> On Wed, Sep 16, 2009 at 3:04 PM, Alok Jain <[email protected]>
> wrote:
>
> Thx Marvin...
> I have now setup CAS on my local environment with Spring
> Security in the application.
> I am getting the following exception , I am using Spring Security with CAS
> cas-server-webapp-3.3.3 :
>
> [INFO,ContextLoader,main] Root WebApplicationContext: initialization
> completed in 833 ms
> [WARN,SingleSignOutFilter,main] javax.naming.NameNotFoundException: Name
> cas is not bound in this Context
> javax.naming.NameNotFoundException: Name cas is not bound in this Context
> at org.apache.naming.NamingContext.lookup(NamingContext.java:770)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:781)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:781)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
> at
> org.apache.naming.SelectorContext.lookup(SelectorContext.java:137)
> at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at
> org.jasig.cas.client.util.AbstractConfigurationFilter.loadFromContext(AbstractConfigurationFilter.java:77)
> at
> org.jasig.cas.client.util.AbstractConfigurationFilter.getPropertyFromInitParams(AbstractConfigurationFilter.java:56)
> at
> org.jasig.cas.client.session.SingleSignOutFilter.init(SingleSignOutFilter.java:41)
> at
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
> at
> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
> at
> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108)
> at
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3696)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:516)
>
>
> --Alok.
>
>
>
>
> -----Original Message-----
> From: Marvin Addison [mailto:[email protected]]
> Sent: Monday, September 14, 2009 6:06 PM
> To: [email protected]
> Subject: Re: [cas-user] CAS deployed on tomcat and accessed through apache
> over SSL.
>
> > If I have Apache routing all the requests to my CAS webapp
> > deployed on tomcat , is it ok to have Apache over SSL and tomcat over
> http.
>
> This sounds like the typical Apache reverse proxy setup for Tomcat.
> In that case it's probably more common to use the AJP protocol instead
> of HTTP, but I can't think of any particular problem with your
> proposed setup provided you trust the network between the Apache and
> Tomcat hosts. As long as the client/browser thinks it is talking
> HTTPS to the CAS server, everything should work fine.
>
> M
>
> --
>
> 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
>
>
> --
> 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
>
>
>
> --
>
> 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
>
> --
> 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
>
>
--
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
