Watson Supply Chain Ideas

Use this form to submit an idea for a new product feature. The product team will review your input and provide status updates as decisions are made regarding the request.

Before you submit a new idea, please view requests that have already been submitted. If your idea has already been submitted, you can add comments or vote on the existing idea, thereby indicating your agreement with the idea. We may use this information to help prioritize development of new features.

 

Submit ideas for Watson Marketing and Watson Commerce products

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 17 2018
  • Under Consideration
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.

What is your industry? Banking
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files