I updated this branch to use the newly released Spring Security 3.2.6.RELEASE. Had to tweak some test dependencies so that CassandraWebTests would still work
See the comments in the PR. I think we should rather have test cases on the HTTP level rather than on the repository because otherwise it raises the question, why the test cases are actually present in Spring Data REST
Retooled the test cases to use MockMvc. Took a bit of work since the APIs for Mock testing with Spring Security had big changes. But now it all works perfectly
Greg Turnquist opened DATAREST-397 and commented
We need test cases that prove Spring Security's annotations work at all levels as expected when controlling access to repository methods.
The task of filtering/not filtering metadata is not part of this task and is being analyzed separately in https://docs.google.com/a/pivotal.io/document/d/19fAbS90tZ_so88bf97PZCM_OHziX9WDD0UNJTQ8d2dg/edit
Issue Links:
SEC-2150 Annotating at class level does not protected Spring Data Repositories methods that are not overriden
("depends on")
DATAREST-15 Support using basic authentication with Spring Security
("is depended on by")
DATAREST-14 Document use of Spring Security to recure resources
("is depended on by")
DATAREST-454 Add section documenting conditional operations
("is depended on by")
DATAREST-289 Spring Security + Spring Data REST: HTTP 400 instead of 403
DATAREST-18 Support using OAuth-2 authentication with Spring Security/Spring OAuth
("supersedes")
Referenced from: pull request #171
The text was updated successfully, but these errors were encountered: