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
Block users from attempting authentication at the Secure Proxy level
We have a Secure Proxy engine that is exposed to the internet. As such we are subjected to a large number of "probing" login attempts from usernames such as "root", "admin", etc.
All of our login attempts are passed to a Sterling External Authentication server for authentication through LDAP. With the current setup we wind up with tens of thousands of failed login attempts daily, causing load on our SEAS engine and LDAP servers, and also filling the SEAS logs with thousands of lines of garbage errors from these failed login attempts.
It would be useful to be able to restrict login attempts at the Secure Proxy level so that known invalid-ids are not even allowed to attempt authentication. This would reduce load on the authentication / LDAP servers, and also make the product more secure as there would be no chance of a user being able to break into a privileged ID if one happens to exist in LDAP.
Ideally it would be preferable if we could configure a pattern / patterns (perhaps using regex) that an allowed username must match in order to be allowed to attempt authentication. If not, it would at least be helpful to be able to blacklist specific usernames so they would not be allowed past the proxy.
Do not place IBM confidential, company confidential, or personal information into any field.