We have three tests that depend on some Spring Security internals and, as a result, they're quite brittle. They currently depend on values being captured by a lambda. This capturing changed in https://github.com/spring-projects/spring-security/commit/c4e9fb885db0f5813317a56d2455aeb96b08e4d9 which broke the tests. e70226b48e3e3f00eca216ba35b26f90db2049ef has aligned the tests with the changes to Spring Security for now. It would be good to test things in a more robust way that does not rely on reflective property or field extraction.
Comment From: wilkinsona
Without adding public API to Spring Security, which would be hard to justify, I don't think there's anything we can do here.