Skip to Main Content
Cloud Platform

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

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,

  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 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 a 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.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on May 11, 2016

Liberty Collective security must support SAF keyrings and certificates that SSA will furnish, with no requirements for Subje

DESCRIPTION: Collective security requires certificates and keystores outside the scope of the configuration specified by the server.xml. The certificates require specific Subject Distinguished Name (DN) values as a way to communicate authentication and authorization information between the Collective Controller and members. Multiple signing authorities are used to enable trust between the controller and members while disabling trust between members and other members. SSA policy is that SAF (Computer Associates Top Secret) certificates and keyrings must be used for servers on z/OS. SSA certificates are issued by the Federal PKI, a third-party certificate authority (CA). When certificates are issued by a third-party CA, the Subject DN values are ultimately not under the control of the certificate requester. The Subject DN in the certificate request might be used, or it might be replaced by the CA with a Subject DN format chosen by the CA. So even if Liberty Collective security supports SAF keyrings, SSA can't guarantee that the certificates produced by its mandated PKI will contain the information required for Collective security to function. SSA also can't guarantee that multiple Federal PKI CA certs are available to implement the trust model.
Liberty Collective security must support whatever SAF keyrings and certificates SSA furnishes, with no requirements for Subject Distinguished Name formats .

Idea priority Urgent
RFE ID 88200
RFE Product WebSphere Application Server