The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
internal user credential mismatch observed in aerospike.log
Problem Description
When checking the aerospike.log the following messages are observed.
Nov 26 2019 15:03:03 GMT: WARNING (security): (security.c:2591) login - internal user credential mismatch
Nov 26 2019 15:03:03 GMT: INFO (security): (security.c:5480) authentication failed (credential) | client: 127.0.0.1:49400 | authenticated user: <none> | action: login | detail: user=ValidUsername
Nov 26 2019 15:03:04 GMT: WARNING (security): (security.c:2591) login - internal user credential mismatch
Nov 26 2019 15:03:04 GMT: INFO (security): (security.c:5480) authentication failed (credential) | client: 127.0.0.1:49406 | authenticated user: <none> | action: login | detail: user=ValidUsername
Nov 26 2019 15:03:04 GMT: WARNING (security): (security.c:2591) login - internal user credential mismatch
Nov 26 2019 15:03:04 GMT: INFO (security): (security.c:5480) authentication failed (credential) | client: 127.0.0.1:49408 | authenticated user: <none> | action: login | detail: user=ValidUsername
Explanation
This message indicates that a user is trying to connect to the cluster and that the user is valid but that an incorrect password has been supplied. The user in question here was a monitoring client however this could be any client connecting to a cluster where authentication has been enabled.
Solution
The solution to this error would be to update the password used by the client that is attempting to connect to the cluster.
Keywords
AUTHENTICATION INTERNAL CREDENTIAL MISMATCH
Timestamp
November 2019