<?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: Log on to e FQDN in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/log-on-to-e-fqdn/m-p/1345170#M2542</link>
    <description>&lt;P&gt;Hi @Tiago Toledo​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ‘address’ filed is used to specify the target host name whereas ‘logon to’ field is used to specify the name of the domain where target account will be used. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;To answer your first question:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CyberArk uses the “log on to” field to direct the authentication request to the correct context, ensuring that the username and password are validated against the intended domain. This allows for more flexible configurations where the address might differ from the authentication context, especially in complex network environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;To answer your second question: &lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In a controlled lab environment, DNS resolution and domain relationships are might be straightforward. The FQDN might correctly resolve and authenticate without issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There could be few causes here&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Depending on the LAB setup,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;DNS resolution might differ. The system might interpret the FQDN differently in the “log on to” field, leading to authentication error.&lt;/LI&gt;&lt;LI&gt;The Active Directory structures can cause variations in how authentication requests are processed.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 20 Jun 2024 00:20:55 GMT</pubDate>
    <dc:creator>M.Vora780263</dc:creator>
    <dc:date>2024-06-20T00:20:55Z</dc:date>
    <item>
      <title>Log on to e FQDN</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/log-on-to-e-fqdn/m-p/1345169#M2541</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Two questions:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) When we onboard a local account, we put the FQDN of the target server in the "address" field and we also put it in the "log on to" field. Why isn't the "address" field used to make a connection?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) In my lab I made this configuration using FQDN in both fields and it worked fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In another environment, I replicated this configuration and access did not work. Starts connection and gives username and password error.&lt;/P&gt;&lt;P&gt;We removed the FQDN from the "log on to" field, leaving only the hostname and it worked, very WEIRD. Has anyone ever seen something like this?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2024 17:47:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/log-on-to-e-fqdn/m-p/1345169#M2541</guid>
      <dc:creator>tiago.faria</dc:creator>
      <dc:date>2024-06-19T17:47:49Z</dc:date>
    </item>
    <item>
      <title>Re: Log on to e FQDN</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/log-on-to-e-fqdn/m-p/1345170#M2542</link>
      <description>&lt;P&gt;Hi @Tiago Toledo​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ‘address’ filed is used to specify the target host name whereas ‘logon to’ field is used to specify the name of the domain where target account will be used. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;To answer your first question:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CyberArk uses the “log on to” field to direct the authentication request to the correct context, ensuring that the username and password are validated against the intended domain. This allows for more flexible configurations where the address might differ from the authentication context, especially in complex network environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;To answer your second question: &lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In a controlled lab environment, DNS resolution and domain relationships are might be straightforward. The FQDN might correctly resolve and authenticate without issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There could be few causes here&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Depending on the LAB setup,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;DNS resolution might differ. The system might interpret the FQDN differently in the “log on to” field, leading to authentication error.&lt;/LI&gt;&lt;LI&gt;The Active Directory structures can cause variations in how authentication requests are processed.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2024 00:20:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/log-on-to-e-fqdn/m-p/1345170#M2542</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2024-06-20T00:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: Log on to e FQDN</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/log-on-to-e-fqdn/m-p/1345171#M2543</link>
      <description>&lt;P&gt;Thank you for answering. &lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2024 13:40:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/log-on-to-e-fqdn/m-p/1345171#M2543</guid>
      <dc:creator>tiago.faria</dc:creator>
      <dc:date>2024-06-20T13:40:54Z</dc:date>
    </item>
  </channel>
</rss>

