Rationalize logging names for Metadata Providers

Description

In the metadata provider and filter code there is a mix between

 SAML_LOGCAT ".MetadataProvider."
 SAML_LOGCAT ".MetadataFilter."
 SAML_LOGCAT ".Metadata."

Suggested change is to standardize on Metadata. and add .Filter and .Provider

I think that at the very least we need to get rid of the last 

Environment

None

Activity

Show:

Scott Cantor March 21, 2018 at 7:48 PM

Handlers updated.

Scott Cantor March 21, 2018 at 7:11 PM

I fixed the outlier Metadata categories. My preference is to stick to plugin type names for the categories, so MetadataProvider, AttributeDecoder, etc.

The ones that I might change are the custom handlers. I think Handler.Status would be better than StatusHandler, it's not consistent with that overall practice.

Rod Widdowson March 20, 2018 at 5:40 PM

Apart from the noted above, this is pretty clean

Orphan Category

OpenSSL

 OpenSSL

Metadata Needs cleaned up.  Look for RED

.ArtifactMap
.AssertionValidator
.Config
.Encryption
.EntityMatcher.EntityAttributes
.EntityMatcher.RegistrationAuthority
.MessageDecoder.SAML1
.MessageDecoder.SAML1Artifact
.MessageDecoder.SAML1POST
.MessageDecoder.SAML1SOAP
.MessageDecoder.SAML2
.MessageDecoder.SAML2Artifact
.MessageDecoder.SAML2ECP
.MessageDecoder.SAML2POST
.MessageDecoder.SAML2Redirect
.MessageDecoder.SAML2SOAP
.MessageEncoder.SAML1Artifact
.MessageEncoder.SAML1POST
.MessageEncoder.SAML1SOAP
.MessageEncoder.SAML2Artifact
.MessageEncoder.SAML2ECP
.MessageEncoder.SAML2POST
.MessageEncoder.SAML2Redirect
.MessageEncoder.SAML2SOAP
.Metadata
.Metadata.Chaining
.Metadata.Folder
.MetadataFilter.EntityRoleWhiteList
.MetadataFilter.WhiteList
.MetadataFilter.Signature
.MetadataProvider
.MetadataProvider.Discoverable
.MetadataProvider.Dynamic
.MetadataProvider.LocalDynamic
.MetadataProvider.XML.
.SecurityPolicyRule.AudienceRestriction
.SecurityPolicyRule.BearerConfirmation
.SecurityPolicyRule.ClientCertAuth
.SecurityPolicyRule.Conditions
.SecurityPolicyRule.DelegationRestriction
.SecurityPolicyRule.Ignore
.SecurityPolicyRule.MessageFlow
.SecurityPolicyRule.NullSecurity
.SecurityPolicyRule.SimpleSigning
.SecurityPolicyRule.XMLSigning
.SignatureProfileValidator
.SOAPClient
.Utility.SAMLSign

XmlTooling

Looks pretty innocuous.  Capitalize Curl? (or cUrl, or libCurl).  Nothing I see a need for.

.Config
.CredentialCriteria
.CredentialResolver.Chaining
.CredentialResolver.File
.DataSealer
.Decrypter
.KeyInfoResolver.Inline
.KeyResolver.Inline
.libcurl
.libcurl.InputStream
.Logging
.ParserPool
.PathValidator.PKIX
.ReplayCache
.SecurityHelper
.Signature
.Signature.Debugger
.SOAPClient
.SOAPTransport.CURL
.StorageService
.StorageService.MEMCACHE
.StreamInputSource
.Threads
.TrustEngine.Chaining
.TrustEngine.ExplicitKey
.TrustEngine.PKIX
.TrustEngine.StaticPKIX
.util.CloneInputStream
.XMLHelper
.XMLObject
.XMLObject.Builder
.XMLObject.Signature

Shibboleth

Do we care about AttributeDecoded as opposed to Attribute.Decoder and so forth?  

.AccessControl.Chaining
.AccessControl.XML
.Application
.ArtifactResolution.SAML2
.ArtifactResolver
.AssertionLookup
.Attribute.NameID
.AttributeCheckerHandler
.AttributeDecoder.Base64
.AttributeDecoder.DOM
.AttributeDecoder.KeyInfo
.AttributeDecoder.NameID
.AttributeDecoder.NameIDFromScoped
.AttributeDecoder.Scoped
.AttributeDecoder.String
.AttributeDecoder.XML
.AttributeExtractor.Chaining
.AttributeExtractor.Delegation
.AttributeExtractor.GSSAPI
.AttributeExtractor.XML
.AttributeFilter
.AttributeFilter.Chaining
.AttributeFilter.Dummy
.AttributeResolver.Chaining
.AttributeResolver.CaseFolding
.AttributeResolver.Query
.AttributeResolver.SimpleAggregation
.AttributeResolver.Template
.AttributeResolver.Transform
.AttributeResolverHandler
.Config
.DiscoveryFeed
.ExternalAuth
.Handler
.IPRange
.ISAPI
.Listener
.Logout
.Logout.ADFS
.Logout.SAML2
.LogoutInitiator.ADFS
.LogoutInitiator.Chaining
.LogoutInitiator.Local
.LogoutInitiator.SAML2
.MessageDecoder.ADFS
.MetadataGenerator
.MetadataProvider.Dynamic
.NameIDMgmt.SAML2
.PropertySet
.ProtocolProvider.XML
.RequestMapper
.SecurityPolicyProvider.XML
.ServiceProvider
.SessionCache
.SessionHandler
.SessionInitiator
.SessionInitiator.ADFS
.SessionInitiator.Chaining
.SessionInitiator.Cookie
.SessionInitiator.Form
.SessionInitiator.SAML2
.SessionInitiator.SAMLDS
.SessionInitiator.Shib1
.SessionInitiator.Transform
.SessionInitiator.WAYF
.SOAPClient
.SPRequest
.SSO.ADFS
.SSO.SAML1
.SSO.SAML2
.StatusHandler
.Utilities.ResolverTest
.Utility.MDQuery
.Utility.ResolverTest

 

Rod Widdowson March 20, 2018 at 11:03 AM

Work here is to get a list of the categories we have and circulate it for discussion

Scott Cantor November 12, 2017 at 10:14 PM

I made a quick fix to the one MetadataProvider with an inconsistent category. I'm ok moving the filter categories but in the interest of not making gratuitous changes, rescheduling that for 3.0.

Fixed

Details

Assignee

Reporter

Original estimate

Fix versions

Created November 10, 2017 at 2:45 PM
Updated July 17, 2018 at 1:56 PM
Resolved March 21, 2018 at 7:49 PM