Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 product management 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Workspace OpenPages Ideas
Components Platform Features
Created by Guest
Created on Mar 29, 2019

Support for Encryption of Files / Encrypted File System

Files attached to Objects in OpenPages could contain sensitive information. These files are physically stored on the op-storage mount point on OpenPages Server. The requirement is for OpenPages to support encryption / decryption of these files or provide support for Encrypted File System e.g. RHEL Encrypted File Systems.
  • Guest
    Jun 20, 2019

    Hi John,

    There's a second dimension here, which is encrypting each file within the repository.


    Infrastructure layer encryption is useful, but what it doesn't do is protect the files from users who gain access to the server where the encrypted volume is mounted / NAS back-end, and hence can then read each file.


    The application support team for OpenPages may be (often can be) different to the Red Hat OS support team or the NAS support team. We need a way to protect the files from these threats, and encrypting each file would certain help.


    Yes, this would have an performance overhead, but the customers may choose to accept this. It would also impact things like search re-indexes (you could index before you encrypt), but that's something customers may be willing to accept.

  • Admin
    JOHN Lundgren
    Jun 14, 2019

    [from Nov 15, 2016, 12:20 PM in the previous RFE system]

    Thank you for submitting this RFE!

    OpenPages management of file-attachments stored on the file system is performed at a layer that is transparent to the underlying details of the file storage. The OpenPages application has no awareness of whether the storage is encrypted or not. As long as the file system encryption technology is transparent to our application then it is supported. Clearly, there is some performance overhead at the file access layer when retrieving/storing information via encrypted storage.