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.

Sterling External Authentication Server High Availability Scenario Failover Mechanism Needs

Hi,

 

We would like to extend the options of failover scenarios in SSP-SEAS integration. In high available configuration, where there are two active SEAS, when one of the servers are down, the other takes over the others responsibilities. However, when the other external authentication server is up again, the SEAS Plugin in SI automatically detects the change and changes back to the original server, but the one in SSP does not understand it and continues to function through the failover SEAS(especially when there is a perimeter server). Since there is no token exchange between external authentication servers, one server switches back, and the other one doesn't, causes a partial service loss in the system. 

 

As a best solution, we would like the SEAS to be able exchange token with other external authentication servers. As a secondary solution, we would like the option to select the autoswitchback mechanism in SSP and SEAS Plugin in SI.

 

Thanks and kind regards,

Tughan.

  • Guest
  • Sep 17 2018
  • Delivered
What is your industry? Banking
How will this idea be used?

Hi,

 

We would like to extend the options of failover scenarios in SSP-SEAS integration. In high available configuration, where there are two active SEAS, when one of the servers are down, the other takes over the others responsibilities. However, when the other external authentication server is up again, the SEAS Plugin in SI automatically detects the change and changes back to the original server, but the one in SSP does not understand it and continues to function through the failover SEAS(especially when there is a perimeter server manages the connection). Since there is no token exchange between external authentication servers, one server switches back, and the other one doesn't, causes a partial service loss in the system. 

 

As a best solution, we would like the SEAS to be able exchange token with other external authentication servers. As a secondary solution, we would like the option to select the autoswitchback mechanism in SSP and SEAS Plugin in SI.

 

Thanks and kind regards,

Tughan.

  • Admin
    VIJAY CHOUGULE commented
    14 Mar, 2019 04:07pm

    SSO token synchronization feature has been implemented in IBM Secure Proxy 6.0 release. 

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.