Uploaded image for project: 'OpenSAML - Java'
  1. OpenSAML - Java
  2. OSJ-293

Consider strict mode to reject unexpected content

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 5.0.0
    • Component/s: Core Classes
    • Labels:
      None

      Description

      The traditional behavior of the unmarshallers is to ignore unxpected content, with the default base class supplying empty non-throwing versions of attribute and element processing.

      I think this is dangerous as a default, and think it's worth considering whether to have a toggleable property to enable more strict behavior that raises exceptions when content that's explicitly disallowed appears where it shouldn't. I think that's mostly in the base class, frankly, and not a huge change.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              putmanb@shibboleth.net Brent Putman
              Reporter:
              cantor.2@osu.edu Scott Cantor
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 15 minutes
                  15m