Hello everyone,
We’re facing an issue during the PCSID renewal process in the simulation environment.
All renewal steps complete successfully until the final POST request to production/csids, where we receive an authorization error.
Below are the detailed steps followed and the issue encountered.
Steps Executed
-
PATCH request to
/production/csids-
Sent the CSR in the request body.
-
Used Authorization header as the combination of the existing PCSID and PSECRET (from the previous onboarding).
-
The request returned:
-
a BinarySecurityToken (used as the new CSID for compliance checks), and
-
a new secret, which was then used to generate new authorization for further API calls.
-
-
-
Used CSID and Private Key from the first onboarding
- Using the CSID from step 1 and the original private key (generated during the first onboarding),
we signed XMLs and generated hash values as part of the standard signing process.
- Using the CSID from step 1 and the original private key (generated during the first onboarding),
-
Submitted signed XMLs for Compliance Check
- All compliance checks were successful using the new authorization obtained from the renewal response.
-
Attempted POST request to
/production/csids-
Used the new authorization and the request ID returned from step 1.
-
At this stage, we receive the following error response:
Error: “You are not authorized to use this API endpoint”
-
Summary of the Issue
-
Renewal via PATCH works fine and returns valid CSID + secret.
-
Compliance checks succeed with the new authorization.
-
But while performing the final POST to
/production/csids(with the new authorization and request ID),
the API responds with “You are not authorized to use this API endpoint.”
Request for Guidance
Could anyone please confirm:
-
If there are any recent changes in authorization scope for the
production/csidsendpoint in simulation? -
Whether the POST call after renewal should still use the old PCSID authorization, instead of the new one?
-
Or if the simulation environment now restricts renewal-related POST requests after successful compliance checks?
Any clarification or guidance from others who faced similar behavior would be appreciated.
“compliance_request_id”: “1762171454537”
Thanks in advance