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.