IBM Sterling Ideas

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

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

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

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.

https://www.ibm.com/support/knowledgecenter/en/SS6PNW_6.0.0/com.ibm.help.ssp.scenarios.doc/reverse_proxy/ssp_hsso_prepsfgunx.html

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 

  • Guest
  • Aug 28 2019
  • Delivered
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.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.