HTTPS Sender adapter in iFlow shows sometimes a 401 error

[RonSterren]

Hi

I have an iFlow with a HTTPS sender adapter. We created a specific role and assigned the role to this iFlow and a clientID (generated in BTP). In general everything is working fine. An external partner is calling the endpoint and sending messages (XML IDOCs).

However we now have a situation that a specific message (relatively large, size 1MB, XML IDOC) is not being processed by the HTTPS sender adapter.

When checking the Integration Suite Logs I see the following that a HTTP 401 is returned.

Also a successfull request is having 401s but will get a 200 in a next request and will continue.

How do I need to interpret this and how can this be solved?

Thanks

Ron

[Andrzej_Filusz]

Hi Ron,

An external partner application sends its first request without any authentication.
That's why you see the 401 error code in your logs. Then the client sends another request, this time
with a proper authentication (and you see HTTP 200).

How to solve that? Your client application should use the preemptive authentication.
In this way the proper authentication credentials will be sent without waiting for the Unauthorized response.

Andrzej

[RonSterren]

Hi Andrzej, Thanks for this explanation. I was not aware of that. But my real issue is that the same interface will get a 401 all the time. Do you have an idea how that can happen?

[Andrzej_Filusz]

Ron, if you get the 401 Unauthorized error all the same then there is something wrong with secret key and/or protocol used by your external partner. Could you please perform a simple test using SoapUI or Postman? If you will be able to send a test message to your interface using the same secret key then it means that guys from your partner made a mistake in their configuration/implementation.