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 Future consideration
Workspace OpenPages Ideas
Components Other
Created by Guest
Created on Mar 29, 2019

DB Roles Assigned to openpages and opworkflow Violate Hardening Requirements

Per previous communications with IBM the openpages and opworkflow (sevice accounts IDs) require the following roles: PENDING_TRANS$

Issues: all these roles have some privileges that normally against hardening guideline to secure the Oracle DB server.

For example:
The RESOURCE role grants a user the privileges necessary to create procedures, triggers and types within the user's own schema area. The privileges includes- create cluster, create procedure, create sequence, create table, create trigger, type.

SELECT_CATALOG_ROLE role allows user to see the data dictionary view where it contains all schema in the db, space allocation, values for column, privileges and roles of the users. If a malicious user has this role, he or she can collect as much information as he or she needs about the db server through data dictionary.

The risk - Granting privileges to the roles will grant users in the role system privileges or object privileges, it increase the attacking surface, and the risk of getting system compromised. Two IDs are service accounts. They may not be monitored as much as regular users or subject to stricter controls (password expiry for example), if they are compromised, the accounts can gain usual information about the DB and proceed to do further damage.