When XFCC is optional at the load-balancer level, it always adds the XFCC http header which results in the ClientCertificateMapper warning that there's an illegal value. We should have a special case for XFCC header having an empty value as this does not warrant a warning message.
When XFCC is optional at the load-balancer level, it always adds the XFCC http header which results in the ClientCertificateMapper warning that there's an illegal value. We should have a special case for XFCC header having an empty value as this does not warrant a warning message.