|
To apply the jar file as a patch for your current Crowd release (1.1.0), please do the following:
If you have any problems with these steps, please comment below. /usr/local/crowd $ ./start_crowd.sh
Using CATALINA_BASE: ./apache-tomcat-5.5.20 Using CATALINA_HOME: ./apache-tomcat-5.5.20 Using CATALINA_TMPDIR: ./apache-tomcat-5.5.20/temp Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Home Jun 24, 2007 10:47:19 PM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8095 Jun 24, 2007 10:47:19 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 460 ms Jun 24, 2007 10:47:19 PM org.apache.catalina.realm.JAASRealm setContainer INFO: Set JAAS app name Catalina Jun 24, 2007 10:47:19 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Jun 24, 2007 10:47:19 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.20 Jun 24, 2007 10:47:19 PM org.apache.catalina.core.StandardHost start INFO: XML validation disabled 22:47:22,189 INFO com.atlassian.crowd.startup: Starting Crowd, Version: 1.1.0 (Build:#174 - Jun 22, 2007) *******************************************************************************
22:47:22,246 ERROR org.springframework.web.context.ContextLoader: Context initialization failed *********************************************************************************************
Jun 24, 2007 10:47:27 PM org.apache.coyote.http11.Http11BaseProtocol start I was able to get the sever to start
edit applicationContextImporter.xml (inside crowd-core-1.1.0.jar) comment out csvImporterDAO in the importer factory now the server starts The fix looks like it works in Firefox. I can log into my Rails application and navigate to the Crowd console without logging in. I'm tracking down an issue in Safari. This works in Safari too, as long as I use the external address of the machine.
When I used localhost, Safari used the IPv6 localhost But the Ruby code use the IPv4 localhost So the tokens didn't match. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Originally tokens were Base64 encoded. This encoding scheme can produce characters in the set A-Za-z0-9 and +, =, /, *. The non-alphanumeric characters in the token are stripped out and filled with 0's.