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
Post 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 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 notification 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Hardcoded Encryption Key is being used in OpenPages. As checked with IBM support team, here is the information:
"For LDAP authentication, the aurora_auth.config is configured and it stores the LDAP "security.search.user.credentials". The password in aurora_auth.config file will be encrypted via AES 256 algorithm when the OpenPages server starts. We have been using the default key which is packaged with the OpenPages product until OP 72 FP1."
However, according to the latest update from IBM support: "I got confirmation from developers that the custom encrypted keystore did not make the 7.3 release, which is why I couldn't find it mentioned in the documentation."
In this case, would you please enhance the product to include this feature.
Do not place IBM confidential, company confidential, or personal information into any field.