Details
-
Bug
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Catalog and Routing
-
ALL
-
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
Attachments
Issue Links
- is related to
-
JAVA-5256 Switching replicas IP with a replica from a different replicaset can result in java driver obtaining HMAC keyId from the different replicaset
-
- Closed
-