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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
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.
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. |
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.
SSO token synchronization feature has been implemented in IBM Secure Proxy 6.0 release.