<?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>article How Does OS User Application authentication work with the Central Credential Provider? in Secrets Management Articles</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/how-does-os-user-application-authentication-work-with-the/ta-p/1427902</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
How is OS User authentication different between the local credential provider and the Central Credential Provider web service?

&lt;H3&gt;Answer&lt;/H3&gt;
&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;The CCP uses a different mechanism than the local provider to capture the OS user. The difference has more requirements and more limited use cases.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;On the local provider when using OS user as an application authentication restriction the provider uses the process ID of the calling application to look up which user started the process in the process table. At a high level this is the same process for local providers on both Windows and *Nix variants.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;On the CCP OS user is captured using an IIS function known as Windows authentication. On a human interactable web site when opening a new session Windows Authentication will bring the end user to their desired page hosted on IIS without being prompted for a username and password.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="Calibri, sans-serif"&gt;&lt;SPAN style="font-size: 14.6667px;"&gt;The way this works is that when the end user accesses an Windows Authentication protected website their local authentication token is passed to IIS which then verifies the token is valid with Active Directory.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Windows Authentication has more requirements:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;The system making the call to the CCP must be on the same domain as the CCP server&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;The user whose name is specified as OS User must have a domain session on the host they are making the call from. The call must come from this session.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;The method/language making the call to the CPP must support passing the authentication token.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-bottom: 11px;"&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Anonymous Authentication may need to be disabled. (this will restrict the CCP application to only allow Windows Authentication calls)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;In power shell and .Net the “&lt;SPAN style="font-size: 10.0pt;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: &amp;quot;Arial&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: #080707;"&gt;UseDefaultCredentials&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;” property will send the users authentication token when making a REST call.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: &amp;quot;Arial&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: #080707;"&gt;An example rest call in PowerShell that will forward the session token of the user executing the command&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;
&lt;PRE class="ckeditor_codeblock"&gt;
invoke-webrequest -method GET -UseDefaultCredentials -ContentType application/json -uri https://pvwa.taco.day/AIMWebService/api/Accounts?AppID=dave"&amp;amp;"username=bear&lt;/PRE&gt;
&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;</description>
    <pubDate>Tue, 13 Aug 2024 08:02:00 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-08-13T08:02:00Z</dc:date>
    <item>
      <title>How Does OS User Application authentication work with the Central Credential Provider?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/how-does-os-user-application-authentication-work-with-the/ta-p/1427902</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
How is OS User authentication different between the local credential provider and the Central Credential Provider web service?

&lt;H3&gt;Answer&lt;/H3&gt;
&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;The CCP uses a different mechanism than the local provider to capture the OS user. The difference has more requirements and more limited use cases.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;On the local provider when using OS user as an application authentication restriction the provider uses the process ID of the calling application to look up which user started the process in the process table. At a high level this is the same process for local providers on both Windows and *Nix variants.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;On the CCP OS user is captured using an IIS function known as Windows authentication. On a human interactable web site when opening a new session Windows Authentication will bring the end user to their desired page hosted on IIS without being prompted for a username and password.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="Calibri, sans-serif"&gt;&lt;SPAN style="font-size: 14.6667px;"&gt;The way this works is that when the end user accesses an Windows Authentication protected website their local authentication token is passed to IIS which then verifies the token is valid with Active Directory.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Windows Authentication has more requirements:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;The system making the call to the CCP must be on the same domain as the CCP server&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;The user whose name is specified as OS User must have a domain session on the host they are making the call from. The call must come from this session.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;The method/language making the call to the CPP must support passing the authentication token.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-bottom: 11px;"&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Anonymous Authentication may need to be disabled. (this will restrict the CCP application to only allow Windows Authentication calls)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;In power shell and .Net the “&lt;SPAN style="font-size: 10.0pt;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: &amp;quot;Arial&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: #080707;"&gt;UseDefaultCredentials&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;” property will send the users authentication token when making a REST call.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: &amp;quot;Arial&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: #080707;"&gt;An example rest call in PowerShell that will forward the session token of the user executing the command&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;
&lt;PRE class="ckeditor_codeblock"&gt;
invoke-webrequest -method GET -UseDefaultCredentials -ContentType application/json -uri https://pvwa.taco.day/AIMWebService/api/Accounts?AppID=dave"&amp;amp;"username=bear&lt;/PRE&gt;
&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;</description>
      <pubDate>Tue, 13 Aug 2024 08:02:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management-articles/how-does-os-user-application-authentication-work-with-the/ta-p/1427902</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-08-13T08:02:00Z</dc:date>
    </item>
  </channel>
</rss>

