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
Hi Harshit,
We have previously requested more clarifying information. Because the additional information was not provided within 30 days, this request has been closed.
Thank you for your interest in the Cúram SPM product.
Shane McFadden, Cúram SPM Product Management team
Hi Harshit,
In order to evaluate your request we require that you provide more information so that we can fully understand your requirements.
The request states: "Currently the OOTB SYSTEM user's password in database does not match the OOTB supplied password for the same user in generated release by default."
If that were correct this would imply Curam would not work in any OOTB deployments. Would a more accurate representation of the request be the following?:
In a customized environment where the SYSTEM user password has been modified (i.e., from the default syspass) later deployments of rebuilt Curam application EAR files contain the default of syspass, which doesn't match the Curam USERS table in this instance and manual, post-deployment steps are required to achieve a working application. Thus, this request is to make it possible to build Curam application EAR files so they will correspond to the target environment without manual intervention.
Thank you,
Shane McFadden, Cúram SPM Product Management team
Hi Harsh,
Thank you for providing this information.
We will look into this further and get back to you shortly.
Thank you,
Eloise O'Riordan, Cúram SPM Offering Management team
Hi Eloise,
By the OOTB supplied password for the same user - I mean the XOR-ed "password" for "SYSTEM" user in CuramSDEJ\ear\templates\ibm-application-bnd.xml and the password in database in Users table is digest(hash) of "syspass" word.
Thanks,
Harsh
Hi Harshit,
In order to evaluate your request we require that you provide more information so that we can fully understand your requirements.
Can you please clarify what is meant by "the OOTB supplied password for the same user in generated release"?
If we do not receive this information within 30 days, this request will be closed.
Thank you,
Eloise O'Riordan, Cúram SPM Offering Management team
Hi Harshit,
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,
Eloise O'Riordan, Cúram SPM Offering Management team