EDIINT outbound messages- authorization

Tim_sah · April 22, 2014, 6:02pm

Hi everybody,

When i send an outbound message to a partner through wm.EDIINT:send i get the following error message in the activity log of the EDIINT transaction

the remote partner server is reachable, because the execution of a telnet command on the IPAdress/Port of the partner connects successfully

furthermore, both sides are using the same AS-version 1.1, and very probably there is no filter above the partner server.

any possible explanation to this issue?

regards

rmg · April 22, 2014, 6:10pm

Most likely it is due to ACL issue or auth issue with the certs…so on EDIINT:receive (what Execute ACL you are on Anonymous or TNPartners or Internal)

HTH,
RMG

Tim_sah · April 22, 2014, 6:18pm

actually, i’m the sender of the message and the partner has a different product (not WM).
the error message is seen on the log activity of my EDIINT send transaction.

moreover the message is neither signed (no certificate) nor encrypted. (plain)

regards

rmg · April 22, 2014, 6:59pm

Sorry I read wrong…

Any user credentials supplied to you for connecting to their AS2 site?

Is the partner seeing your request attempt in their firewall and their product tool logs?

Also please make sure the AS2 identifiers are correct on both sides.

Either way the TP side need to check more on the Auth side of aspects.

HTH,
RMG

sivakumar_guntha · April 22, 2014, 7:31pm

According to exception, i can say ACL relates this exception.

can you check do you have the required privileges to execute that service.

or your name get added to the Admin ACL then this issue probably solves

rmg · April 22, 2014, 8:06pm

ACL applies only for receive side but the exception is sending to TP from wM/EDIINT outbound.

HTH,
RMG

Tong_Wang · April 22, 2014, 9:01pm

I guess the error is returned from your partner’s system.
Make sure the username/password or authentication cert is configured on their system and has the privilege to execute the AS2 receiving service.

rmg · April 22, 2014, 9:48pm

Should be it

Any user credentials supplied to you for connecting to their AS2 site and TP is expecting same no typos or user not enabled?

HTH,
RMG

Tim_sah · April 23, 2014, 11:39am

thank you for your usual assistance,

i’m suspecting the user/pasword provided to us by the partner, i’m asking him right now to check them for us again.

regards

Tim_sah · April 25, 2014, 4:43pm

Hi everybody and thanks for your assistance,

as you said, it was an authentication issue. the partner was wrong to consider the login/password unnecessary.
in addition to this, he set the parameter “deferred response” to off on his product, then the MDN for EDI messages is received on his system successfully.

the only problem left is that the partner did not receive the MDN for text messages. In stead of the MDN he received a strange file with an html content (the pipeline values for the interface wm.tn.route:routeBizdoc !!!)

did anyone see something like this before?

regards

Tong_Wang · April 25, 2014, 5:30pm

I’m little confused.
Your system is sending via AS2, MDN should be generated by your client’s system, and received by your system.
If you are receiving html response, that means your client system is not generating MDN. Check with your client.

Tim_sah · April 25, 2014, 5:51pm

actually, my system is receiving both EDI and flat file messages, and sending EDI messages. with the same partner.

this is the status:
sending EDI , OK - receiving its MDN, OK
receiving EDI , OK - sending its MDN, OK
receiving flat files, OK - sending its MDN NOK

for this last one, the transaction “EDIINT MDN” is well generated with no error on the activity log and with status “SendMDNMsg:DONE” . my partner receives an html file instead of the MDN

regards

Tong_Wang · April 25, 2014, 6:43pm

What’s the content-type they used for the flat file?
EDI INT only support specific content types, that maybe the reason of no MDN generated. check the Guide for detail on content types.

rmg · April 25, 2014, 8:47pm

OK html file that sounds weird:

Tim_sah · April 25, 2014, 8:54pm

hi,

the message WM received if of content type = application/txt , and according to “8-0-SP1_EDIINT_Module_Install_and_Users_Guide.pdf” :

but i’m doing the processing very well through a custom service of the service “ProcessMsg” that is called in the EDIINT processing rule.

the problem is that an MDN is truly generated and mentions that it’s successfully sent but the partner does not receive it ! (he receives the html file)

i’m always confused because there is certainly something missing but i don’t know what it is.

regards

Tong_Wang · April 25, 2014, 9:17pm

in the incoming AS2 envelope header, is this field: Disposition-notification-to populated with a value?
If not, ask the sender to populate it (this field means a MDN is expected).

Tim_sah · April 26, 2014, 12:06am

Hi Tong wang,

yes, the Disposition-notification-to comes to WM populated for both EDI and TXT as well. then a an MDN is sent to the partner for both message types. however the partner doesn’t receive the MDN for TXT.

i traced the pipeline in th gateway service for the http request for the both cases:

Trace of the HTTP request for an EDIFACT message on our gateway service*****

