Masking or Reducing the Severity of Login Errors in the CM Log
(Doc ID 2438931.1)
Last updated on MARCH 24, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Billing and Revenue Management (BRM), when a failed login attempt is made, the following errors are logged by Connection Manager (CM) to cm.pinlog:
bad login for "root.0.0.0.1 (/service/admin_client)", failure type 6
E Sun Dec 16 03:46:27 2018 brmhost cm:6168 cm_child.c(133):2696 2:brmhost:cm:5665:-143489328:9:1534455090:1::::
CM bad login attempt from ip_addr=dhcp-1-2-3-4.com:53456, err=56(PIN_ERR_BAD_LOGIN_RESULT), field=0(0)
Is it possible to prevent this alarm from being logged when incorrect credentials are used to log into BRM or at least reduce the severity from an error to something lower?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document