We are trying to connect to an API to get an authorization token to use in subsequent API calls to get or post data. The url looks like
https://{host}/app/api/JrmQfe/MJZZbq/LoginApi/Login?signature=signature×tamp=1667469087254&nonce=494700 where nonce is a random integer between 100000 and 1000000 and timestamp is the number of milliseconds since Jan 1, 1970. I have
https://{host}/app/api/JrmQfe/MJZZbq/LoginApi/Login?signature=signature in the partner profile along with the required SSL settings and certificates. I generate the timestamp and random integer in the BP and build the complete URL.
The error I get at the HTTP Post is:
HTTP reason phrase [Internal Error: Connection was closed from the perimeter side with error: CloseCode.READ_FAILURE]
I don't see anything in the HTTP Client logs that points to the problem.
Using POSTMAN or Invoke-WebRequest with PowerShell successfully returns a response so the API seems to be working just not with B2B. I have confirmed we can reach the host from our DMZ so that should not be an issue.
I have tried various versions of how much of the URL I put in the partner profile and how much I generate at runtime and they all fail. I have tried not using the partner profile in the HTTP Begin session and using the fully generated URL and it still fails.
We have successfully connected to other APIs with out this problem.
Has anyone see something like this before? Is there some setting the API needs to change to make it work with B2B?
Any advice is appreciated.
------------------------------
John Morrissey
------------------------------
#SupplyChain#B2BIntegration