Limitations of Basic Authentication Parameters in PI 7.31 SOAP Adapter

[weberpat]

Broadening the original question as I found that I'm getting the same 401 when calling the receiver service through a "static" comm channel with the long username and password configured. Are there any known restrictions for HTTP Basic Authentication parameters in the PI 7.31 SOAP Adapter? Can they be influenced through configuration in the admin tools?

--

We are extensively using dynamic endpoints in our SAP PI 7.31 SOAP Adapters that we are allocation through dynamic configuration headers. The usernames for these endpoints are passed via the TAuthKey header and the corresponding passwords are stored securely in the credential store of the SOAP adapter. This has worked very well for us for many years until recently we have started integrating with Dell Boomi processes for which the Basic Authentication credentials are auto-generated and significantly longer than what we use for other systems today.

Usernames are 41 characters long and contain an "@"
Passwords are 32 Byte GUIDs in lowercase, dashed notation

We are getting HTTP 401s from the receiver in Boomi. This error does not occur when the same credentials are tested in Postman or when we build the HTTP Authorization header ourselves and send it along with the message (which we don't want to do for obvious reasons).

Is anybody aware of limitations to the dynamic authorization key concept that could apply here?

[weberpat · Accepted solution]

Apparently the combination of username and password cannot be longer than 53 characters. This is fixed in a later PI 7.31 Service Pack that we won't install anymore. Reference:SAP Note 2294216