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.

SEAS Logging Update - User Account/Key Auth

We have SEAS pointing to an LDAP for authentication. When a user account fails to authenticate via SSH public/private key, the logs show
that failure in 'error' mode, but that line does not contain the user
account that failed to log in. We can only see the error when the logging is set to 'debug,' and then the username is approximately 2
lines above the key failure error.

In the attached log sample you can see this - line 2832 is the key failure in ERROR level; line 2830 has the user ID associated with that
authentication failure and that is in the DEBUG level.

To troubleshoot the key failures we see, we have to set the logs in debug mode, and with that level of information the logs roll over every minute or so, giving us limited visibility time-wise. Ideally, the username would be added to the ERROR-level message.
  • Guest
  • Jan 8 2018
  • Future consideration
DeveloperWorks ID DW_ID78894
RTC ID RTC_ID481035
Link to original RFE http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=78894

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.