Skip to Main Content
IBM Sterling

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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories Usability
Created by Guest
Created on Jan 8, 2018

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.
DeveloperWorks ID DW_ID78894
Link to original RFE