Skip to content

Support of authentication using MariaDB Parsec plugin#409

Open
lawrinn wants to merge 3 commits intoblackbeam:masterfrom
lawrinn:master
Open

Support of authentication using MariaDB Parsec plugin#409
lawrinn wants to merge 3 commits intoblackbeam:masterfrom
lawrinn:master

Conversation

@lawrinn
Copy link
Contributor

@lawrinn lawrinn commented Feb 7, 2026

Actual support is enabled by client_parsec feature.

Introduced new test 'parsec_connect' that is also enabled by before-mentioned feature. To the test 'should_change_user' added covering of the case when user authenticated via parsec plugin.

Most of the logic of the work with the plugin is in the method continue_parsec_auth
perform_auth_switch sends additional empty packet to request ext-salt packet. After that continue_parsec_auth calls AuthPlugin methods to read that packet info and to generate response.

Actual support is enbaled by `client_parsec` feature.

Introduced new test 'parsec_connect' that is also enabled by
beforementioned feature. To the test 'should_change_user' added covering
of the user authenticated via parsec plugin.

Most of the logic of the work with the plugin is in the method continue_parsec_auth
perform_auth_switch sends additional empty packet to request ext-salt
packet. After that continue_parsec_auth calls AuthPlugin methods to read
that packet info and to generate response.
and to start server with server plugin loaded
@lawrinn
Copy link
Contributor Author

lawrinn commented Feb 7, 2026

One more thing. Looking at ed25519 I've made it as a feature. It can stay so if you want.
Parsec is designed to be default auth plugin. If it's not default, it doesn't fulfill its main promise - that password is not sent on the wire. It won't happen that soon - for now it's not even possible.

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.

1 participant