Replies: 7 comments 11 replies
-
|
MDN handling has not been changed in a very long time. My guess is that it has nothing to do with the MIC and MDN at all. Most likely it is because the IBM system does not support chunking. See #341 or search for "chunking" in the lartest OpenAS2HowTo.pdf for a possible solution. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Below is my partner configuration.
I don’t believe this is a chunking issue since I already have “no_chunked_max_size” set to 104857600. When I switch back to version 2.9, everything works fine, but upgrading to any newer version causes the errors to appear. |
Beta Was this translation helpful? Give feedback.
-
|
The original implementation only required setting “no_chunked_max_size” attriribute but in 3.1.0 the "prevent_chinking" attribute was added for performance and confusion in implementation reasons. Read section 17.5 "Content Length Versus Chunked" in the guide for details.
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
still getting the same error with "prevent_chunking" logs |
Beta Was this translation helpful? Give feedback.
-
|
partnership |
Beta Was this translation helpful? Give feedback.
-
|
I have seen these reports quite often where there is a response from the partner but no MDN report and associated MIC. I have added additional logging in this jar (which you will have to remove the .txt extension from to use) that may provide insight to the problem: Since it works for a 2.x version but not for 3.x or 4.x, if you are using exactly the same AS2 certificate key store (as2_certs.p12 by default) and the same partnership.xml (except for adding the If you are NOT using exactly the same certiifcates keystore and partnerships.xml files then you should make sure that the correct certificates are installed and the AS2 ID's match exactly. There may be details in the returned HTTP response that provide some clue as to what is going on. Try enabling TRACE level logging and see if that provides more insight. (see "Log Level Configuration" section in the OpenAS2HowTo). Failing that try enabling Mime Body Part logging to see if your partner is returning any information about the failure on their side (see "Mime Body Part Logging" in the OpenAS2HowTo). If neither of those work then you will need to ask your partner if they can p[rovide more details on what exactly the error is that is being thrown on their side. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Please find the trace-level logs below with 4.6.4 JAR |
Beta Was this translation helpful? Give feedback.
-
|
Logs with MIME body parts enabled show an error at the end of the received MIMEBODYPART. I’m not sure about the root cause yet — do you suggest I contact the partner regarding this, or do you already have some information on it? |
Beta Was this translation helpful? Give feedback.
-
|
The reported error states in the HTML "The requested URL was rejected. Please consult with your administrator." This seems to point to the fact that you are possibly using an incorrect URL in the partnership attribute: If this is the identical URL that you are using when running using the 2.X version of OpenAS2 then you will need to contact them to get more details on what their system is reporting in terms of the URL it is receiving because that message is probably misleading and it may mean they cannot identiofy your AS2 ID or some other issue that I could only guess at. Can you confirm that you are using exactly the same as2_certs.p12 and partnerships.xml files (apart from the specific differences I mentioned in a prior response to this issie) for testing the working 2.x version against the 3.X or 4.X versions? |
Beta Was this translation helpful? Give feedback.
-
|
The only difference is in config.xml to accommodate the 4.X versions. as2_certs.p12 and partnerships.xml are the same. |
Beta Was this translation helpful? Give feedback.
-
|
NOTE: Off the back of the issue you are facing I have just released 4.7.0 which enhances logging to provide more details at the standard log levels when the MDN response is not what is expected (avoids having to increase logging levels to TRACE level). |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
I see below line in logs in case of successfull file transfer with positive MDN
mean while let me test that problematic partner. |
Beta Was this translation helpful? Give feedback.
-
|
4.7.1 fixes the logic that incorrectly produces that log message when the AS2 transaction is successful and fixes the 3 spelling werrors in the message. |
Beta Was this translation helpful? Give feedback.
-
|
still geting same error that was in 4.6.4 |
Beta Was this translation helpful? Give feedback.
-
|
config.xml for 4.X config.xml 2.9 |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if there has been a misunderstanding here but the code changes I made were NOT intended to fix your underlying issue - they were simply to provide better logging so that the underlying problem can be more easily debugged. Your partner is reporting that the URL you are using to connect to it is somehow incorrect: At face value the error message returned from the partner points to the "as2_url" attribute being wrong BUT ... this may not be the real reason it is failing - the partner software might be erroring out because of some other underlying reason that it has summarised as a URL error. The first step is to be absolutely certain that your 2.X and4.X configurations are essentially identical to rule out the possiblity that you have made some error across the two configurations that are causing the issue. If the "as2_url" attribute is identical for the 2.X test and the 4.X test (apart from the added "prevent_chunking" attribute for 4.X) then you will need to ask your partner if they can provided an extended log around the error they are getting on their end to figure out what is wrong. NOTE: The config.xml settings are most likely irrelevant in identifying this issue because you are successful in connecting to other partners so it is configuration specific to this partner you are trying to debug and that is going to be in the partnerships.xml file. The only possible reason there may be a config.xml file change is if you are referencing "properties" attributes in your partnership file such as the |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
NOTE: You should no longer need to modify the config.xml file in 4.X. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Is this still an issue? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Issue: MDN parsing issue after upgrade from 2.9 to 4.6.3
Hello team,
After upgrading OpenAS2 from v2.9 to v4.6.3, I’m experiencing an issue when exchanging AS2 messages with IBM Sterling B2B.
The same configuration works fine on v2.9, but fails on all later versions (3.x.x–4.6.3).
Error log:
An MDN is received from Sterling, but OpenAS2 fails to recognize it as a valid
multipart/report, and the MIC validation does not occur.Relevant configuration:
In v4.6.3, OpenAS2 appears to expect a
multipart/reporteven when the MDN option is set to optional, while in v2.9 it handled this correctly without error.Working version: 2.9
Failing versions: 3.x.x – 4.6.3
Request:
Could you please confirm if there were changes in MDN handling or validation logic after v2.9 that now require a multipart MDN even when
signed-receipt-protocol=optionalis used?Thank you.
Beta Was this translation helpful? Give feedback.
All reactions