-
Suggestion
-
Resolution: Fixed
Hi folks,
Thanks for your feedback and continued support. We wanted to give you an update on the status of this issue.
Over the medium term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. Exciting development has occurred and is going to continue within this space. This feature is a strong candidate for a future release. We can't promise a specific release, but we'll update the issue when we have more concrete information.
Regards,
Eugene Mak
Atlassian Product Management
http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Spring+Security is written for SS 2.0. Now that 3.0 is out, it needs updating.
Update May 3rd 2012: This is now scheduled in for the next major release, Crowd 2.5. At this stage we don't have an expected release date for 2.5.
[CWD-1807] Spring Security 3.0 Integration tutorial
Thomas Peeters
added a comment - @Joseph Walton
I'm sorry but that link you provided shows config for spring security 2.x. For example:
try and deploy your application to Tomcat with this config in your applicationContext:
<intercept-url pattern="/styles/*" filters="none"/>
You'll notice that this is config for Spring 2.x and NOT spring 3 .
Thomas Peeters
added a comment - @Joseph Walton
I'm sorry but that link you provided shows config for spring security 2.x. For example:
try and deploy your application to Tomcat with this config in your applicationContext:
<intercept-url pattern="/styles/*" filters="none"/>
You'll notice that this is config for Spring 2.x and NOT spring 3 . Integrating Crowd with Spring Security now covers integrating Crowd 2.5 with Spring Security 3.1.
Stefan Lehmann
added a comment - How is the status with 2.4.0? 
Jasper van Veghel
added a comment - 2.3.3 doesn't seem to include the springsecurity-integration in its source code anymore - but with some manual labor I managed to apply the patch to the 2.3.2 sources as well and it's working just fine.
I get that the downside to applying this to trunk would be the loss of 2.5.x support, but those people can just keep using the Crowd <= 2.3.3 libraries no?
For those wanting to use the integration, I've attached my crowdContext.xml file which contains all the Crowd-related beans - they've changed slightly as some packages have moved around and interfaces have changed. I don't use crowd.properties so yours may vary. Other than that, simply add the JAR and POM file to your local repository like so:
mvn install:install-file -DgroupId=com.atlassian.crowd -DartifactId=crowd-integration-client -Dversion=2.3.2-SPRING3 -Dpackaging=jar -Dfile=crowd-integration-client-2.3.2-SPRING3.jar mvn install:install-file -DgroupId=com.atlassian.crowd -DartifactId=crowd-integration-client -Dversion=2.3.2-SPRING3 -Dpackaging=pom -Dfile=crowd-integration-client-2.3.2-SPRING3.pom
Jasper van Veghel
added a comment - 2.3.3 doesn't seem to include the springsecurity-integration in its source code anymore - but with some manual labor I managed to apply the patch to the 2.3.2 sources as well and it's working just fine.
I get that the downside to applying this to trunk would be the loss of 2.5.x support, but those people can just keep using the Crowd <= 2.3.3 libraries no?
For those wanting to use the integration, I've attached my crowdContext.xml file which contains all the Crowd-related beans - they've changed slightly as some packages have moved around and interfaces have changed. I don't use crowd.properties so yours may vary. Other than that, simply add the JAR and POM file to your local repository like so:
mvn install:install-file
-DgroupId=com.atlassian.crowd
-DartifactId=crowd-integration-client
-Dversion=2.3.2-SPRING3
-Dpackaging=jar
-Dfile=crowd-integration-client-2.3.2-SPRING3.jar
mvn install:install-file
-DgroupId=com.atlassian.crowd
-DartifactId=crowd-integration-client
-Dversion=2.3.2-SPRING3
-Dpackaging=pom
-Dfile=crowd-integration-client-2.3.2-SPRING3.pom
Jasper van Veghel
added a comment - For the record - I'm still using this patch with Spring 3.0.5.RELEASE and it's working just fine. I'm not really understanding why it's taking so long to get on the ball with integrating it into a release build.
Jasper van Veghel
added a comment - For the record - I'm still using this patch with Spring 3.0.5.RELEASE and it's working just fine. I'm not really understanding why it's taking so long to get on the ball with integrating it into a release build. 
Alois Cochard
added a comment - In 20 months I leared new languages/frameworks and even actually developing my own IoC container...
So thank you Atlassian, but you are very late on the game now 
Alois Cochard
added a comment - In 20 months I leared new languages/frameworks and even actually developing my own IoC container...
So thank you Atlassian, but you are very late on the game now 
Nick Shaw
added a comment - I'm nothing short of amazed that this has been open for > 20 months. O_O
Has anyone here tried Jasper's patch with spring-security-3.0.5.RELEASE?
Nick Shaw
added a comment - I'm nothing short of amazed that this has been open for > 20 months. O_O
Has anyone here tried Jasper's patch with spring-security-3.0.5.RELEASE? 
john sullivan
added a comment - December 16th, 2009
http://blog.springsource.com/2009/12/16/spring-framework-3-0-goes-ga/
john sullivan
added a comment - December 16th, 2009
http://blog.springsource.com/2009/12/16/spring-framework-3-0-goes-ga/ Wow, what a disappointment. We were > this close < to buying too. Spring 3.x is "not new" anymore.
Thanks, Thomas; the documentation doesn't match at all. I've fixed it to move those unauthenticated resources out into their own <http> elements:
That's what I'm using in the sample applicationContext-security.xml.