SecureChannelProcessor and InSecureChannelProcessor alway return false in support method call

Summary

I used the configuration from the current documentation, slightly modified it:

/sec:filter-security-metadata-source

Actual Behavior

On application start I get an exception: Unsupported configuration attributes: [REQUIRES_SECURE_CHANNEL, REQUIRES_INSECURE_CHANNEL, REQUIRES_SECURE_CHANNEL]

I think it's a bug in the support method of both SecureChannelProcessor and InSecureChannelProcessor:

public boolean supports(ConfigAttribute attribute) {
    return (attribute != null) && (attribute.getAttribute() != null)
            && attribute.getAttribute().equals(getSecureKeyword());
}

because (attribute.getAttribute() != null) always returns false

Expected Behavior

Configuration

Version

Sample

Read SecureChannelProcessor and InsecureChannelProcessor, focusing on their supports(ConfigAttribute) methods and the channel configuration shown in the issue. Reproduce the startup failure with the provided REQUIRES_SECURE_CHANNEL and REQUIRES_INSECURE_CHANNEL attributes, then verify that the completed change recognizes the intended attributes without reporting them as unsupported.