Page Comparison

...

Documentation needing fleshed out

AlgorithmWhitelist

...

Configuration

Below is a list of configuration elements which still work but are not documented.

• MetadataProvider:

  • legacyOrgNames deprecation warning added

  • type="Chaining" (used internally but not in configuration)

• Metadata Filter Synonyms:deprecation warnings added

  • <BlacklistMetadataFilter>, <Exclude> (for type="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 precedence

  • scheme inside the <Site> isn't used

• AttributeExtractor - 
  

  • Chaining

  • aliases attribute for the XMLAttributeExtractor and GSSAPIAttributeExtractor

• Attribute Resolver

  • Chaining

• SPConfig

  • <SecurityPolicies>

• Policy
  

  • Rule

• TrustEngine  type="chaining"

• SessionCache
  

  • cacheTimeout

• CredentialResolver

  • type="chaining"

  • FileCredentialResolver 
    

    • CredentialCertificate <CAPath>

• Apache
  

  • Rule Types
    

    • valid-user

      user 

    • user 
      

    • any string value (Apache 2.2 and Earlier, Deprecated)

• NativeSPSunConfig You gotta be kidding me, right?

...

RequestMapper "exportStdVars" (property) : A  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 "

...