<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SSL with different hostname in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122337#M1187849</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sietze,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your answer. I indeed have things working at this moment. Problem was that I performed some previous tests and internet explorer still had some certificates loaded, causing the error messages. As you already mentioned the CN in the certificate should describe the hostname in the url. This brings us to another problem. We would like a smooth transition from the old name serv_01 to sapbw. To prevent lots of service desk calls we would temporary like both urls to point to the same BW system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thus:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://serv01/sap/bw/bex" target="test_blank"&gt;https://serv01/sap/bw/bex&lt;/A&gt;&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;A href="https://sapbw/sap/bw/bex" target="test_blank"&gt;https://sapbw/sap/bw/bex&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To point to the same BW system (with only one server).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, then we would face the CN problem in the certificate. Is there any easy way to make this work? Or should we temporarely install 2 SAP Web Dispatchers on seperate servers, which redirect to the BW system?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Bart.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Jan 2009 14:28:42 GMT</pubDate>
    <dc:creator>BSG</dc:creator>
    <dc:date>2009-01-21T14:28:42Z</dc:date>
    <item>
      <title>SSL with different hostname</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122335#M1187847</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For our SAP BW system running on host serv_01 we would like to use a more functional hostname for the enduser access, e.g. sapbw. For this we have created an alias in the dns: sapbw, pointing to serv_01.&lt;/P&gt;&lt;P&gt;The idea is that end users will then use sapbw in their URLs to access the system, e.g. http(s)://sapbw/sap/bw/BEx in stead of http(s)://serv_01/sap/bw/BEx. For http access this goes fine. However, when using https we encounter certificate problems. Internet explorer is giving certificate errors mentioning that the hostname mentioned in the certificate (probably serv_01?) is not the hostname in the url (sapbw).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did anyone try to use such a functional hostname with an alias to the technical hostname and succeeded in this? Any other ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bart&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jan 2009 13:09:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122335#M1187847</guid>
      <dc:creator>BSG</dc:creator>
      <dc:date>2009-01-21T13:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: SSL with different hostname</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122336#M1187848</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The CN part of the subject must equal the server name. This rule is enforced by all browsers to thwart man-in-the-middle attacks using the DNS and forms an important part of the security SSL (or TLS) offers (although there are always ways around it, of course). So just issue the server a certificate with the correct name and you're done.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jan 2009 13:58:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122336#M1187848</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-21T13:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: SSL with different hostname</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122337#M1187849</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sietze,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your answer. I indeed have things working at this moment. Problem was that I performed some previous tests and internet explorer still had some certificates loaded, causing the error messages. As you already mentioned the CN in the certificate should describe the hostname in the url. This brings us to another problem. We would like a smooth transition from the old name serv_01 to sapbw. To prevent lots of service desk calls we would temporary like both urls to point to the same BW system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thus:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://serv01/sap/bw/bex" target="test_blank"&gt;https://serv01/sap/bw/bex&lt;/A&gt;&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;A href="https://sapbw/sap/bw/bex" target="test_blank"&gt;https://sapbw/sap/bw/bex&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To point to the same BW system (with only one server).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, then we would face the CN problem in the certificate. Is there any easy way to make this work? Or should we temporarely install 2 SAP Web Dispatchers on seperate servers, which redirect to the BW system?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Bart.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jan 2009 14:28:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122337#M1187849</guid>
      <dc:creator>BSG</dc:creator>
      <dc:date>2009-01-21T14:28:42Z</dc:date>
    </item>
    <item>
      <title>Re: SSL with different hostname</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122338#M1187850</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why so hard? Just have an apache server on serv01 that redirects (after a certain period of time) to sapbw. You can then also display a message to users explaining things. Of course, the solution with both web dispatchers will also work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2009 12:58:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122338#M1187850</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-22T12:58:04Z</dc:date>
    </item>
    <item>
      <title>Re: SSL with different hostname</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122339#M1187851</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Decided to use a dns alias.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jun 2009 05:55:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ssl-with-different-hostname/m-p/5122339#M1187851</guid>
      <dc:creator>BSG</dc:creator>
      <dc:date>2009-06-02T05:55:07Z</dc:date>
    </item>
  </channel>
</rss>

