I'm trying to reach a Postgresql base via ssl from the builtin database browser in IntelliJ IDEA Ultimate.
In datasource properties I have added the same key and cert pem-files that work fine with psql and pgadmin, but on "Test Connection" I just get
[08006] SSL error: No X509TrustManager implementation available
Updated in response to Andrey's comment:
If I add the local root certificate (which neither psql or pgadmin needed) in the CA file setting, the error changes to
[08006] SSL error: No trusting managers found for ECDHE_RSA
What am I missing?
Can anyone confirm a working db-connection using:
IntelliJ IDEA Ultimate Edition 2019.2 or later
Ssl
PostgreSQL 12.x or later
I had the same problem. I updated my intelliJ to latest version (IntelliJ IDEA 2021.3.3 - ultimate). Then it started working.
Related
I am trying to add a PostgreSQL database to DBeaver and am getting the following error when I try to connect to the database. I'm using DBeaver Version 7.2.3.202010191702. And after receiving this message I installed the latest version of the JDK (11.0.9) and pgJDBC (postgresql-42.2.18.jar). I've not had PostgreSQL on this machine yet, so it's a fresh install of the latest version (v13). Any suggestions?
SCRAM authentication is not supported by this driver. You need JDK >= 8 and pgjdbc >= 42.2.0 (not ".jre" vesions)
I had same error and in my situation I had old database drivers. These steps fixed it for me:
Go to Database Driver Manager
Select PostgreSQL (either double click or single select and then "Edit ...")
Click on "Download/Update"
Choose newer version (see bold version text) e.g. 42.2.18 for org.postgresql:postgresql:RELEASE
Press "Download"
Even using all the tips and tricks found on SO I was not able to connect to PGSQL 14 DBs.
I fixed it by using PostgreSQL (Old) driver, and it now works.
The problem I faced was identical, and what resolved it for me was:
Removing the previous PostgreSQL JDBC from the lib folder.
Downloading the latest PostgreSQL JDBC.
Substituting the old JDBC with the new one.
I had a problem similar to yours. This is the way to fix it:
open folder PostgreSQL\14\data, edit postgresql.config fix password_encryption to md5
alter all METHOD value to password in pg_hba.conf
restart postgres server
In my case, JRE version postgres being used in Pom.xml. Update it to the latest version and it should work
Recently I installed PostgreSQL 10.4, but it was losing connection all the time. I uninstalled it, removed the data folder and installed version 9.6, which didn't help, so I uninstalled it as well and removed the data folder. I installed 10.4 again hoping that it will work well this time.
When I opened pgAdmin it showed as if version 9.6 was still installed apart form the 10.4 (which should be there). I tried creating a user in it (to see if it really works) and it created it successfully, but after further investigation I realized that it created the same user in the 10.4 installation. It must have been the same installation, but pgAdmin saw it as two separate ones. I deleted both installations form pgAdmin and reinstalled version 10.4.
Everything works fine now, but I still wanted to ask what might have caused this issue? Can it cause problems for my existing db in the future?
It's not "PostgreSQL" that remembered the installation. It's pgAdmin where you simply didn't delete the configured connection. Connection information is something specific to the SQL client, not the database server.
The existing connection definition uses the same hostname, port and apparently password that was valid for a running 9.6 server or the new Postgres 10 server. The name of that "server" is something that is specified in pgAdmin and has nothing to do with the actual Postgres installation. You could have named the "9.6 Server" connection "Connect to some nice DBMS" instead.
That information is not stored together with the PostgreSQL installation, but in your user profile.
I am using MariaDB and am currently trying to create a database connection using DTP.
When I test the connection the ping is succeeding:
When I click on 'Finish' afterwards, the 'Database Connections' Folder is still empty:
Am I missing a step or am I encountering a bug?
working with Eclipse Neo.3 on Arch Linux
The solution to this problem was rather simple: uninstall DTP and install DBeaver.
I didnt knew that DTP was outdated and got more or less abandoned by his community.
There are many posts here and all over the web about getting the message:
Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled)
when trying to connect a a MySQL database. In my case, it's coming from MySQLWorkbench version 6.3 newly installed on a almost as newly install Ubuntu 15.10 system.
The advice is always to update the password on the database to use the new authentication.
However, that is not my problem, and that's not what the message says. It says that the OLD authentication is being used when the database wants the NEW authentication.
This version of MySQLWorkbench has a checkbox that tells it to use the OLD authentication, which is unchecked, but, from the message, it appears to be using the OLD authentication all the time.
I can connect to the database easily from version 5.2 of MySQLWorkbench running on Mac OS X.
I tried installing an older version of MySQLWorkbench on my Ubuntu system, but there were numerous errors with the package, which is intended for an earlier version of Ubuntu.
Any ideas about how I can force MySQLWorkbench to use the NEW authentication? I tried setting:
useLegacyAuth=0
but that did nothing.
OK, got the answer. The hosting outfit (Siteground) sets up MySQL passwords to work with EITHER the legacy or the new protocol. I don't know if this is homegrown, some sort of plugin that's generally available, or a standard MySQL feature. With this option, MySQLWorkbench fails to connect and erroneously reports the problem as the server not supporting the old protocol. Probably it's just confused by the error response which its programmers didn't anticipate.
Siteground very quickly set my password to use the new authentication ONLY upon my request, and then MySQLWorkbench connected with no problem.
I'd like to create a local copy on my Windows 8 machine to further develop existing extensions and test upcoming updates of a Typo3 6.1.7 installation. I tared everything up including the MySQL DB dump, extracted it into a fresh install of XAMPP and imported the database. After adjusting the DB and OpenSSL settings in the LocalConfiguration.php I tried to login with my password, but I get a message stating my credentials must be wrong.
The LoginSecurity on BE is configured with RSA, and the InstallTool states that my OpenSSL config is running correct. Then why can't I login? What did I miss?
Searching what could be wrong I looked at the requirements for Typo3 6.1.x, and it clearly states that it supports MySQL 5.5.x. Sure enough, the freshly installed XAMPP uses MySQL 5.6. I removed it, installed the other current XAMPP package with MySQL 5.5 and now it works.