ahaleiii
January 7, 2021, 6:40pm
17
This might be related to the usage of Azure Database for PostgreSQL. There are a few other threads which suggest that gssEncMode is not currently supported by Azure Postgres and should be disabled, specifically around the upgrade to SonarQube 8.5.
SonarQube updated the postgres driver from 42.2.14 -> 42.2.16.
Due changes on the default gssEncMode, this version and therefore SonarQube 8.5 is incompatible on Azure’s PostreSQL offering…
a workaround is to add ?gssEncMode=disable to your connection string.
maybe you would like to notify your users about that - or upgrade the driver to version xxxx.17 in the upcoming version.
Cheers, Adrian
see here too:
Hi @Jos_Wilbrink ,
we did some investigation and noticed that we upgraded the postgresql jdbc driver by 2 patch versions ( 42.2.14 to 42.2.16 ). and with that we dug deeper if there are any issues with this version connected to azure, and indeed there is one documented in the azure docs that hits what you observed perfectly!
please try to disable GSS explicitly in the connect string, so like this:
jdbc:postgresql://xxxxx.postgres.database.azure.com:5432/xxxx?gssEncMode=disable
Hey, is your database hosted on Azure PostgreSQL PaaS? If yes, have a look here , there is a workaround to explicitly disable gssEncMode.
2 Likes