Previously if csrf() was used and subsequently not used, the
TestCsrfTokenRepository was still used. This makes it difficult to test
the actual CsrfTokenRepository implementation.
Now the TestCsrfTokenRepository is only used if explicitly enabled.
Fixes gh-4016
@ -318,13 +318,13 @@ public final class SecurityMockMvcRequestPostProcessors {
@@ -318,13 +318,13 @@ public final class SecurityMockMvcRequestPostProcessors {
@ -367,9 +367,12 @@ public final class SecurityMockMvcRequestPostProcessors {
@@ -367,9 +367,12 @@ public final class SecurityMockMvcRequestPostProcessors {
@ -384,12 +387,30 @@ public final class SecurityMockMvcRequestPostProcessors {
@@ -384,12 +387,30 @@ public final class SecurityMockMvcRequestPostProcessors {
@ -39,7 +39,7 @@ public class SecurityMockMvcRequestBuildersFormLoginTests {
@@ -39,7 +39,7 @@ public class SecurityMockMvcRequestBuildersFormLoginTests {
@ -56,7 +56,7 @@ public class SecurityMockMvcRequestBuildersFormLoginTests {
@@ -56,7 +56,7 @@ public class SecurityMockMvcRequestBuildersFormLoginTests {
@ -37,7 +37,7 @@ public class SecurityMockMvcRequestBuildersFormLogoutTests {
@@ -37,7 +37,7 @@ public class SecurityMockMvcRequestBuildersFormLogoutTests {
@ -50,7 +50,7 @@ public class SecurityMockMvcRequestBuildersFormLogoutTests {
@@ -50,7 +50,7 @@ public class SecurityMockMvcRequestBuildersFormLogoutTests {
@ -143,6 +147,25 @@ public class SecurityMockMvcRequestPostProcessorsCsrfTests {
@@ -143,6 +147,25 @@ public class SecurityMockMvcRequestPostProcessorsCsrfTests {