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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Include special characters (e.g. @) in Parameter Name of Obscure Data - Process Data Values service
We are using SI 126.96.36.199 and the Parameter Name does not allow special characters such as "@" being used in the Obscure Data - Process Data Values service. This prevents email addresses being used as Names.
Remove the validation of the X520SerialNumber in the PKI-J toolkit
An error occurred when updating a certificate for a client with a Serial number too long issue. Certicom found that certificate is not valid and cannot be used since the X520SerialNumber contains more than 64 characters which violates the RFC.
Fine grained authorisation for REST services
It seems any user in APIUser can execute any Product service. In our solution we might want to permission different users (identified by an access token , I've raised other Ideas for that) to have different access to services (proxied through the ...
Support token based authentication for HTTP adapters and Product REST communications
We are using the 6.1 product REST, the REST Auth.war and a set of custom REST services (the latter two in HTTP Adapters). We have a security challenge on the use of Basic Auth for securing these services which we access via a gateway (Tyk) from a ...
Limit the version number for resources
There should be a way/property to limit the number of versions for B2B Integrator artifacts like Business Process, XSLT, Maps, Code Lists. Currently we can have as many versions as created for each of these artifacts and need to manually clean up ...
MDC (Modification Detection Code) support for native PGP service with in the Sterling Integrator.
Other PGP software's like 'McAFee' supports MDC (Modification Detection Code).
Support for MQ version 9.2, currently supports upto v188.8.131.52
Our Implementation uses Global Mailbox and the current version of B2Bi (184.108.40.206, 6.1.1) supports maximum MQ version 220.127.116.11. Our Security and MQ team have identified a security vulnerability with version 9.1.x.x which is remediated with version 9....
Enable FIPS support for HSMs in Sterling B2B Integrator
Sterling B2B Integrator does not support FIPS enabled HSMs. As it is a security requirement that FIPS mode is enabled in HSMs, Sterling B2BI should provide this support so that certificates can be protected by HSMs
Additional REST services
In our project, we have augmented the Sterling REST services with some other capabilities which we wrote as JAX-RS/Jersey REST services, hosted in a WAR in an HTTP Adapter. It would be good if you would consider in the roadmap providing the functi...
Enable authentication by token on the Sterling B2B REST API
Seems like currently the B2B REST API only supports authentication of basic type, where username/password is sent in header of get/post/put HTTP call. Can there be a mechanism to authenticate via bearer token? Thanks very much!
Do not place IBM confidential, company confidential, or personal information into any field.