2014-04-24 10:12:58 WET [ISP.0090.0001C] --- START tracePipeline [24/04/14 10:12] ---
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 requestHdrs {com.wm.util.Values} => 
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 MIME-Version {java.lang.String} = '1.0'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 AS2-From {java.lang.String} = 'xxx@xxxxxx.xxx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 AS2-To {java.lang.String} = 'xxxxx@xxxxxxxxxx.xx.xx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 AS2-Version {java.lang.String} = '1.1'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Accept {java.lang.String} = '*/*'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Authorization {java.lang.String} = 'Basic YW5wdXNlcjphbnB1c2Vy'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Connection {java.lang.String} = 'close'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Content-Disposition {java.lang.String} = 'attachment; filename="Message_IFTMBP.txt"'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Content-Length {java.lang.String} = '1011'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Content-Transfer-Encoding {java.lang.String} = 'binary'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Content-Type {java.lang.String} = 'application/edifact'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Date {java.lang.String} = 'Thu, 24 Apr 2014 09:17:06 GMT'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Disposition-Notification-To {java.lang.String} = 'xxx@xxxxxx.xx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 From {java.lang.String} = 'xxx@xxxxxx.xxx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Host {java.lang.String} = '194.204.247.50:5557'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Message-Id {java.lang.String} = '<1398331026.93.xxx@xxxxxxxxxxxxxX>'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 Subject {java.lang.String} = 'TEST'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 To {java.lang.String} = 'xxxxx@xxxxxxxxx.xx.xx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 User-Agent {java.lang.String} = 'XXXXXXXX/3.2'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 MIME-Version {java.lang.String} = '1.0'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 AS2-From {java.lang.String} = 'xxx@xxxxx.xxx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 AS2-To {java.lang.String} = 'xxxxx@xxxxxxxxxx.xx.xx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 AS2-Version {java.lang.String} = '1.1'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 Content-Disposition {java.lang.String} = 'attachment; filename="Message_IFTMBP.txt"'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 contentLength {java.lang.String} = '1011'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 Content-Transfer-Encoding {java.lang.String} = 'binary'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 contentType {java.lang.String} = 'application/edifact'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 Date {java.lang.String} = 'Thu, 24 Apr 2014 09:17:06 GMT'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 DispositionNotificationTo {java.lang.String} = 'xxx@xxxxx.xxx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 From {java.lang.String} = 'xxx@xxxxxx.xxx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 message-ID {java.lang.String} = '<1398331026.93.xxx@xxxxxxxxxxxxxX>'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 Subject {java.lang.String} = 'TEST'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 To {java.lang.String} = 'xxxxxx@xxxxxxxxxx.xx.xx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 stream {java.io.SequenceInputStream} = 'java.io.SequenceInputStream@3dc37641'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 protocol {java.lang.String} = 'http'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 0 ipInfo {com.wm.util.Values} => 
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 localIp {java.lang.String} = 'xxx.xx.xx.xxx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 localPort {java.lang.String} = 'xxxxx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 remoteIp {java.lang.String} = 'xxx.xxx.xxx.xx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 remotePort {java.lang.String} = 'xxxx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 clientIp {java.lang.String} = 'xx.xxx.xxx.xx'
2014-04-24 10:12:58 WET [ISP.0090.0008C] 1 clientPort {java.lang.String} = 'xxxxx'
2014-04-24 10:12:58 WET [ISP.0090.0002C] --- END tracePipeline ---

Trace of the HTTP request for a application/txt message on our gateway service******

2014-04-24 14:38:34 WET [ISP.0090.0001C] --- START tracePipeline [24/04/14 14:38] ---
2014-04-24 14:38:34 WET [ISP.0090.0008C] 0 requestHdrs {com.wm.util.Values} => 
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 MIME-Version {java.lang.String} = '1.0'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 AS2-From {java.lang.String} = 'xxx@xxxxxx.xxx'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 AS2-To {java.lang.String} = 'xxxxx@xxxxxxxxxx.xx.xx'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 AS2-Version {java.lang.String} = '1.1'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Accept {java.lang.String} = '*/*'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Authorization {java.lang.String} = 'Basic YW5wdXNlcjphbnB1c2Vy'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Connection {java.lang.String} = 'close'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Content-Disposition {java.lang.String} = 'attachment; filename="Message_2.txt"'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Content-Length {java.lang.String} = '426'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Content-Transfer-Encoding {java.lang.String} = 'binary'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Content-Type {java.lang.String} = 'application/txt'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Date {java.lang.String} = 'Thu, 24 Apr 2014 13:42:56 GMT'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Disposition-Notification-To {java.lang.String} = 'xxx@xxxxxx.xxx'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 From {java.lang.String} = 'xxx@xxxxxx.xxx'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Host {java.lang.String} = 'xxx.xxx.xxx.xx:xxxx'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Message-Id {java.lang.String} = '<1398346976.562.xxx@xxxxxxxxxxxxxX>'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 Subject {java.lang.String} = 'TEST'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 To {java.lang.String} = 'xxxxx@xxxxxxxxxx.xx.xx'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 1 User-Agent {java.lang.String} = 'XXXXXXXX/3.2'
2014-04-24 14:38:34 WET [ISP.0090.0008C] 0 contentStream {com.wm.net.HttpInputStream} = 'com.wm.net.HttpInputStream@5f7ff231'
2014-04-24 14:38:34 WET [ISP.0090.0002C] --- END tracePipeline ---

is there anything wrong with the http request for application/txt message

regards

rmg · April 28, 2014, 4:46pm

Did they set Type as Plain or some thing else?..In the plain case it should send MDN as expected.

HTH,
RMG

Tong_Wang · April 28, 2014, 8:30pm

the MDN should be sent back as the HTTP response (sync MDN).
You have MDN generated, but not put as the response.
try to trace: wm.EDIINT.rules:processMsg
you may get some idea.
HTH,

rmg · April 28, 2014, 9:41pm

What type of MDN requested async or sync mode from your TP?

I believe you were saying they received in html format and it shouldn’t the format.

HTH,
RMG