<?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: Is the default Ansible API Integration not viable? in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336796#M176</link>
    <description>Hey @dghort could you let me know what version of TPP you are running? Could you also confirm what action(s) you were running with the Ansible, assuming you have pulled in the Venafi collection? (https://github.com/Venafi/ansible-collection-venafi) This certainly is not the intended behaviour. Once a user is assigned, you should then have the permissions as described in this application integration: certificate:manage,revoke;configuration:manage Base access has no users</description>
    <pubDate>Tue, 08 Oct 2024 09:30:41 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-10-08T09:30:41Z</dc:date>
    <item>
      <title>Is the default Ansible API Integration not viable?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336794#M174</link>
      <description>I was setting up theVenafi Role for Red Hat Ansible with the client ID of ansible-by-venafi for testing, and not matter which user I added, even a Master Admin, it would state the user didnt have permission for the scope used. The scope was exactly the same as what was listed for the integration. I exported it, deleted it, and creating a new one with all the same parameters with the exception of the Vendor field (Venafi, Inc.), and it worked immediately. Does this particular integration in the on-prem TPP not work unless you do this? I should say that the hashicorp-terraform-by-venafi integration did not have this problem when I set it up. It seems limited to just the Ansible one. Has anyone else run into this?.</description>
      <pubDate>Wed, 11 Sep 2024 13:09:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336794#M174</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-09-11T13:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: Is the default Ansible API Integration not viable?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336795#M175</link>
      <description>Hi @dghort , Thank You for Your Patience! We appreciate your question and apologize for the delay in our response. Rest assured, you should be receiving an answer shortly from one of our Venafi Team Members.</description>
      <pubDate>Thu, 26 Sep 2024 06:50:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336795#M175</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-09-26T06:50:53Z</dc:date>
    </item>
    <item>
      <title>Re: Is the default Ansible API Integration not viable?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336796#M176</link>
      <description>Hey @dghort could you let me know what version of TPP you are running? Could you also confirm what action(s) you were running with the Ansible, assuming you have pulled in the Venafi collection? (https://github.com/Venafi/ansible-collection-venafi) This certainly is not the intended behaviour. Once a user is assigned, you should then have the permissions as described in this application integration: certificate:manage,revoke;configuration:manage Base access has no users</description>
      <pubDate>Tue, 08 Oct 2024 09:30:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336796#M176</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-10-08T09:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: Is the default Ansible API Integration not viable?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336797#M177</link>
      <description>Hey @dghort could you let me know what version of TPP you are running? Could you also confirm what action(s) you were running with the Ansible, assuming you have pulled in the Venafi collection? (https://github.com/Venafi/ansible-collection-venafi) This certainly is not the intended behaviour. Once a user is assigned, you should then have the permissions as described in this application integration: certificate:manage,revoke;configuration:manage Base access has no users</description>
      <pubDate>Tue, 08 Oct 2024 09:30:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336797#M177</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-10-08T09:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: Is the default Ansible API Integration not viable?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336798#M178</link>
      <description>Well I am on the latest version now. It appears as if the default integration is back as it was before, and it seems that I can use it properly. Not sure what the deal was before honestly, but thanks for checking it out for me.</description>
      <pubDate>Mon, 16 Dec 2024 07:18:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/is-the-default-ansible-api-integration-not-viable/m-p/1336798#M178</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-12-16T07:18:47Z</dc:date>
    </item>
  </channel>
</rss>

