<?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: website mointoring in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480405#M59057</link>
    <description>&lt;P&gt;For the external, make sure a firewall is not blocking connections. Typically, you would use a proxy to connect to external websites from within an organization&lt;/P&gt;

&lt;P&gt;For internal, ensure you have the right authorization headers. Typically organizations have LDAP or SAML authentication set up. This might be blocking your requests since the system is unable to authorize you.&lt;/P&gt;

&lt;P&gt;Since I have no idea how your systems are setup, not sure if I can help beyond the above guesses.&lt;/P&gt;</description>
    <pubDate>Sun, 10 Nov 2019 12:16:46 GMT</pubDate>
    <dc:creator>arjunpkishore5</dc:creator>
    <dc:date>2019-11-10T12:16:46Z</dc:date>
    <item>
      <title>website mointoring</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480404#M59056</link>
      <description>&lt;P&gt;Hi &lt;BR /&gt;
we have two types of web portals. Internal and external. Internal are only for our employees and exteranals are for specific people to access from remote location.&lt;/P&gt;

&lt;P&gt;In the status Overview Page, &lt;BR /&gt;
for Internal Portal, the reponse is 401.&lt;/P&gt;

&lt;P&gt;and for External Portal the response is "502"&lt;/P&gt;

&lt;P&gt;&lt;IMG src="https://community.splunk.com/storage/temp/276052-error2.jpg" alt="alt text" /&gt;&lt;/P&gt;

&lt;P&gt;from _internal logs: &lt;BR /&gt;
index=_internal sourcetype="web_availability_modular_input" auth_type&lt;BR /&gt;
&lt;IMG src="https://community.splunk.com/storage/temp/276051-error1.jpg" alt="alt text" /&gt;&lt;/P&gt;

&lt;P&gt;Please support.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:54:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480404#M59056</guid>
      <dc:creator>riqbal47010</dc:creator>
      <dc:date>2020-09-30T02:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: website mointoring</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480405#M59057</link>
      <description>&lt;P&gt;For the external, make sure a firewall is not blocking connections. Typically, you would use a proxy to connect to external websites from within an organization&lt;/P&gt;

&lt;P&gt;For internal, ensure you have the right authorization headers. Typically organizations have LDAP or SAML authentication set up. This might be blocking your requests since the system is unable to authorize you.&lt;/P&gt;

&lt;P&gt;Since I have no idea how your systems are setup, not sure if I can help beyond the above guesses.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2019 12:16:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480405#M59057</guid>
      <dc:creator>arjunpkishore5</dc:creator>
      <dc:date>2019-11-10T12:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: website mointoring</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480406#M59058</link>
      <description>&lt;P&gt;HI&lt;BR /&gt;
thanks for your response.&lt;/P&gt;

&lt;P&gt;when I put the full URL for external the response goes green with code=20 &lt;/P&gt;

&lt;P&gt;we are using LDAP authentication and I am pretty sure that it is the basic cause for blocking the request. can you please share the step for LDAP authorization. .&lt;BR /&gt;
I used curl command with proxy and user credentaill but still using the error code 401&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2019 13:00:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480406#M59058</guid>
      <dc:creator>riqbal47010</dc:creator>
      <dc:date>2019-11-10T13:00:48Z</dc:date>
    </item>
    <item>
      <title>Re: website mointoring</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480407#M59059</link>
      <description>&lt;P&gt;You'll have to check with the LDAP admin on the type of authentication headers needed. With curl, you can try some of the available methods to figure out - &lt;A href="https://ec.haxx.se/http-auth.html"&gt;https://ec.haxx.se/http-auth.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2019 22:54:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480407#M59059</guid>
      <dc:creator>arjunpkishore5</dc:creator>
      <dc:date>2019-11-10T22:54:10Z</dc:date>
    </item>
    <item>
      <title>Re: website mointoring</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480408#M59060</link>
      <description>&lt;P&gt;sorry I lost in between.&lt;/P&gt;

&lt;P&gt;As per AD admin we are using kerberos authentication whereas I link the available authentication methods are digest,negotiate and ntlm.&lt;/P&gt;

&lt;P&gt;beside this how can we fix this issue from app side.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Nov 2019 05:54:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/website-mointoring/m-p/480408#M59060</guid>
      <dc:creator>riqbal47010</dc:creator>
      <dc:date>2019-11-11T05:54:03Z</dc:date>
    </item>
  </channel>
</rss>

