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.

More detailed ERROR logging for SEAS

SEAS logging at ERROR level does not provide sufficient information regarding authentication failures, forcing us to keep logging level at DEBUG which uses an extremely high amount of disk space in order to have sufficient log retention.

For example, a failure to authenticate via SSH key authentication returns an ERROR message showing that the key assertion failed as well as the key used and the key stored in LDAP, but it does NOT specify which username failed to authenticate with the key. The only way to identify the user seems to be to check the Sterling Secure Proxy logs to correlate what time a user tries to log in with what time the assertion failed. With hundreds of logins happening in a very short time period this becomes difficult if not impossible to do.

At a minimum the ERROR level notification for a failure to authenticate via ssh key should provide the username that was used, the key that was used, and the key that was retrieved from LDAP. Currently it only returns the latter two pieces of information.

I've attached a sample log from a failed login attempt demonstrating that user information is not available as part of the ERROR message.
  • Guest
  • Jan 8 2018
  • Functionality already exists
DeveloperWorks ID DW_ID45583
Link to original RFE

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.