/
MS SQL connection fails for the ESE
MS SQL connection fails for the ESE
Problem
Using HiveMQ broker version >= 4.25.0
Using Enterprise Security Extension with MS SQL realm
The database name in the MS SQL realm configuration contains
;encrypt=false
When the Enterprise Security Extension is starting, it fails to connect to the MS SQL database.
Solution
Update the configuration of the MS SQL realm in the ESE config.xml file.
Remove
;encrypt=false
from the database name in the MS SQL realm configurationRestart the ESE.
Related articles
Related content
How to configure ESE to use Certificates Authentication
How to configure ESE to use Certificates Authentication
More like this
How to configure ESE to authenticate clients using client certificates and authorize using postgresSQL(without username/password)
How to configure ESE to authenticate clients using client certificates and authorize using postgresSQL(without username/password)
More like this
I created a permission, but creating a role fails
I created a permission, but creating a role fails
More like this
Configuring HiveMQ Security Extension with Active Directory for MQTT Client Authentication and Authorization
Configuring HiveMQ Security Extension with Active Directory for MQTT Client Authentication and Authorization
More like this
Using File RBAC and Enterprise security extension together
Using File RBAC and Enterprise security extension together
More like this
ERROR - Not able to create SSL server context. Reason: Not able to open or read KeyStore '/opt/hivemq/conf/xxxxx.p12' with type 'JKS'
ERROR - Not able to create SSL server context. Reason: Not able to open or read KeyStore '/opt/hivemq/conf/xxxxx.p12' with type 'JKS'
More like this