MySQL Forums
Forum List  »  Connector/Node.js

Re: Cannot use caching_sha2_password using XDevAPI, unless using mysqlsh first
Posted by: Geert Vanderkelen
Date: March 16, 2022 04:46AM


Ok, that is important information. Maybe I missed reading that anywhere, and a user must first connect using conventional/classic/0x0a protocol..
Interesting.. But X Plugin uses its own cache. How can that cache then ever be initialised?
And skimming through the X Plugin source, the sha256 is not filled by plain.

With mysqlsh, I am not doing anything special, except connecting to the X Plugin port:

MySQL localhost:18028+ ssl JS > \c msandbox:msandbox@localhost:18028
Creating a session to 'msandbox@localhost:18028'
Fetching schema names for autocompletion... Press ^C to stop.
Closing old connection...
Your MySQL connection id is 81 (X protocol)
Server version: 8.0.28 MySQL Community Server - GPL

(same with --mx)

When I do that, all is good. All tests pass in my code, using TLS or not, using PLAIN (over TLS) or SHA256_MEMORY: I get AuthenticationOK.

I have a feeling I have missed something very obvious :(

Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.