[SERVER-83571] Errors like "No keys found for HMAC that is valid for time" should be included in server logs. Created: 25/Nov/23  Updated: 04/Jan/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Michał Knasiecki Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 1
Labels: car-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to JAVA-5256 Switching replicas IP with a replica ... Closed
Assigned Teams:
Catalog and Routing
Operating System: ALL
Participants:
Story Points: 1

 Description   

Currently, when the client gets "No keys found for HMAC that is valid for time" the only place we can find this in logs is client's logs.

When you have hundreds of clients it can be impossible to track HMAC issues without logs in one, central place. Moreover, since the HMAC error is returned by the server, this information should be contained in the server logs

For this reason, I would like to have a proper log here: https://github.com/mongodb/mongo/blob/db3d58f3eff9f017d329706283f85fdc3ff67f1d/src/mongo/db/keys_collection_manager.cpp#L142


Generated at Thu Feb 08 06:52:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.