on 12-13-2008 3:21 PM
Hi,
I would like to know the cause of the following error which I frequently encounter in my Seeburger AS2 adapter engine for outgoing messages
MIC not verified # MIC values not verified: QRP65LlObLvoGwZmMdIFpuXsvzA=-yqCovOQUkVWawfNVfSrXXaRRt8c=
It appears only in the adapter engine and doesnt reflect as an error in RWB.
We have already checked the certificate being used and found it to be valid.
Would like to know the root cause of this.
Thanks in advance
Hi Minisha
This can be error due to adapter locking check with Visual admin.
I have not faced this error but i suggest contact basis for this. it can be issue occurred while installation with AS2.
Thanks
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
MIC is the message digest sent by the receiver AS2 system as a part of MDN to acknowledge the status of sent message. This is used by sender for non-repudiation of sent message. This message indicates some problem in the message sent. The point of this verification is the at sender system. This is not exactly XI related problem.
Found a similar problem in Seeburger guides but this is related to authentication failure
Outbound: MIC not verified # authentication-failed, processing continued
Cause:
An incorrect signing certificate is being was used, but the trading partner continued with the
processing, because it doesnu2019t matter, if the message is authenticated, or not.
Solution:
Check the signing certificate configuration.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.