Skip to content

Conversation

ebozduman
Copy link
Collaborator

Before this fix, what we caught and displayed for an invalid access key value was:

... "Alert":"Object reference not set to an instance of an object.",
"Message":"System.NullReferenceException: Object reference not set to an instance of an object. ...

while the stack trace showed (this is the correct exception message).

Unhandled exception. Minio.Exceptions.AuthorizationException: The Access Key Id you provided does not
exist in our records. ...

For an invalid secret key, what we catch is:

"Alert":"Object reference not set to an instance of an object."

and the stack trace is:

Unhandled exception. Minio.Exceptions.AuthorizationException: The request signature we calculated does
not match the signature you provided. Check your key and signing method.

It looks like the stack trace captures the correct exception message while we miss it.
So, this PR resolves this issue.

@AmBplus
Copy link

AmBplus commented Jul 30, 2025

Check if your locale time is US or not. It seems there is a problem with datetime that may cause an unknown error. I have sent an issue report for this matter. Please verify if the situation is the same or not.
#1323

@ebozduman ebozduman force-pushed the incorrect-credetials-exception-bug branch from 9ccb0a9 to d78d338 Compare October 9, 2025 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants