Merative Ideas Portal
Shape the future of Merative!
We invite you to shape the future of Merative, 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 Merative team to refine your idea
Help Merative prioritize your ideas and requests
The Merative 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
Sorry posted the previous comment before completing.
We are having the same issue in SAMS, Ontario project. In addition to the main issue explained in the idea, we want to add below points.
1. For fixing this issue in SAMS, we had to override the CuramAuthenticatorFactory class and also it doesn’t directly picked up by just overriding and we had to replace/patch this class in OOTB jars like CURAMSDEJ\lib\coreinf.jar, CURAMSDEJ\lib\jde-commons.jar, CURAMCDEJ\lib\curam\jar\jde-commons.jar. Unless we did this, at many instances only core version of the file gets picked up. This is not recommended way of fixing the issue, and we need guidance/suggested approach from PD for fixing the issue. i.e overriding the class in custom component with same package doesn’t ensure that custom version gets picked up. Alternatively, we are looking for help from PD to provide a supported way of overriding the behavior.
2. While we were analysing the issue, we see that Curam OOTB SSO code’s logging capabilities should be improved for troubleshooting issues related to SSO.
3. The OOTB code - CuramAuthenticatorFactory that is updated by SAMS is present in multiple libraries. Presence of same Class in multiple libraries is a bad practice and contributes to/results in unpredictable behavior issues as observed during this issue. The code must be improved by product.
We are having the same issue in SAMS , ontario project. In addition to the main issue.
Hi Garry,
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
attached custom code.
in addition as requested:
The SPM system is used by the following users
- Agent users (internal agency users who will access the application over the intranet)
- Support users (SPM live support team/devops etc – may have multiple roles)
- System ‘users' (other systems who will access the application through web service APIs through the intranet)
The SSO integration is only applicable to Agent users.
For SSO users we need to have identity_only set to true.
For non-SSO users we need to have identity_only set to false.
OOTB only allows one option, we require 2.
Attachment (Description)
Attachment (Description)
Hi Garry,
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