Scott Battaglia (Migrated from SEC-1348) said:
The Spring Security 3 schema says the value for the custom-filter should be (for example) "CAS_PROCESSING_FILTER" but if you start the application up using that it fails. It wants CAS_FILTER (which is what the sample application uses). This confuses IntelliJ which parses the Schema definition.
Scott Battaglia said:
Apparently IntelliJ has an earlier version of the file as part of its plugin. Its not using the one from the web server. So I'm not sure where an issue should be opened. With IntelliJ, or does Spring maintain that support?
Luke Taylor said:
No, I guess jetbrains must be using a milestone version of the 3.0 schema.