Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Aug 28, 2019

Single sign on(SSO) Implementation for External Connection Via SSP for B2Bi Docker

It was noticed that the current steps(mentioned in below link) for SSO implementation is not suitable for External connection Via SSP/SEAS
for docker based B2Bi install.

According to the steps mentioned in above link,

1. files needs to be copied inside the container.
2. /private diretory needs to be created inside container after the container is build.
3. jar files needs to be copied inside container's /private directory.

These steps needs to be repeated every time the container is deleted and a new container is spawned.

In docker based implementation, we should not go inside container and do manual changes.

So a more cleaner approach is required for docker based SSO implementation.

As there are many customers using SSP and SEAS, so this implementation becomes a critical part.

Please provide a cleaner way of doing this implementation.


Attached is the reply from developer and the PMR raised for this is:TS002637002 

What is your industry? Government
How will this idea be used?

we should do a better way of implementation of this piece because this a component which is used by our Major clients who are using SSP/SEAS for external traffic. Because every time the container is dropped, we need to rebuild this components inside container.