-
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
Workflow | Original: JAC Suggestion Workflow [ 3362879 ] | New: JAC Suggestion Workflow 3 [ 3625862 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392476 ] | New: JAC Suggestion Workflow [ 3362879 ] |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 273866 ] | New: Simplified Crowd Development Workflow v2 [ 1392476 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Technical Review [ 10028 ] | New: Resolved [ 5 ] |
Summary | Original: Spring Security 3.0 Integation tutorial | New: Spring Security 3.0 Integration tutorial |
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.