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).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
External authentication is already achieved through SEAS, however, if additional authentication logic is required then the only way to achieve this is through a SEAS custom exit. Use of a SEAS custom exit means that we have to re-write the existing authentication logic that ships with SEAS in addition to completing the additional logic.
For instance, if we use a custom exit to authenticate an SSH key and validate that the user is not connecting from a volatile list of IP addresses then we have to write the key authentication logic and IP lookup even though the key authentication logic ships with SEAS.
It would be much better to have either a pre or post authentication exit for a SEAS profile so that additional logic can be executed in addition to that which ships with the product.
For instance, I configure SEAS with the OOTB Key authentication profile. In that profile, I then have the option to set a Java class as a user exit once the OOTB authentication completes. This reduces the complexity of code we need to maintain and ensures that the main authentication logic as designed and tested by IBM is still used.
This would likely benefit all users of product that have need of custom exit, but do not want to re-write and manage the authentication logic that ships with the product in addition to the custom extension.
What is your industry?
How will this idea be used?
The exit will be used to validate connections against a volatile list of undesired sources and record the user information who attempted the connection.
Do not place IBM confidential, company confidential, or personal information into any field.