[07:55:43 CST(-0600)] <ries> Hope I can ask my question again...
[07:55:50 CST(-0600)] <ries> how do you in general implement password warning?
[07:55:55 CST(-0600)] <ries> I see it's implemented in CAS 3.4.11, but I don't see how I should use it
[07:56:06 CST(-0600)] <ries> Documentation from 2009 seems to be outdated : https://wiki.jasig.org/display/CAS/Expired+Password+Integration
[07:56:12 CST(-0600)] <ries> tates that there is a AccountStatusAction but it's no where to be found
[08:58:59 CST(-0600)] <foxnesn> hello
[09:06:22 CST(-0600)] <foxnesn> i am working on setting up cas so that if a user goes to hostname/cas/login and is validated they are redirected to a specific casified service rather than see the "login successful" message
[09:06:30 CST(-0600)] <foxnesn> is this something that i can do in login-webflow.xml ?
[09:07:30 CST(-0600)] <foxnesn> i see the "viewGenericLoginSuccess" end state and view
[09:29:23 CST(-0600)] <foxnesn> nvm got it
[12:28:50 CST(-0600)] <foxnesn> hi guys im attempting to implement jpaticketreg and am receiving the following error
[12:28:54 CST(-0600)] <foxnesn> Cannot resolve reference to bean 'entityManagerFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in ServletContext resource [/WEB-INF/spring-configuration/ticketRegistry.xml]: Cannot resolve reference to bean 'dataSource' while setting bean property 'dataSource'
[12:38:06 CST(-0600)] <foxnesn> ok nvm i was using the wrong ticketRegistry bean
[12:38:13 CST(-0600)] <foxnesn> so now i am getting...
[12:38:27 CST(-0600)] <foxnesn> Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.jasig.cas.ticket.registry.JpaTicketRegistry]: No default constructor found
[12:38:55 CST(-0600)] <foxnesn> following these directions https://wiki.jasig.org/display/CASUM/JpaTicketRegistry
[13:35:58 CST(-0600)] <ries> fox, that last error also seems to be a configuration issue
[13:36:14 CST(-0600)] <foxnesn> seems that way
[13:36:25 CST(-0600)] <foxnesn> do i need to add any jar files to tomcat lib other than mysql?
[13:36:51 CST(-0600)] <foxnesn> im using the same format as ticketRegistry.xml from the wiki
[13:37:03 CST(-0600)] <foxnesn> and i added the hibernate and c3po dependencies to my pom
[13:37:04 CST(-0600)] <ries> it doesn't look like that error has something todo with a jar missing, if that would be the case you see stuff like class exception
[13:38:03 CST(-0600)] <ries> did you create a entityManagerFactory bean?
[13:38:06 CST(-0600)] <foxnesn> my ticket reg xml matches the one in the wiki with the changes to the database location and schema
[13:38:10 CST(-0600)] <foxnesn> no i did not
[13:38:28 CST(-0600)] <foxnesn> well
[13:38:37 CST(-0600)] <foxnesn> im using the one from the ticket reg xml wiki
[13:38:42 CST(-0600)] <foxnesn> https://wiki.jasig.org/display/CASUM/JpaTicketRegistry
[13:38:44 CST(-0600)] <ries> Check your deployerConfigontext.xml
[13:38:52 CST(-0600)] <foxnesn> oooo
[13:39:24 CST(-0600)] <foxnesn> but what should go in deployer? i dont see mention in the wiki
[13:42:21 CST(-0600)] <ries> I took some ideas from tho space : https://wiki.jasig.org/display/CASUM/Configuring
[13:43:16 CST(-0600)] <foxnesn> hrm so i need duplicate entity managers in deployer and in ticketreg ?
[13:44:25 CST(-0600)] <ries> Hmmm nope… you do have some freedom where to put what beans where...
[13:44:40 CST(-0600)] <foxnesn> i guess
[13:44:58 CST(-0600)] <foxnesn> i thought all of the connection info and reqquired beans would be held in the ticketregistry.xml file
[13:45:08 CST(-0600)] <foxnesn> with the required hibernate dependencies in pom.xml
[13:45:58 CST(-0600)] <ries> So I just send my first message on the CAS mailing list, then I get back : I will be out of the office on Disability. You may contact me after the end of April 2012.
[13:46:00 CST(-0600)] <ries> hahaha
[13:46:30 CST(-0600)] <ries> foxnesn: that would be a better place to put them.. I just happen to have then somewhere else
[13:46:35 CST(-0600)] <ries> I am new to this stuff myself
[13:47:43 CST(-0600)] <foxnesn> our setup works very well as is
[13:47:55 CST(-0600)] <foxnesn> but we are looking into high availability and want to store tickets on a database
[13:48:09 CST(-0600)] <foxnesn> and it seems the docs are a bit confusing
[13:48:18 CST(-0600)] <ries> Understood… I am still in a phase where I try to display a message 'your password is about to expire' 
[13:48:45 CST(-0600)] <foxnesn> we used a third party solution for that kind of thing
[13:49:05 CST(-0600)] <ries> But don't you want to show that after a user log's in?
[13:51:52 CST(-0600)] <foxnesn> it does
[13:52:01 CST(-0600)] <foxnesn> the program is casified
[13:57:00 CST(-0600)] <ries> Hmmm I was planning to show this in a CAS screen..
[13:57:16 CST(-0600)] <foxnesn> i can specific the version of cas simply by changing it in the pom.xml if i build using maven, right?
[13:57:36 CST(-0600)] <foxnesn> specify
[13:58:02 CST(-0600)] <foxnesn> so if i change properties to 3.4.11 from 3.4.10 then i have the new version?
[14:06:04 CST(-0600)] <ries> yup.. that worked for me
[14:34:20 CST(-0600)] <foxnesn> ries, do you have cas-server-core in your pom.xml ?
[14:34:28 CST(-0600)] <ries> let me check
[14:36:10 CST(-0600)] <ries> yes, for my main web app
[14:36:21 CST(-0600)] <ries> <dependency>
[14:36:21 CST(-0600)] <ries> <groupId>org.jasig.cas</groupId>
[14:36:21 CST(-0600)] <ries> <artifactId>cas-server-core</artifactId>
[14:36:22 CST(-0600)] <ries> <version>$ </version>
[14:36:22 CST(-0600)] <ries> </dependency>
[14:37:54 CST(-0600)] <foxnesn> yay
[14:38:01 CST(-0600)] <foxnesn> apparently i need that lol
[14:59:25 CST(-0600)] <foxnesn> hrm, it isn't creating the tables...