There are two places in the configuration (implemented in NameIDFromScopedAttributeDecoder.cpp and ScopedAttributeDecoder.cpp) where an XML attribute is defined with the name scopeDelimeter. Normal spelling would dictate scopeDelimiter (see, e.g., http://en.wikipedia.org/wiki/Delimiter).
Turns out it's a documentation and code bug, but the schema was correct, so using the wrong spelling wouldn't validate either (and I just turned on validation of a few dependent config files by default).
I used some discretion and decided to change the code to honor the schema.
There are two places in the configuration (implemented in NameIDFromScopedAttributeDecoder.cpp and ScopedAttributeDecoder.cpp) where an XML attribute is defined with the name scopeDelimeter. Normal spelling would dictate scopeDelimiter (see, e.g., http://en.wikipedia.org/wiki/Delimiter).
The incorrect spelling is documented here:
https://spaces.internet2.edu/display/SHIB2/NativeSPAttributeDecoder
So, it's unfortunately part of the public API. On the other hand, I'd be surprised if a lot of people actually used this.
Shades of "REFERER", eh?