<?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: Certificate Authentication for REST API access in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336682#M161</link>
    <description>Additional screenshots for VEDAuth SSL Settings and Venafi site IIS Certificate Mapping</description>
    <pubDate>Thu, 15 Feb 2024 07:47:01 GMT</pubDate>
    <dc:creator>dghort</dc:creator>
    <dc:date>2024-02-15T07:47:01Z</dc:date>
    <item>
      <title>Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336676#M155</link>
      <description>I am having a little trouble with getting this setup, and I was wondering if there is anyone that might have some insight. I have a dev environment where I am testing this and right now authentication into the web console is through LDAP. From reading about how to setup certificate authentication for the Rest API, I need to toggle Certificate Authentication checkboxin Platforms, then update IIS SSL settings for Aperture and VEDAdmin to Require SSL certificates. The problem with doing this is that it locked me out of the web console immediately. I did not even have an option to put in user/pass credentials. Had to run a query on the DB to clear that. Is there any way to do certificate authentication to get a bearer token for API calls without affecting access to the web console?.</description>
      <pubDate>Wed, 14 Feb 2024 22:07:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336676#M155</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-02-14T22:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336677#M156</link>
      <description>&lt;P&gt;Make sure youre reading the right documentation for how to configure certificate auth for the API. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;It sounds like you followed the doc for configuring it for the Web Console. You do not want to modify Aperture or VEDAdmin IIS settings. The IIS changes should be limited to VEDAuth.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2024 22:07:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336677#M156</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-14T22:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336678#M157</link>
      <description>&lt;P&gt;Make sure youre reading the right documentation for how to configure certificate auth for the API. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;It sounds like you followed the doc for configuring it for the Web Console. You do not want to modify Aperture or VEDAdmin IIS settings. The IIS changes should be limited to VEDAuth.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2024 22:07:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336678#M157</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-14T22:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336679#M158</link>
      <description>&lt;P&gt;Hi dghort, are you trying to enable certificate authentication for Web Console or REST API?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2024 22:07:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336679#M158</guid>
      <dc:creator>ALombardi</dc:creator>
      <dc:date>2024-02-14T22:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336680#M159</link>
      <description>I guess the main question is the URL in the call correct? ''https://tpp.domain.com/vedauth/authorize/certificate The more I read the more it looks like I have to have the web console certificate authentication set up to use this one. I have all of the API Authentication items checked that are necessary.</description>
      <pubDate>Thu, 15 Feb 2024 06:32:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336680#M159</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-02-15T06:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336681#M160</link>
      <description>I guess the main question is the URL in the call correct? ''https://tpp.domain.com/vedauth/authorize/certificate The more I read the more it looks like I have to have the web console certificate authentication set up to use this one. I have all of the API Authentication items checked that are necessary.</description>
      <pubDate>Thu, 15 Feb 2024 06:32:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336681#M160</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-02-15T06:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336682#M161</link>
      <description>Additional screenshots for VEDAuth SSL Settings and Venafi site IIS Certificate Mapping</description>
      <pubDate>Thu, 15 Feb 2024 07:47:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336682#M161</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-02-15T07:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336683#M162</link>
      <description>Well I managed to get to the point where I am no longer getting the Certificate Authentication working. Now it looks like a permissions issue. Getting this Invoke-RestMethod : 403 - Forbidden: Access is denied. Server Error   403 - Forbidden: Access is denied.  You do not have permission to view this directory or page using the credentials that you supplied.  Not sure what on the certificate might be a problem. Is there a specific scope I need to usein order to make this work?</description>
      <pubDate>Thu, 15 Feb 2024 08:02:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336683#M162</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-02-15T08:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336684#M163</link>
      <description>The good news is that I have figured out my own problem. I am posting it here for reference in case anyone else runs into the problem. Somehow the Venafi Operational Certificate that was created from our internal CAafter the initial install was in place in the Trusted Root store in addition to the Personal store. I essentially moved that to the Intermediate store and it started producing a token. This main issue is that the Trusted Root store should ONLY contain self-signed certificates. Having a signed certificate in the Trusted Root store caused my issue. Running this script in Powershell will find all certificates that are not self-signed which you can then move accordingly. Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File 'c:\computer_filtered.txt'</description>
      <pubDate>Fri, 16 Feb 2024 09:56:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336684#M163</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-02-16T09:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336685#M164</link>
      <description>The good news is that I have figured out my own problem. I am posting it here for reference in case anyone else runs into the problem. Somehow the Venafi Operational Certificate that was created from our internal CAafter the initial install was in place in the Trusted Root store in addition to the Personal store. I essentially moved that to the Intermediate store and it started producing a token. This main issue is that the Trusted Root store should ONLY contain self-signed certificates. Having a signed certificate in the Trusted Root store caused my issue. Running this script in Powershell will find all certificates that are not self-signed which you can then move accordingly. Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File 'c:\computer_filtered.txt'</description>
      <pubDate>Fri, 16 Feb 2024 09:56:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336685#M164</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-02-16T09:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336686#M165</link>
      <description>Thank you for following up with your findings @dghort !</description>
      <pubDate>Fri, 16 Feb 2024 16:01:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336686#M165</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-16T16:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Authentication for REST API access</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336687#M166</link>
      <description>Thank you for following up with your findings @dghort !</description>
      <pubDate>Fri, 16 Feb 2024 16:01:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-authentication-for-rest-api-access/m-p/1336687#M166</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-16T16:01:29Z</dc:date>
    </item>
  </channel>
</rss>

