Release Notes of 3.5.0 say it's including PARSEC auth support.

However the commit diff is not showing any additions for PARSEC and trying out 2.5.0 aborts with parsec beeing unsupported (tested against 11.6.1).

swiffer ouch. Like you indicate, the parsec implementation never went to jdbc connector 3.5.0, it has stayed on a specific branch, and never been merged for 3.5.0 release. This will be corrected in 3.5.1 release

👍 i've tried out 3.5.1-SNAPSHOT, indeed this has support enabled. however isMitMProof() is not set in the new auth plugin making Zero-Config SSL so that does not work anymore.

Is PARSEC indeed not MitM Proof or is that an oversight? (https://mariadb.org/mission-impossible-zero-configuration-ssl/)

The issue currently is:

java.rmi.RemoteException: (conn=34384) Self signed certificates. Either set sslMode=trust, set a password or provide server certificate to client; nested exception is:
java.sql.SQLNonTransientConnectionException: (conn=34384) Self signed certificates. Either set sslMode=trust, set a password or provide server certificate to client

as a password is set this error might be confusing, shouldn't it be "Either set sslMode=true, use a MitM-Proof auth plugin or provide server certificate to client" instead?

yes, error message has changed, and currently finalizing "zero configuration ssl" implementation. That is part of this task

released in SNAPSHOT version

👍 thanks, confirmed working now with latest SNAPSHOT build