tracker issue : CF-4205102

select a category, or use search below
(searches all categories and all time range)

ColdFusion erroneously writes LDAP error messages to server.log and exception.log

| View in Tracker

Status/Resolution/Reason: To Fix//BugVerified

Reporter/Name(from Bugbase): A. B. / ()

Created: 09/04/2019

Components: Logging

Versions: 2018

Failure Type:

Found In Build/Fixed In Build: 2018,0,04,314546 /

Priority/Frequency: Normal /

Locale/System: / Win 2016

Vote Count: 0

Problem Description:
Each time an LDAP login attempt fails, ColdFusion writes the corresponding error message to server.log and to exception.log. This is erroneous. 
There is, especially, no justification for logging LDAP errors in server.log! 

Steps to Reproduce:
Set up your ColdFusion instance in the usual way to use LDAP authentication. Then deliberately attempt to log in with, say, 10 invalid login credentials. 
Then examine your exception.log and server.log. See attached examples.

Actual Result:
The LDAP errors are logged to exception.log and server.log.

Expected Result:
 LDAP errors SHOULD NOT be logged to exception.log or to server.log. Especially not to server.log, where they stick out like a sore thumb.
The ColdFusion Team might want to create a separate log file for such Java errors.

Any Workarounds:
Not relevant.



Please refer to:
Comment by A. B.
31272 | September 04, 2019 08:32:40 AM GMT