<?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: Synthetic HTTP Monitor domain credential popup. in Synthetic Monitoring</title>
    <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/Synthetic-HTTP-Monitor-domain-credential-popup/m-p/112071#M122</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It's using NTLM authentication. I was able to get it working using a browser monitor setup using our internal gateway which at first I wasn't able to locate, but later I was.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Roy&lt;/P&gt;</description>
    <pubDate>Mon, 04 May 2020 13:12:50 GMT</pubDate>
    <dc:creator>roy_carroll</dc:creator>
    <dc:date>2020-05-04T13:12:50Z</dc:date>
    <item>
      <title>Synthetic HTTP Monitor domain credential popup.</title>
      <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/Synthetic-HTTP-Monitor-domain-credential-popup/m-p/112069#M120</link>
      <description>&lt;P&gt;I have a internal URL that I am trying to setup a Synthetic HTTP Monitor for. The URL is on a separate domain and there is no trust, so I need to be able to supply the domain credentials to access the site when prompted. I tried adding credentials using the set authentication/authorization option with no luck. Confirmed able to browse to the location and supply the credentials in the dialog prompt. Is there a way to pass the necessary domain credentials for the HTTP Monitor? Or a better way to accomplish this?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2020 21:10:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Synthetic-Monitoring/Synthetic-HTTP-Monitor-domain-credential-popup/m-p/112069#M120</guid>
      <dc:creator>roy_carroll</dc:creator>
      <dc:date>2020-04-28T21:10:58Z</dc:date>
    </item>
    <item>
      <title>Re: Synthetic HTTP Monitor domain credential popup.</title>
      <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/Synthetic-HTTP-Monitor-domain-credential-popup/m-p/112070#M121</link>
      <description>&lt;P&gt;Hi Roy,&lt;/P&gt;&lt;P&gt;do you know the type of authentication that is used here? If not, you can try to use a browser monitor and provided the credentials via the basic authentication option. (this should also solve NTLM, Kerberos challenges)&lt;/P&gt;&lt;P&gt;Kind regards, Philipp&lt;/P&gt;</description>
      <pubDate>Mon, 04 May 2020 07:34:41 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Synthetic-Monitoring/Synthetic-HTTP-Monitor-domain-credential-popup/m-p/112070#M121</guid>
      <dc:creator>Philipp_Kastner</dc:creator>
      <dc:date>2020-05-04T07:34:41Z</dc:date>
    </item>
    <item>
      <title>Re: Synthetic HTTP Monitor domain credential popup.</title>
      <link>https://community.dynatrace.com/t5/Synthetic-Monitoring/Synthetic-HTTP-Monitor-domain-credential-popup/m-p/112071#M122</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It's using NTLM authentication. I was able to get it working using a browser monitor setup using our internal gateway which at first I wasn't able to locate, but later I was.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Roy&lt;/P&gt;</description>
      <pubDate>Mon, 04 May 2020 13:12:50 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Synthetic-Monitoring/Synthetic-HTTP-Monitor-domain-credential-popup/m-p/112071#M122</guid>
      <dc:creator>roy_carroll</dc:creator>
      <dc:date>2020-05-04T13:12:50Z</dc:date>
    </item>
  </channel>
</rss>

