Prisma Cloud Integration Instance authorization failure - failed to parse login error: readObjectStart: expect { or n, but found <
Symptom
• The integration instance displayed the status "Authorization Failure".
• Generated new access key in Prisma Cloud with different permission levels, the integration still failed.
• The test command executed in the playground, `!prismacloud_instancename-test-module debug-mode=true`, generated an authentication token from the Prisma Cloud API without any visible errors.
Environment
Cortex XSIAM
Cortex XDR
Cause
The customer was using the incorrect Prisma Cloud API URL. The documentation provided the URL for the Prisma Cloud Admin Console, `https://app3.prismacloud.io`, which wasn't the correct one for integration purposes.
Resolution
In this Prisma Cloud API URL article
The Domain URL is separated into "Prisma Cloud Admin Console URL" and "Prisma Cloud API URL".
The solution is to make sure the Prisma Cloud Data Source instance is using "Prisma Cloud API URL"
1. Configure the Prisma Cloud Integration Instance Domain URL to use Prisma Cloud API URL "https://api3.prismacloud.io".
2. This new configuration allows Prisma Cloud integration in Cortex XSIAM to receive alerts and inventory information.
Additional Information
Switched to the correct Prisma Cloud API URL, `https://api3.prismacloud.io`, and the integration worked as expected.