Curam by Merative Ideas Portal
Hide about this portal
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
On the TLS version checking, 1.2 is the one we see mostly these days but 1.3 is also being used more.
This was created back in the day when browsers had not yet caught up with the 1.0, 1.1, 1.2 changes. And under Windows, under the Internet Options, is where TLS version settings are now stored. So will browsers automatically warn clients now in their browsers on their behalf without the UA or SPM product having to issue the warning, when it detects an issue with server TLS version vs browser capabilities? Just like when a site issues a self-signed cert, the browser warns the user, the application does not need to handle this.
Thx,
Andrew
Hi, was any modification made to the DbDiff component of the upgrade helper to resolve this since 2023? I can always download and check it but thought I'd ask first.
Thx,
Andrew
CoE is waiting for more comments but as we understand it this is still needed, medium priority
Hi Ravi,
We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
SPM should explicitly check if a TLS 1.2 connection is made, and if not, display an error message to the user instead of relying on the browser brand & version's behaviour.
The theme is aligned with our current multi-year strategy for our product and we have accepted your suggestion as a consideration for a future release. Not all items under consideration will make it into a release. As plans are confirmed, you will be notified when a specific release includes this enhancement.
Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.
Regards,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Hi Ravi,
Apologies for the delay. We are still reviewing this enhancement request and will revert back shortly.
Thank you,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Hi Shane
As it is over 30 days now, wanted to know if there is any update on this RFE?
Regards
Ravi.
Hi Ravi,
Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.
We will review the information you have provided and get back to you within 30 days. If additional details are required in order to complete our evaluation, we will send you a request for more information.
Thank you,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Attachment (Use case)