This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
security.OverrideAsnCompliancePolicy=true needs to be added into the security.properties.in file
per IBM - There is a technote that indicates security.OverrideAsnCompliancePolicy=true be added to the customer_overrides specifically to ignore OID errors caused by certificates with attributes not supported by the Certicom jar files which SI uses for signature verification. This option only enables Sterling Integrator to read additional OID Fields in the certificates which were not supported by the default Certicom libraries.
Additionally – it would have no affect on AS2 communication for those which are currently functioning.
I was seeing this with random AS2 errors on windows, but could show up on any installation.
- with errors such as: Failure unpackaging message Error - class: 5; subclass: 1; code: -1; reporting function: detachedsignatureverifier.transformtext.com.trustpoint.asn.asnexception
The IBM technotes indicate the client add security.OverrideAsnCompliancePolicy=true to customer_overrides.
However, there is no documentation on this. OverrideAsnCompliancePolicy does not exist in the security.properties file. Nor any other property file.
The client therefore gets confused currently, as well as later as to why this is present.
What is your industry?
How will this idea be used?
The simplest thing here is that this property value should be documented and placed into the security.properties and security.properties.in files.
That will ensure the client can find it later when performing updates.
It can also allow additional clients to find it, who may be facing this issue, who don't know there is a possible solution.
Do not place IBM confidential, company confidential, or personal information into any field.