Commented by: @mrotteveel

The requirement to specify a connection character set was dropped with Jaybird 3.0.2, so if your main complaint is about that, then you are not using Jaybird 3.0.2, but an earlier version (3.0.0 or 3.0.1).

As to the "No valid encoding definition" error, the `charSet` property expects a Java character set name, and NONE is not a Java character set name, but a Firebird character set. Use property encoding instead if you want to specify NONE (see also https://www.firebirdsql.org/file/documentation/drivers_documentation/java/faq.html#how-can-i-specify-the-connection-character-set) .

As to the "Incompatible wire encryption levels" error, Firebird 3 by default requires wire protocol encryption, which Jaybird 3 doesn't support (it will be available in Jaybird 4). You need to configure Firebird (in firebird.conf) by setting WireCrypt to Enabled as documented:
- https://www.firebirdsql.org/file/documentation/drivers_documentation/java/3.0.2/release_notes.html#notes-on-firebird-3-support
- https://github.com/FirebirdSQL/jaybird/wiki/Jaybird-and-Firebird-3

PS This is really a support question, and the tracker is intended for bug reports only. In the future could you post these types of questions to the Firebird-Java mailinglist instead . And if you do post a bug report, then please make sure you post all relevant reproduction information (steps to reproduce or a sample program, full exception stacktraces and logs).