Shape the future of Curam!
We invite you to shape the future of Curam, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the Curam team to refine your idea
Help Curam prioritize your ideas and requests
The Curam 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 Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at Merative, 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.
Merative External Privacy Statement: https://www.merative.com/privacy
Curam exposes a range of REST APIs for various business modules. They are all exposed by the REST EAR.
It should be possible to disable the subset of REST API end points such that unused REST API end points are not exposed by the REST EAR. This would provide an additional level of security to prevent APIs that are not being used from being invoked unexpectedly.
The only way to do this currently is to edit the range of OOTB Resources XML files in place which is not a compliant mechanism for customization.
SOAP inbound web services can be disabled in the way we are requesting from within a custom component. We request equivalent behavior for REST APIs.
Customer Name | City of New York - Department of Information Technology (DoITT) |
Hi Fintan,
We are happy to inform you that your enhancement request has been delivered in the new release of IBM Cúram Social Program Management, version 7.0.8.0.
IBM Cúram Social Program Management provides a number of REST APIs related to key business functions that are available for use. Currently; however, there is no recommended way to disable these APIs if they are not required. It is now possible to disable any of the REST APIs by adding the APIs to be disabled to a ResourceConfig.xml file so that they will be excluded by the REST Infrastructure when it builds the REST APIs at runtime. REST APIs may be disabled by listing their endpoints individually, by listing a namespace (where all APIs defined with this namespace will be disabled), or by listing a version (where all APIs defined with this version will be disabled).
We hope that this addition to the product will meet your requirements sufficiently.
I will now close this ticket as delivered.
Thank you for your interest in the Cúram product.
Shane McFadden, Cúram SPM Product Management team
Hi Fintan,
We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development however the theme is aligned with our current multi-year strategy and will be considered for a future release.
IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.
IBM will update this request in the future.
Thank you for your interest in the Cúram product.
Shane McFadden, Cúram SPM Product Management team
Hi Fintan,
Thank you for your enhancement request.
We require some further analysis to determine whether or not this enhancement can be considered in a future release.
I will provide another response when our investigation is complete.
Thank you,
Shane McFadden, Cúram SPM Product Management team