Thanks, Pat. If people want to post any "upgrade to RC1" woes in here, we can compile it into a page in the wiki for upgraders.
Cheers, Scott On Fri, Feb 26, 2010 at 1:12 PM, Patrick Berry <[email protected]> wrote: > I should also note that this diff of the deployerConfigContext.xml is > helpful in upgrading from 3.3.5 to 3.4-RC1 > > @@ -15,7 +15,9 @@ > <beans xmlns="http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:p="http://www.springframework.org/schema/p"; > - xsi:schemaLocation="http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";> > + xmlns:sec="http://www.springframework.org/schema/security"; > + xsi:schemaLocation="http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-3.0.xsd > + http://www.springframework.org/schema/security > http://www.springframework.org/schema/security/spring-security-3.0.xsd";> > <!-- > | This bean declares our AuthenticationManager. The > CentralAuthenticationService service bean > | declared in applicationContext.xml picks up this AuthenticationManager > by reference to its id, > @@ -98,20 +100,17 @@ > This bean defines the security roles for the Services Management > application. Simple deployments can use the in-memory version. > More robust deployments will want to use another option, such as the > Jdbc version. > > - The name of this should remain "userDetailsService" in order for Acegi > to find it. > + The name of this should remain "userDetailsService" in order for Spring > Security to find it. > > To use this, you should add an entry similar to the following between > the two value tags: > battags=notused,ROLE_ADMIN > > where battags is the username you want to grant access to. You can put > one entry per line. > - --> > - <bean id="userDetailsService" > class="org.springframework.security.userdetails.memory.InMemoryDaoImpl"> > - <property name="userMap"> > - <value> > - > - </value> > - </property> > - </bean> > + --> > + > + <sec:user-service id="userDetailsService"> > + <sec:user name="@@THIS SHOULD BE REPLACED@@" password="notused" > authorities="ROLE_ADMIN" /> > + </sec:user-service> > > <!-- > Bean that defines the attributes that a service may return. This > example uses the Stub/Mock version. A real implementation > > > On Fri, Feb 26, 2010 at 9:56 AM, Scott Battaglia < > [email protected]> wrote: > >> Sorry we added a new property in CAS 3.4 to hold the roles (for people who >> map to LDAP). There should be a default one in CAS: >> >> >> https://www.ja-sig.org/svn/cas3/trunk/cas-server-webapp/src/main/webapp/WEB-INF/cas.properties >> >> You can probably just copy that one in to your custom one. >> >> Cheers, >> Scott >> >> >> On Fri, Feb 26, 2010 at 12:54 PM, Patrick Berry <[email protected]> wrote: >> >>> I dropped 3.4-RC1 into my pom, did a mvn clean package, cleaned out >>> $TOMCAT/webapps/cas and unfortunately got this: >>> >>> 2010-02-26 09:47:09,419 ERROR >>> [org.springframework.web.context.ContextLoader] - Context initialization >>> failedorg.springframework.beans.factory.BeanDefinitionStoreException: >>> Invalid bean definition with name >>> 'org.springframework.security.web.access.intercept.FilterSecurityInterceptor#0' >>> defined in null: Could not resolve placeholder >>> 'cas.securityContext.serviceProperties.adminRoles >>> ' >>> at >>> org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:272) >>> at >>> org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:75) >>> at >>> org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553) >>> at >>> org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:527) >>> at >>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362) >>> at >>> org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255) >>> at >>> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199) >>> at >>> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45) >>> at >>> org.jasig.cas.web.init.SafeContextLoaderListener.contextInitialized_aroundBody0(SafeContextLoaderListener.java:62) >>> at >>> org.jasig.cas.web.init.SafeContextLoaderListener.contextInitialized_aroundBody1$advice(SafeContextLoaderListener.java:44) >>> at >>> org.jasig.cas.web.init.SafeContextLoaderListener.contextInitialized(SafeContextLoaderListener.java:1) >>> at >>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3795) >>> at >>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4252) >>> at >>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) >>> at >>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) >>> at >>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) >>> at >>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:831) >>> at >>> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:720) >>> at >>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) >>> at >>> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150) >>> at >>> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) >>> at >>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) >>> at >>> org.apache.catalina.core.StandardHost.start(StandardHost.java:736) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) >>> at >>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) >>> at >>> org.apache.catalina.core.StandardService.start(StandardService.java:448) >>> at >>> org.apache.catalina.core.StandardServer.start(StandardServer.java:700) >>> at org.apache.catalina.startup.Catalina.start(Catalina.java:552) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:597) >>> at >>> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) >>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) >>> >>> >>> I don't have anything funny in cas.properties though, at least nothing >>> that breaks 3.3.5. >>> >>> On Fri, Feb 26, 2010 at 8:35 AM, Scott Battaglia < >>> [email protected]> wrote: >>> >>>> All, >>>> >>>> We're pleased to announce CAS 3.4 Release Candidate 1 with the following >>>> features, tasks, and bug fixes: >>>> >>>> * Upgrade to Inspektr 1.0.0-RC2 with new configuration which is more >>>> customizable (also includes cleaner) >>>> * Ticket Generator can now do SAML1 and SAML2 >>>> * Utilize POM DependencyManagement Features >>>> * Experimental Mobile Theme for WebKit browsers >>>> * Spring Framework 3 upgrade >>>> * Spring Web Flow 2 Upgrade >>>> * Switch to Java Validation API and Hibernate Validator >>>> * High Availability Ticket Registry Cleaner >>>> * Improved Logging for Ticket Validation Failures >>>> * Upgrade to Perf4j for performance logging >>>> * Upgrade to OGNL 2.7.3 >>>> * Upgrade to RADIUS Client 1.0.0 >>>> * Upgrade to Spring Security 3 >>>> * Update to casPostResponseView.jsp to work when JavaScript is disabled. >>>> * Fix to allow serverErrorSsoView.jsp to function correctly >>>> * PrincipalNameTransformer interface >>>> * Fix NullPointerException in ThrottledSubmissionHandler for Inspektr >>>> * Improved Logging >>>> * Display messages in Services Management Tool when no services are >>>> registered and WARN to add service management tool >>>> * Fixed assembly.xml to actually include the right files. >>>> >>>> The Release Candidate can be found in our Jasig Repository and from: >>>> http://www.ja-sig.org/downloads/cas/ >>>> >>>> Thanks to Marvin Addison and the Unicon Cooperative Support program for >>>> their assistance in getting this release candidate out. We're hoping to >>>> have the final version out by the conference, so if you can test, please do >>>> so! >>>> >>>> Note that with the library changes, if you've heavily customized your >>>> Spring configuration files OR your Spring Web Flow, I would recommend >>>> reviewing them. I can guarantee your Web Flow 1 flow will fail. >>>> >>>> Cheers, >>>> Scott >>>> >>>> -Scott Battaglia >>>> PGP Public Key Id: 0x383733AA >>>> LinkedIn: http://www.linkedin.com/in/scottbattaglia >>>> >>>> -- >>>> 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-dev >>>> >>>> >>> -- >>> 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-dev >>> >>> >> -- >> 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-dev >> >> > -- > 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-dev > > -- 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-dev
