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 Functionality already exists
Categories Usability
Created by Guest
Created on Jan 8, 2018

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