SQL server middleware supports front-end and back-end password separation

After more than a month of careful analysis and research, the verification process of sql server was finally completed, and the verification process was implemented separately in the middleware oneproxy-for-sqlserver of sql server. Currently oneproxy-for-sqlserver has implemented the front-end and back-end password separation function. You can learn more about the situation through civilian software or follow the wiki of this project to learn about the situation.

As of version 1.1.0 of oneproxy-for-sqlserver, the password separation function is supported. oneproxy-for-sqlserver is developed under the open source framework oneproxy-monotor. The front end uses a different username and password to log in to the database to log in to the middleware oneproxy-for-sqlserver, and oneproxy-for-sqlserver uses another username and password to log in to the database. The following explains the configuration and usage:

[oneproxy]
logfile = oneproxy_log.log
pidfile = oneproxy_pid.pid
listen_addr = 0.0.0.0
listen_port = 9999,8888,7777,6666
httpserver_addr = 0.0.0.0
httpserver_port = 8080
log_level = error
data_dump = false
log_sql = false
clientusername = admin
clientpassword = 123456
passwordseparate = true

[database_1433]
host = 127.0.0.1
port = 1433
username = sa
password = 0000 

[sqlserver_9999]
dbmastergroup = database_1433
classname = SSProtocol
frontport = 0

The above is the content in the configuration file. The configuration related to password separation is under the [oneproxy] and [database_xxx] tags. The following is the configuration under the [oneproxy] tag. This configuration is the username and password used by the client. passwordseparate instructs the middleware to use this feature or not. By default (without this configuration item), it is true. If you need to turn off the password separation function, just set this configuration to false.

clientusername = admin
clientpassword = 123456
passwordseparate = true

At the same time, it should be noted that the database information must be placed under the [database_xxx] tag, and the name of the tag must start with database. The username and password to log in to the database must be placed under the database label and specified by username and password.

Test environment:

Server version:

Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 14393: ) (Hypervisor)

Client program and version:

1. sqlserverjdbc4

2. Microsoft SQL Server Manager studio

3. sqlstress