Development Notes
Holding Area for comments about SPV3. To be removed before final release
Documentation needing fleshed out
Configuration
Below is a list of configuration elements which still work but are not documented.
legacyOrgNames
deprecation warning addedtype="Chaining"Â
(used internally but not in configuration)
Metadata Filter Synonyms:deprecation warnings added
<BlacklistMetadataFilter>, <Exclude>
(fortype="
BlackList")
<WhitelistMetadataFilter>, <Include>
(for type="WhiteList")<SignatureMetadataFilter>
(for type="SignatureMetadataFilter")
FolderMetadataProvider
Maybe we want to deprecate this in favor of LocalDynamicMetadataProvider
Does not supportÂ
tagsInFeed
?
ISAPI Lets just not mention normal.izeRequests. It's very complicated
We can get the port from the server headers (secuirely)
We can infer the host name from the IIS config
Most people will specify a
<Site>
which takes precedencescheme
inside the<Site>
isn't used
aliases
attribute for the XMLAttributeExtractor and GSSAPIAttributeExtractor
TrustEngine Â
type="chaining"
cacheTimeout
type="chaining"
CredentialCertificate
<CAPath>
Rule Types
valid-user
userÂ
any string valueÂ
(Apache 2.2 and Earlier, Deprecated)
NativeSPSunConfig You gotta be kidding me, right?
Deprecation
RequestMapper "exportStdVars" (property) : A future version of the SP may remove these built-ins in favor of explicit configuration using the Attribute Extractor of type="Assertion"
XMLAccessControl  RuleRegex "ignoreCase
 "
RequestMap HostRegex "ignoreCase
 "
RequestMap PathRegex "ignoreCase
 "