Issue

This document explains the cause and resolution method of connection errors caused by SSL (TLS) protocol mismatch when integrating MS SQL Server DB Link (Gateway) with Tibero.

It also summarizes the authentication error situations caused by TLS version differences and the resolution method through Java security setting changes.

Applicable Environment

This document was verified in the following environment.

• Tibero 7 (tbgw)

• Target DB: MS SQL Server

• Integration Method: Gateway + DB Link

Tibero → MS SQL Server Connection Test Failure

The following error occurs when connecting to Gateway in tbsql.

tbsql test/"test@1234"@msgate_test

Error message

TBR-130005: Authentication failed.
- The driver cannot establish a secure connection to SQL Server using SSL (Secure Sockets Layer) encryption.
- Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS12]"

DB Link Connection Failure

SELECT * FROM INFORMATION_SCHEMA.TABLES@DL_TEST;

Error message

TBR-12130: Unable to connect to remote database
TBR-130005: Authentication failed.
(The server selected protocol version TLS10 is not accepted by client preferences [TLS12])

Cause

This error occurs due to a mismatch in TLS protocol versions.

• MS SQL Server uses TLS 1.0 based communication.

• Tibero Gateway allows only TLS 1.2 or higher according to Java security policies.

• TLS negotiation fails because TLS 1.0 / 1.1 are disabled in the Java java.security settings.

Solutions

Check Tibero Gateway Configuration

Verify that the Gateway information is properly configured in the tbdsn.tbr file.

msgate_test=(
 (GATEWAY=
  (LISTENER=
   (HOST=localhost)
   (PORT=9093)
  )
  (TARGET=111.111.111.111:1444:C_TEST)
  (TX_MODE=LOCAL)
 )
)

Modify Java Security Settings (Change TLS Policy)

Edit the Java security settings file.

vi /usr/lib/java/openjdk-8u342-b07/jre/lib/security/java.security

Remove TLSv1, TLSv1.1 from the following entry.

jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1

Configure to allow use of TLS 1.2 or higher.

Terminate Tibero Java Gateway Process

Check the Gateway process.

ps -ef | grep java

After confirming the process, terminate it.

kill -9 <PID>

If necessary, check port usage.

netstat -nap | grep 9093

Restart Gateway

Restart the Gateway.

cd $TB_HOME/client/tbJavaGW
./tbgw

Example startup log:

Name : TmaxTibero JAVA GATEWAY
Database: 0
Port : 9093

Post-Action Verification

Gateway Connection Test

tbsql test/"test@1234"@msgate_test 

Result:

Connected to SQL SERVER GATEWAY using msgate_test.

Confirm successful connection.

DB Link Connection Test

SELECT * FROM INFORMATION_SCHEMA.TABLES@DL_TEST;

Result:

1 row selected.

Confirm successful query.

Note

• This issue occurs due to mismatch between MS SQL Server TLS version and Java security policy.

• Gateway restart is required after changing Java security settings.