Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
6.4.1
-
None
Description
it is impossible to hash the nosqlrotocol.password as a regular maxscale service user.
example :
maxpasswd /var/lib/maxscale aBcd_123
|
gives a hash
when replacing plain text password with said hash in this :
[mcs_mongo]
|
type=listener
|
service=Read-Write-Service
|
protocol=nosqlprotocol
|
nosqlprotocol.user=mongo_test
|
nosqlprotocol.password=HASH
|
port=27017 |
|
after restart all tries to insert a new document end up with this error message :
db.runCommand({insert: "mongo_collection", documents: [{_id: 1, "hello": "world"}]}); |
|
|
uncaught exception: Error: error doing query: failed: network error while attempting to run command 'insert' on host '127.0.0.1:27017' : |
|
|
DB.prototype.runCommand@src/mongo/shell/db.js:177:19 |
with password in clear text, everything works as intended.
Attachments
Activity
you mean that both the service user that connects to mariadb and the listener user that connects to mongo have to be the same and thus we should be using the same hash ?
No, you don't need to use the same hash. However, this worked fine for me, it would be good to verify that the used hash works in some other place. To rule out the possibility that it was created using another key than the one MaxScale uses for decrypting it.
I just tried that and it seems to work. Could you please verify that the user and the encrypted password work when used in the service. To rule out the case that the password was encrypted using another key than the one MaxScale uses for decrypting it.