Issue with IFS connect outbound messages with soap actions IFS Cloud 22r2

We have got an issue after and upgrade from 22r1 to 22r2. It seems to be a bug in the framework but as we don’t have access to any bug database I’ll try to raise the question here.

We have an out bound message goin out true ifs connect with http sender and a soap action added wit : (ex urn:test:test2:tes3:v1/test) this was working fine in 22r1.

In 22r2 it has been introduced new way of authenication in the http sender where you can use non,basic….

What we see is inside the table fndcn_address_label_tab and column address_data_2 the data has change inside here:

In 22r1 it contains only the soap action like this

urn:test:test2:tes3:v1/test

in 22r2 it has been added more data into this and now it looks like this

AuthenticationMethod=None:SoapAction=urn:test:test2:tes3:v1/test

In 22r2 when ifs connect process the message we get this exception

ExecutionException from Sender thread

Caused by: ifs.fnd.connect.senders.ConnectSender$TemporaryFailureException: Exception while sending data

Caused by: ifs.fnd.connect.http.InternalServerErrorException: InternalServerErrorException: 500#<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</faultcode><faultstring xml:lang="en-US">The message with Action 'urn' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring></s:Fault></s:Body></s:Envelope>

Have a close look at the Action ‘urn’ in the exception

It looks like : is used to separate the different values in the fndcn_address_label_tab and column address_data_2 causing soap action including : inside will be chunked up and causing the outbound message failing as the soap action will just be urn.