Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2209047

Summary:	Inconsistencies in the log messages
Product:	Red Hat Directory Server	Reporter:	Viktor Ashirov <vashirov>
Component:	389-ds-base	Assignee:	LDAP Maintainers <idm-ds-dev-bugs>
Status:	CLOSED MIGRATED	QA Contact:	LDAP QA Team <idm-ds-qe-bugs>
Severity:	low	Docs Contact:	Evgenia Martynyuk <emartyny>
Priority:	low
Version:	12.2	CC:	idm-ds-dev-bugs, musoni, pasik, tbordaz
Target Milestone:	DS12.5	Keywords:	Triaged
Target Release:	dirsrv-12.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-26 13:49:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Viktor Ashirov 2023-05-22 12:27:24 UTC

Description of problem:
From https://bugzilla.redhat.com/show_bug.cgi?id=2057070 

There are some inconsistencies in the log messages, that might affect log parsing (i.e. for monitoring systems):
1. Mixed first letter case, see attached file

2. Double space before "Entry:"
Account is locked and requires administrator reset.  Entry (uid=dbyers,ou=people,dc=example,dc=com) Policy (Global)
(also this message is a bit confusing, in the source right above it says: "Exceed password retry limit. Contact system administrator to reset.")
password retry limit exceeded.  Entry (uid=tuser,ou=people,dc=example,dc=com) Policy (Global)
user is not allowed to change password.  Entry (uid=dbyers,ou=People,dc=example,dc=com) Policy (Global)

3. Dot at the end of the message
update pwdTPRUseCount=1 on entry (uid=jdoe1,ou=people,dc=example,dc=com) policy (Global).

4. Mixed separators before "Entry" (dot instead of colon)
Account is locked and requires administrator reset.  Entry (uid=dbyers,ou=people,dc=example,dc=com) Policy (Global)

5. Entry/Policy small case
Unsuccessful bind, increase pwdTPRUseCount = 1 (max 3) - entry (uid=jdoe1,ou=People,dc=example,dc=com) policy (Global)

6. Function name in the message (not sure, maybe it should be there, but it's the only one I encountered)
slapi_check_tpr_limits - attempt to bind with TPR password not yet valid (current=20230210133504Z, validity=20230210133514Z): Entry (uid=jdoe2,ou=people,dc=example,dc=com) Policy (Global)

Version-Release number of selected component (if applicable):
389-ds-base-2.2.6-1.module+el9dsrv+17949+63c5b04e

Comment 2 Viktor Ashirov 2024-06-26 13:49:05 UTC

This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-39. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.