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
Categories Security
Created by Guest
Created on Jan 8, 2018

HTTP Proxy Support in SEAS

We are using SEAS to do CRL checking during C:D session setup. We are having difficulties keeping up with some Certificate Authorities. Here is the process as we understand it…
1. The URL for CRL checking is pulled out of the certificate.
2. SEAS attempts to connect to that URL.
3. If the connection fails, CRL checking fails and the session fails.

The problem we are having is that several of the CA's have started using global DNS/IP addresses. When you do several lookups of the DNS name you get a set of IP addresses instead of just one. Also, we can get a different set of addresses when doing the lookups from Kansas City than we get from Parkersburg. This ends up being a large list of IP addresses and they are not always the same static set of addresses. The big issue for us is in the way our network security is structured. We have to open firewall rules for each address. We cannot just open outbound port 80 to the world. We do have port 80 outbound to the world but that is only via http proxy devices. If we could get SEAS to be http proxy aware that would greatly simplify things for us.
DeveloperWorks ID DW_ID110368
Link to original RFE
  • Guest
    Jun 6, 2018

    Delivered in