Generic error for Common Name mismatch

[somdev]

Hi @dchiesa1

I have added common name check for a target server like this(during the target server creation):

{
"name": "common-name-test",
"host": "(URL Removed by Staff)",
"isEnabled": true,
"port": "443",
"sSLInfo": {
"commonName": {
"value": "*.example.com",
"wildcardMatch": true
},
"enabled": true
}
}

The cert's cname does not match this value, so the proxy is throwing an error but it's a generic '500 Internal Server Error' "errorcode": "messaging.adaptors.http.flow.InternalServerError" } }

This is happening when cname is added at target server level.

But when SSLInfo is added at the target endpoint(proxy level), like this:

<HTTPTargetConnection>
<SSLInfo>
<Enabled>true</Enabled>
<CommonName wildcardMatch="true">*.example.com</CommonName>
</SSLInfo>
<URL>(URL Removed by Staff)</URL>
</HTTPTargetConnection>

Since CN doesn't match, it's throwing error as below, which is easier to understand:

{
"fault": {
"faultstring": "Common-Name mismatch",
"detail": {
"errorcode": "protocol.http.CommonNameMismatch"
}
}
}

Is there any reason why it's behaving differently in case of Target server? Can same kind of unique error be provided in the first case(target server) too or at least any error variable to identify it's because of CN check failure?

[somdev]

Hi @dchiesa1 ,

Any suggestion on this please?

[dchiesa1]

I don;'t know why it's different.

I suggest you open a support case and have them create a bug on your behalf.  Yours seems a reasonable request, from my perspective. 

There's no guarantee the bug will be accepted, and that the engineering team will work on it quickly, and of course you wouldn't be able to count on getting that fix soon.  but you can ask.