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