IBM Sterling Ideas

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

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.

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

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.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 8 2018
  • Already exists
What is the idea priority? High
DeveloperWorks ID DW_ID45583
Link to original RFE
  • Attach files