Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9091

Re: Conten type in Seeburger

$
0
0

Hi All,

Sorry for late reply..I was testing in different ways

 

The first thing is our customer is using TIBCO system and we Seeburger whenever we receive order (ENCOM2002) we send back functional ack.

So the configuration part in PI system as below

1.       payload signed  SHA-1

2.       payload encrypted 3DES

3.       MDN Synchronous

4.       MDN is signed SHA-1

 

from both the ends.

 

Issues

 

1) If our customer uncheck the encryption and send messages then he can see the control message with content as application/edifact and its working fine 

 

2) But when he send with encryption the control message contains content type as application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m

 

The log from customer end is like below

Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m

Content-Disposition: attachment; filename=smime.p7m

Disposition-Notification-Options: signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1

 

Since content type is appearing as pkc7 he was not able to decrypt the data

 

 

3) But when I send through RWB by its own I can see the content type as what I mentioned in comm channel which is application/edifact and I can see in SEEBURGER MONI and our customer can decrypt the data

 

I tried with different content type as well like

1) application/edifact 

2) application/edi

3) application/PKCS7-mime

 

 

Can you please let me know what I am missing in our config.


Viewing all articles
Browse latest Browse all 9091

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>