<?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 Can http Access be Disabled in WFA? in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26648#M5559</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IHAC who's using https for WFA and would like to disable http access for internal IT audit reasons. Is there currently any way to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:31:29 GMT</pubDate>
    <dc:creator>jpierson</dc:creator>
    <dc:date>2025-06-05T05:31:29Z</dc:date>
    <item>
      <title>Can http Access be Disabled in WFA?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26648#M5559</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IHAC who's using https for WFA and would like to disable http access for internal IT audit reasons. Is there currently any way to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:31:29 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26648#M5559</guid>
      <dc:creator>jpierson</dc:creator>
      <dc:date>2025-06-05T05:31:29Z</dc:date>
    </item>
    <item>
      <title>Re: Can http Access be Disabled in WFA?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26653#M5560</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;http on WFA can be disabled for the external access of WFA server i.e. access using IP or Hostname. Access of WFA using "localhost" over http will still work and its also required by WFA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How? It depends on your WFA vesion. What is the WFA version you are using?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jul 2014 12:29:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26653#M5560</guid>
      <dc:creator>sinhaa</dc:creator>
      <dc:date>2014-07-31T12:29:05Z</dc:date>
    </item>
    <item>
      <title>Re: Can http Access be Disabled in WFA?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26657#M5561</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Customer is using two versions; &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;2.0 for 7-mode and &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;2.2 for cDOT&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jul 2014 13:28:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26657#M5561</guid>
      <dc:creator>jpierson</dc:creator>
      <dc:date>2014-07-31T13:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: Can http Access be Disabled in WFA?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26662#M5562</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For 2.0&lt;/P&gt;&lt;P&gt;====&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;Steps&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1. Open the Windows services console by using services.msc and stop the NetApp WFA Server &lt;/SPAN&gt;&lt;SPAN style="color: black; font-family: 'Courier New'; font-size: 10pt; line-height: 1.5em;"&gt;service.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2. Edit the server.xml file:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a) Open the server.xml file from the following location using an XML editor such as Notepad&lt;/SPAN&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;++: &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;c:\Program Files\NetApp\WFA\jboss\server\default\deploy&lt;/SPAN&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;\jbossweb.sar&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; b) Locate the following element: &amp;lt;Connector protocol="HTTP/1.1" port="$&lt;/SPAN&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;{http.port}" address="&lt;SPAN style="color: #ff0000;"&gt;${jboss.bind.address}&lt;/SPAN&gt;" connectionTimeout="20000" &lt;/SPAN&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;redirectPort="${https.port}" maxSavePostSize="-1"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;restrictedUserAgents="^.*MS Web Services Client Protocol.*$" /&amp;gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; c) Replace "${jboss.bind.address}" with &lt;SPAN style="color: #008000;"&gt;"127.0.0.1"&lt;/SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; d) Save the server.xml file.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Courier New'; color: black;"&gt;3. Restart the NetApp WFA Server service.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For 2.2 &lt;/P&gt;&lt;P&gt;======&lt;/P&gt;&lt;P&gt;See the installation and setup guide &lt;A href="https://library.netapp.com/ecm/ecm_get_file/ECMP1397247" title="https://library.netapp.com/ecm/ecm_get_file/ECMP1397247" target="_blank"&gt;https://library.netapp.com/ecm/ecm_get_file/ECMP1397247&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Page 29.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sinhaa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jul 2014 17:55:16 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26662#M5562</guid>
      <dc:creator>sinhaa</dc:creator>
      <dc:date>2014-07-31T17:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: Can http Access be Disabled in WFA?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26671#M5563</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you very much sinhaa. Do you have any detail as to why http access is still needed using "localhost" and we can't simply stop the http port from listening? I know I'm going to be asked that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jul 2014 21:15:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26671#M5563</guid>
      <dc:creator>jpierson</dc:creator>
      <dc:date>2014-07-31T21:15:49Z</dc:date>
    </item>
    <item>
      <title>Re: Can http Access be Disabled in WFA?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26676#M5564</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;WFA cmdlets like Get-WfaLogger etc internally make rest call using localhost on http. Other job executors also use http on localhost. This is by design. So if the http port is disabled, WFA server willsure&amp;nbsp; come up and you can login too, but you can't do anything useful with it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sinhaa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Aug 2014 12:40:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26676#M5564</guid>
      <dc:creator>sinhaa</dc:creator>
      <dc:date>2014-08-03T12:40:05Z</dc:date>
    </item>
    <item>
      <title>Re: Can http Access be Disabled in WFA?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26684#M5565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sinhaa. Appreciate the additional explanation. Thanks for all your help!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Aug 2014 10:19:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Can-http-Access-be-Disabled-in-WFA/m-p/26684#M5565</guid>
      <dc:creator>jpierson</dc:creator>
      <dc:date>2014-08-07T10:19:21Z</dc:date>
    </item>
  </channel>
</rss>

