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 Functionality already exists
Workspace WebSphere Liberty
Created by Guest
Created on Mar 4, 2021

Support SAN on CAC\Smart Card with Liberty server

Add support Subject Alternative Names (SANs) for use with CAC\Smart Cards in Liberty server
Currently using with the ssl-1.0 feature.

Idea priority High
RFE ID 149063
RFE Product WebSphere Application Server
  • Admin
    Gary Picher
    Aug 23, 2021

    Although we do not support directly mapping the SAN, we added support for plugging in custom X509CertificateMapper implementations for exactly this type of case where someone needs to map something that we don't explicitly provide first-class support for.

    That support is described on this page: the section entitled "Example of a custom X509CertificateMapper implementation".

    Using a custom X509CertificateMapper is the preferred way to map attributes that are not directly supported by us in the config.