IBM Sterling Ideas

formerly Watson Supply Chain

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. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

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

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.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 8 2018
  • Uncommitted Candidate
What is the idea priority? Medium
DeveloperWorks ID DW_ID78894
Link to original RFE
  • Attach files