Customer required help to get this working on there own - leading to unnecessary support ticket. This was basically just getting the API url correct with XSOAR documentation alone. It appears API URL will vary customer by customer, depending on what tenant they are on. They were confused why they kept getting Auth Failure log in testing integration, and created unnecessary support case and troubleshooting session.
Hi and welcome to our Content Developer Docs project!
Thanks and congrats for opening your very first issue.
If you know the fix, you may also submit a PR to fix the issue if you like!
Describe the problem
Customer required help to get this working on there own - leading to unnecessary support ticket. This was basically just getting the API url correct with XSOAR documentation alone. It appears API URL will vary customer by customer, depending on what tenant they are on. They were confused why they kept getting Auth Failure log in testing integration, and created unnecessary support case and troubleshooting session.
Environment
n/a
Suggested fix
I suggesting adding this link to our docs will avoid this in future: https://api.docs.prismacloud.io/reference -> add here: https://xsoar.pan.dev/docs/reference/integrations/red-lock.
Maybe also be good add link to to the Prisma guide on creating a key for convenience: https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin/manage-prisma-cloud-administrators/create-access-keys.html