https://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-comen-USTelligent Community 12https://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-comThu, 14 Nov 2019 05:36:31 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:48c7b97a-acf6-4425-b5f1-e1634795c481Parmida Borhanihttps://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-com#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 11/14/2019 5:36:31 AM<br /> <h2 class="name">Symptoms</h2> <div class="content"> <p><span>When testing an integration with an HTTPS endpoint using the IP address, users may see the following error:</span></p> <pre>Failed to connect to https://&lt;IP_ADDRESS&gt;/example/endpoint/etc<br />Host name &#39;&lt;IP_ADDRESS&gt;&#39; does not match the certificate subject provided by the peer (CN=sample.fqdn.com, O=Organization, L=Location, ST=State, C=Country)</pre> <p>This can happen even when the certificate has been added as a client certificate in the Administration Console.</p> <h2><span>Cause</span></h2> <p><span>The IP address has not been added to the certificate as an <code>IPAddress</code> attribute under the <code>SubjectAltName</code>&nbsp;section of the certificate. Note that adding the IP address as a <code>DNSName</code> attribute does not work.</span></p> <h2><span>Action</span></h2> <p><span>Add the IP address as an <code>IPAddress</code> attribute&nbsp;under the&nbsp;<code>SubjectAltName</code>&nbsp;section of the certificate, then upload the new certificate to the Administration Console Client Certificate store.</span></p> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian.</span></p> <p><span>Last Reviewed: November 2019</span></p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: integrations, integration, how-to, web services, Certificate, Certificates, SSL</div> https://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-com/revision/3Tue, 12 Nov 2019 08:58:59 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:48c7b97a-acf6-4425-b5f1-e1634795c481Sean Kimhttps://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-com#commentsRevision 3 posted to Appian Knowledge Base by Sean Kim on 11/12/2019 8:58:59 AM<br /> <h2 class="name">Symptoms</h2> <div class="content"> <p><span>When testing an integration with an HTTPS endpoint using the IP address, users may see the following error:</span></p> <pre>Failed to connect to https://&lt;IP_ADDRESS&gt;/example/endpoint/etc<br />Host name &#39;&lt;IP_ADDRESS&gt;&#39; does not match the certificate subject provided by the peer (CN=sample.fqdn.com, O=Organization, L=Location, ST=State, C=Country)</pre> <p>This can happen even when the certificate has been added as a client certificate in the Administration Console.</p> <h2><span>Cause</span></h2> <p><span>The IP address has not been added to the certificate as an <code>IPAddress</code> attribute under the <code>SubjectAltName</code>&nbsp;section of the certificate. Note that adding the IP address as a <code>DNSName</code> attribute does not work.</span></p> <h2><span>Action</span></h2> <p><span>Add the IP address as an <code>IPAddress</code> attribute&nbsp;under the&nbsp;<code>SubjectAltName</code>&nbsp;section of the certificate, then upload the new certificate to the Administration Console Client Certificate store.</span></p> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian.</span></p> <p><span>Last Reviewed: November 2019</span></p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: integrations, integration, how-to, web services, Certificate, Certificates, SSL</div> https://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-com/revision/2Mon, 11 Nov 2019 15:11:04 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:48c7b97a-acf6-4425-b5f1-e1634795c481Sean Kimhttps://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-com#commentsRevision 2 posted to Appian Knowledge Base by Sean Kim on 11/11/2019 3:11:04 PM<br /> <h1 class="name"></h1> <div class="content"> <h2><span>Symptoms</span></h2> <p><span>When testing an integration with an HTTPS endpoint using the IP Address, users may see the following error:</span></p> <code><span>Failed to connect to https://&lt;IP_ADDRESS&gt;/example/endpoint/etc</span></code><br /><span><code>Host name &#39;&lt;IP_ADDRESS&gt;&#39; does not match the certificate subject provided by the peer (CN=sample.fqdn.com, O=Organization, L=Location, ST=State, C=Country)</code><br /><br />This can happen even when the certificate has been added as a client certificate in the Administration Console.</span> <h2><span>Cause</span></h2> <p><span>The IP address has not been added to the certificate as an <code>IPAddress</code> attribute under the <code>SubjectAltName</code>&nbsp;section of the certificate. Note that adding the IP address as a <code>DNSName</code> attribute does not work.</span></p> <h2><span>Action</span></h2> <p><span>Add the IP Address as an <code>IPAddress</code> attribute&nbsp;under the&nbsp;<code>SubjectAltName</code>&nbsp;section of the certificate, then upload the new certificate to the Administration Console Client Certificate store.</span></p> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian.</span></p> <p><span>Last Reviewed: Nov 2019</span></p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: integrations, integration, how-to, web services, Certificate, Certificates, SSL</div> https://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-com/revision/1Mon, 11 Nov 2019 15:10:44 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:48c7b97a-acf6-4425-b5f1-e1634795c481Sean Kimhttps://community.appian.com/support/w/kb/1592/kb-2020-host-name-does-not-match-the-certificate-subject-provided-by-the-peer-cn-customer-endpoint-com#commentsRevision 1 posted to Appian Knowledge Base by Sean Kim on 11/11/2019 3:10:44 PM<br /> <h1 class="name"></h1> <div class="content"> <h2><span>Symptoms</span></h2> <p><span>When testing an integration with an HTTPS endpoint using the IP Address, users may see the following error:</span></p> <code><span>Failed to connect to https://&lt;IP_ADDRESS&gt;/example/endpoint/etc</span></code><br /><span><code>Host name &#39;&lt;IP_ADDRESS&gt;&#39; does not match the certificate subject provided by the peer (CN=sample.fqdn.com, O=Organization, L=Location, ST=State, C=Country)</code><br /><br />This can happen even when the certificate has been added as a client certificate in the Administration Console.</span> <h2><span>Cause</span></h2> <p><span>The IP address has not been added to the certificate as an <code>IPAddress</code> attribute under the <code>SubjectAltName</code>&nbsp;section of the certificate. Note that adding the IP address as a <code>DNSName</code> attribute does not work.</span></p> <h2><span>Action</span></h2> <p><span>Add the IP Address as an <code>IPAddress</code> attribute&nbsp;under the&nbsp;<code>SubjectAltName</code>&nbsp;section of the certificate, then upload the new certificate to the Administration Console Client Certificate store.</span></p> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian.</span></p> <p><span>Last Reviewed: Nov 2019</span></p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: integrations, integration, how-to, web services, Certificate, Certificates, SSL</div>