Spring Security
  1. Spring Security
  2. SEC-1348

Spring Security 3 Schema refences enumeration that differs when you start application

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.1
    • Component/s: Namespace
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Scott Battaglia added a comment -

        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?

        Show
        Scott Battaglia added a comment - 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?
        Hide
        Luke Taylor added a comment -

        No, I guess jetbrains must be using a milestone version of the 3.0 schema.

        Show
        Luke Taylor added a comment - No, I guess jetbrains must be using a milestone version of the 3.0 schema.

          People

          • Assignee:
            Scott Battaglia
            Reporter:
            Scott Battaglia
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: