A database virtual account proxy identity authentication and proxy access method

By using the same authentication server and pseudo-client as the target database in the database virtual account proxy authentication and proxy access method, a communication pipeline is established to realize that the real client accesses the target database without password, and the account password in the existing technology is solved Sharing and security issues improve database security.

CN118784373BActive Publication Date: 2024-12-06PALADI NETWORK TECH HANGZHOU
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202411258925.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-10
Publication Date
2024-12-06
Estimated Expiration
2044-09-10

AI Technical Summary

Technical Problem

The existing database virtual account proxy access technology requires adding a virtual account to the target database or forcibly cracked login verification, which cannot achieve password-free access to the real client and cannot solve the problem of password sharing of database accounts, increasing management and security risks.

Method used

Using the same authentication server and pseudo-client as the target database type and version, a communication pipeline is established through a virtual login agent and a real login agent, so that the real client can authenticate and access without knowing the target database account password, maximum Minimize the exposure of account passwords.

Benefits of technology

It realizes that when the real client does not need to know the target database account password, log in through a virtual account and use the real account permissions, minimizes the exposure of the database account password, improves database security and solves the problem of account password sharing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118784373B_ABST
    Figure CN118784373B_ABST
Patent Text Reader

Abstract

The present invention discloses a method for proxy identity authentication and proxy access to a database virtual account, comprising: using a database of the same type and version as a target database as an identity authentication server for a virtual account, using a virtual login agent to proxy data communication between the identity authentication server and a real client, and realizing virtual account identity authentication from the real client to the identity authentication server; preparing a pseudo client with the same operating system and database protocol version as the real client, using a real login agent to proxy data communication between the pseudo client and the target database, and realizing real account identity authentication from the pseudo client to the target database; establishing a communication pipeline between the virtual login agent and the real login agent, and realizing proxy access from the real client to the target database based on the communication pipeline after the identity authentication is successful. As a new method, the security and secure access of the real account of the database can be realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of data security, and in particular relates to a database virtual account proxy identity authentication and proxy access method. Background Art

[0002] To achieve database account password security, it is usually necessary to frequently change passwords and increase password complexity, and then distribute the modified account passwords to applications and individuals who need to use database accounts to achieve database access security. Various database application scenarios are extensive, making it difficult for users to safely and conveniently implement database account passwords, and it is difficult to conveniently and economically deliver modified database account passwords.

[0003] The existing method of publishing through the bastion host database client application can only realize the delivery of database account and password in user operation and maintenance scenarios. Enterprise password safe can only be applied to mature and stable business database account and password applications through password push and fingerprint acquisition. In application scenarios such as enterprise development, scripting applications, DOCKER applications, sandbox sandbox, data calculation and analysis, and other CS clients, users still have to deliver the target database account and password, making the database account and password security measures ineffective and causing additional management and operation burdens. Moreover, it still cannot solve the problem of database account and password sharing. Therefore, database virtual account proxy access database technology came into being. As a supplementary technology for enterprise database account and password security measures, it can minimize the exposure of the real database account and password and solve the problem of enterprise database application sharing accounts.

[0004] The existing database virtual account proxy access database technology mainly includes two methods, one of which is the proxy user identity authentication and connection technology, referred to as the proxy user method, which specifically includes: by creating a virtual account on the target database, and then the administrator authorizes the virtual account to authorize the real target account and its permissions that it can proxy. In this way, the user only needs to log in by using the virtual account, without knowing the real target account of the database, and can log in to the target database in the proxy mode of the real target account and have the identity and permissions of the target account.

[0005] The other method is to forcibly modify various verification challenges in the database authentication process during the proxy process, which is referred to as the verification cracking method. Specifically, it includes: verifying the virtual account password through the database access password verification algorithm, and using the target database account password according to the database account password verification process and challenges to modify the proxy's application protocol password verification data, so as to log in to the target database with the target database account password, thereby realizing virtual account proxy access. Summary of the invention

[0006] In view of the above, the purpose of the present invention is to provide a database virtual account proxy identity authentication and proxy access method, which as a new method, does not require adding any virtual account on the target database, nor does it require forcibly cracking the virtual account proxy login target database process of the database login verification protocol.

[0007] To achieve the above-mentioned purpose of the invention, an embodiment provides a database virtual account proxy identity authentication and proxy access method, including:

[0008] A database of the same type and version as the target database is used as the authentication server of the virtual account, and virtual account authentication information is added to the authentication server. A virtual login agent is used to proxy data communication between the authentication server and the real client, and virtual account authentication is implemented from the real client to the authentication server based on the virtual account authentication information.

[0009] Prepare a pseudo client with the same operating system and database protocol version as the real client, use a real login agent to proxy the data communication between the pseudo client and the target database, and implement real account identity authentication from the pseudo client to the target database;

[0010] A communication channel is established between the virtual login agent and the real login agent, and after the identity authentication is successful, the real client's proxy access to the target database is implemented based on the communication channel.

[0011] Preferably, the method further includes: in the virtual account identity authentication stage and the real account identity authentication stage, according to different database protocol characteristics, forwarding corresponding protocol data packets or protocol control fields, overwriting or modifying corresponding protocol data packets or protocol control fields, so as to establish a data forwarding channel between the real client and the target database through the communication pipeline.

[0012] Preferably, database protocol negotiation is performed during the virtual account identity authentication stage and the real account identity authentication stage, and the negotiation content includes whether to forward the protocol data packets, modify the fields or not, forward more or less fields, the real client traffic or fields forwarded by the virtual login agent to the real login agent, and the target database traffic or fields forwarded by the real login agent to the virtual login agent.

[0013] Preferably, the method also includes: the virtual login agent program identifies the authentication success data packet after the virtual account identity authentication is successfully performed and the real login agent program identifies the authentication success data packet after the real login agent program successfully performs the real account identity authentication, and the real login agent program must forward the whole or part of the fields of the real authentication success data packet returned by the target database to the pseudo client to the virtual login agent program; according to the characteristics of the database protocol, the virtual login agent program replaces the whole or part of the fields of the virtual authentication success data packet returned by the authentication server to the real client with the whole or part of the fields of the real authentication success data packet, and forwards the replaced authentication success data packet to the real client.

[0014] Preferably, the method also includes: after the virtual login agent successfully performs virtual account identity authentication and after the real login agent successfully performs real account identity authentication, according to the database protocol and its version requirements, the real login agent identifies part of the session control fields in the real identity authentication success data packet, and then modifies the corresponding session control fields in the virtual identity authentication success data packet while the virtual login agent forwards the virtual identity authentication success data packet.

[0015] Preferably, the method further includes: after the virtual login agent successfully performs virtual account identity authentication, there is no more communication traffic between the virtual login agent and the identity authentication server; after the real login agent successfully performs real account identity authentication, there is no more communication traffic between the real login agent and the pseudo client.

[0016] Preferably, after the identity authentication is successful, proxy access from the real client to the target database is implemented based on the communication pipeline, including:

[0017] The virtual login agent forwards the request data of the real client to the real login agent through the communication pipeline, and the real login agent then forwards the request data to the target database. Similarly, the real login agent forwards the return data formed by the target database based on the request data to the virtual login agent through the communication pipeline, and the virtual login agent then forwards the return data to the real client. During the forwarding process, the virtual login agent or the real login agent modifies the virtual account to the real account in the data packet, so that the real client can log in to the target database through the virtual account without knowing the target database account password and use the identity authority of the real account to operate on the target database.

[0018] Preferably, the order in which the virtual login agent program and the real login agent program are started is flexibly set according to the implementation method, including:

[0019] After determining the real client database protocol version, the virtual login agent creates a domain socket and prepares to communicate with the real login agent; then starts the real login agent to dynamically listen for connection requests from the pseudo client; then starts the pseudo client program, the pseudo client connects to the real login agent, and the real login agent connects to the target database.

[0020] Preferably, the main protocol negotiation data in the request data of the real client to the virtual login agent is different from the corresponding request protocol negotiation data of the real login agent to the target database; the main protocol negotiation data in the return data of the virtual login agent to the real client is different from the corresponding return protocol negotiation data of the target database to the real login agent.

[0021] Compared with the prior art, the present invention has the following beneficial effects:

[0022] Introduce a database of the same type and version as the target database as the authentication server, and introduce a virtual login agent to authenticate the virtual account of the real client to the authentication server; introduce a pseudo client with the same operating system and database protocol version as the real client, and introduce a real login agent to authenticate the real account of the target database; and establish a communication channel between the virtual login agent and the real login agent, and after the authentication is successful, implement proxy access from the real client to the target database based on the communication channel. In this way, the real client can log in to the target database through a virtual account without knowing the target database account password and use the identity permissions of the real account to operate the target database, which minimizes the exposure of the real account and password of the database and realizes the security of the database server account and password. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 It is a flowchart of components and the identity authentication stage involved in the database virtual account proxy identity authentication and proxy access method provided in the embodiment;

[0025] Figure 2 It is a flowchart of proxy access from a real client to a target database after both the authentications are successful in the database virtual account proxy identity authentication and proxy access method provided in the embodiment. DETAILED DESCRIPTION

[0026] To make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific implementation methods described herein are only used to explain the present invention and do not limit the scope of protection of the present invention.

[0027] The inventive concept of the present invention is: a new method is proposed to realize database virtual account proxy identity authentication and proxy access, the method does not need to add any virtual account on the target database, and does not need to forcibly crack the virtual account proxy login target database process of the database login verification protocol. The access to the target database is proxied by a real client, and through appropriate control of two-way access data, during this access process, the user does not need to know the real account and password of the database, which minimizes the exposure of the real account and password of the database and realizes the security of the database server account and password.

[0028] like Figure 1 As shown, an embodiment provides a database virtual account proxy identity authentication and proxy access method, and the components implementing the method include an authentication server, a virtual login agent (referred to as virtual agent), a real client, a pseudo client, a real login agent (referred to as real agent), and a target database. The purpose of these components is to enable the real client to access the target database while ensuring the security of the real account and password of the database.

[0029] The authentication server uses a database of the same type and version as the target database to facilitate authentication of the virtual account. Here, it is understood that when the major version of the database is the same, the database version is considered to be the same. The authentication server adds virtual account authentication information, where the virtual account authentication information includes the virtual account, virtual account password, and database / instance, etc.

[0030] The virtual proxy is used to proxy the data communication between the authentication server and the real client. Whether the virtual proxy uses the Transport Layer Security (TLS) protocol to encrypt the communication depends on the protocol support requirements of the real client. As a communication bridge between the authentication server and the real client, the virtual proxy can transfer the virtual account authentication process, realize the virtual account authentication from the real client to the authentication server, and recognize the successful message of the real client logging into the authentication server during the conversion process.

[0031] A pseudo client refers to a non-real client that has the same operating system (such as Linux, Windows, etc.) and database protocol version as a real client. Here, it is understood that when the major version of the database protocol version is the same, the database protocol version is considered to be the same. The pseudo client can log in to the target database using the real account of the target database.

[0032] The real proxy is used to proxy the data communication between the pseudo client and the target database. Whether the real proxy uses the Transport Layer Security Protocol (TLS) to encrypt the communication depends on the target database settings. As a communication bridge between the pseudo client and the target database, the real proxy can transfer the real account authentication process to realize the real account authentication from the pseudo client to the target database. At the same time, it can identify the successful message of the pseudo client logging into the target database during the conversion process.

[0033] A communication channel is also established between the virtual agent and the real agent, and after both the virtual identity and the real identity are successfully verified, the proxy access of the real client to the target database is realized based on the communication channel, that is, data forwarding between the real client and the target database is realized.

[0034] The order of starting the virtual agent and the real agent can be flexibly set according to the implementation method, and the communication method between the two can also be flexibly used. Similarly, whether the real agent uses a dynamic listening port, the physical location of the pseudo client, and the physical location of the authentication server are not restricted. An optional order of starting the virtual agent and the real agent is set as follows: after the virtual agent determines the real client database protocol version, it creates a domain socket and prepares to communicate with the real agent; then starts the real agent and dynamically listens for the connection request of the pseudo client; then starts the pseudo client program, the pseudo client connects to the real agent, and the real agent connects to the target database.

[0035] In the virtual account authentication stage and the real account authentication stage, that is, the database protocol negotiation stage, according to different database protocol characteristics, the corresponding protocol data packets or protocol control fields are forwarded, the corresponding protocol data packets or protocol control fields are overwritten, or the corresponding protocol data packets or protocol control fields are modified, so as to establish a data forwarding channel between the real client and the target database through the communication pipeline. If the database protocol negotiation or database protocol capability attributes (usually called Capabilities and Extended Capabilities) are simple to control, there is no need to forward or modify any protocol data packets, nor is there any need to forward or modify any protocol control fields. When conducting database protocol negotiation, the optional negotiation content includes whether to forward or not forward protocol data packets, whether to modify or not modify fields, whether to forward more or less fields, the real client traffic or fields forwarded by the virtual proxy to the real proxy, and the target database traffic or fields forwarded by the real proxy to the virtual proxy.

[0036] like Figure 2 As shown, after the virtual agent successfully authenticates the virtual account, there is no more communication traffic between the virtual agent and the authentication server, that is, after the virtual authentication is successful, the virtual agent cuts off the communication between the virtual agent and the authentication server. Similarly, after the real agent successfully authenticates the real account, there is no more communication traffic between the real agent and the pseudo client, that is, after the real authentication is successful, the real agent disconnects the connection communication between the real agent and the pseudo client.

[0037] In one embodiment, after the virtual agent successfully authenticates the virtual account and after the real agent successfully authenticates the real account, the authentication success packets can be identified respectively, and according to the specific characteristics of the database protocol, the whole or part of the fields of the real authentication success packet returned by the real agent target database can be used to replace the whole or part of the fields of the virtual authentication success packet returned by the virtual agent authentication server to the real client. This is because some database protocols carry relevant database session control information in the login authentication success packet. In this case, the real agent must forward the whole or part of the fields of the real authentication success packet returned by the target database to the pseudo-client to the virtual agent. According to the characteristics of the database protocol, the virtual agent replaces the whole or part of the fields of the virtual authentication success packet returned by the authentication server to the real client with the whole or part of the fields of the real authentication success packet, and forwards the replaced authentication success packet to the real client.

[0038] In another embodiment, after the virtual agent successfully authenticates the virtual account identity and the real agent successfully authenticates the real account identity, the real agent can also identify some session control fields in the real identity authentication success data packet according to the database protocol and its version requirements, and then modify the corresponding session control fields in the virtual identity authentication success data packet while the virtual agent forwards the virtual identity authentication success data packet.

[0039] After both the virtual identity and real identity authentication are successful, the proxy access of the real client to the target database is realized based on the communication pipeline built between the virtual proxy and the real proxy, which specifically includes: the virtual proxy forwards the request data of the real client to the real proxy through the communication pipeline, and the real proxy then forwards the request data to the target database. Similarly, the real proxy forwards the return data formed by the target database based on the request data to the virtual proxy through the communication pipeline, and the virtual proxy then forwards the return data to the real client. During the forwarding process, the virtual proxy or the real proxy can modify the virtual account in the data packet to the real account according to the specific implementation method, so that the real client can log in to the target database through the virtual account without knowing the target database account password and use the identity authority of the real account to operate the target database. For example, in Oracle, the following SQL statement: ALTER SESSION SET CURRENT SCHEMA='xxxx' (its meaning is to modify the "mode" of the session, change the current mode to the "xxxx" mode, and the xxxx mode in Oracle is the same as the target database user name). Some Oracle client software will execute such statements by default after successful login. However, because this user and mode do not exist in the target database, the user and mode represented by the virtual account must be replaced with the real account and mode of the target database.

[0040] The important feature of the present invention in network traffic is: in the identity authentication stage, in the request data from the real client to the virtual agent, the main protocol negotiation data (i.e., most of the data except the forwarding traffic, which does not contain the identity authentication data) is completely different from the corresponding protocol negotiation data from the pseudo client to the target database; similarly, in the identity authentication stage, in the return data from the virtual agent to the real client, the main protocol negotiation data (i.e., most of the data except the forwarding traffic, which does not contain the identity authentication data) is completely different from the corresponding protocol negotiation data from the target database to the pseudo client. Usually, the virtual agent and the real agent will be implemented and run on the same server, which is called a virtual server, that is: the main body of the request protocol negotiation data from the real client to the virtual server is different from the request protocol negotiation data from the virtual server to the target database; the main body of the return protocol negotiation data from the virtual server to the real client is different from the return protocol negotiation data from the target database to the virtual server. Of course, since the virtual account password is different from the real account password, in the identity authentication stage, the two corresponding identity authentication related data must be different. This feature is an important network traffic representation that distinguishes the present invention from the verification cracking method. Since the verification cracking method uses a virtual server to directly proxy and forward the traffic between the real client and the target database, only the identity authentication related data is changed. Therefore, all the protocol negotiation data in the identity authentication phase between the virtual server and the real client, and between the virtual server and the target database in the verification cracking method implementation example are exactly the same, and only the identity authentication related data is different.

[0041] The following is a detailed description of the above method using the example of a virtual account proxy based on the ORACLE protocol to log in to the target database. Before identity authentication, the ORACLE protocol needs to negotiate relevant protocol details, such as data type negotiation, data protocol negotiation, font negotiation, etc. In the protocol data part, when Data ID is 1, it indicates protocol type negotiation, that is, the real client sends a Set protocol packet to the authentication server through the virtual proxy. After receiving the Set protocol data packet from the real client, the authentication server needs to reply with the corresponding Set protocol packet to tell the real client how to identify the data protocol and data type returned by the authentication server. After receiving the Set protocol packet from the authentication server, the real client will parse the network data packet with the corresponding protocol and data format, and then can communicate normally.

[0042] In the embodiment, the Set protocol packet returned by the target database to the pseudo client is also required to replace the Set protocol packet returned by the identity authentication server to the real client, so that the real client can identify the protocol and data format used by the target database, and use the data format it can recognize to send request data to the target database. Since the real client and the pseudo client database protocol version numbers are the same or similar, and the target database and the identity authentication server have the same major version number, the data type (Set Datatype) interaction part of ORACLE will not affect the stability of protocol identification and subsequent forwarding.

[0043] The specific implementation methods described above provide a detailed description of the technical solutions and beneficial effects of the present invention. It should be understood that the above is only the most preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, supplements and equivalent substitutions made within the scope of the principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A database virtual account proxy identity authentication and proxy access method, It is characterized in that The following steps are involved: A database of the same type and version as the target database is used as the authentication server of the virtual account, and virtual account authentication information is added to the authentication server. A virtual login agent is used to proxy data communication between the authentication server and the real client, and virtual account authentication is implemented from the real client to the authentication server based on the virtual account authentication information. Prepare a pseudo client with the same operating system and database protocol version as the real client, use a real login agent to proxy the data communication between the pseudo client and the target database, and implement real account identity authentication from the pseudo client to the target database; A communication channel is established between the virtual login agent and the real login agent, and after the identity authentication is successful, the real client's proxy access to the target database is implemented based on the communication channel.

2. The database virtual account proxy identity authentication and proxy access method according to claim 1, It is characterized in that Also includes: During the virtual account identity authentication stage and the real account identity authentication stage, corresponding protocol data packets or protocol control fields are forwarded, overwritten or modified according to different database protocol characteristics, so as to establish a data forwarding channel between the real client and the target database through the communication pipeline.

3. The database virtual account proxy identity authentication and proxy access method according to claim 2, It is characterized in that During the virtual account authentication stage and the real account authentication stage, database protocol negotiation is performed. The negotiation content includes whether to forward the protocol data packets or not, whether to modify the fields or not, how many fields to forward, the real client traffic or fields forwarded by the virtual login agent to the real login agent, and the target database traffic or fields forwarded by the real login agent to the virtual login agent.

4. The database virtual account proxy identity authentication and proxy access method according to claim 1, It is characterized in that Also includes: After the virtual account authentication is successfully performed, and the real login agent is after the real account authentication is successfully performed, the virtual login agent respectively identifies the authentication success data packet, and the real login agent must forward the whole or part of the fields of the real authentication success data packet returned by the target database to the pseudo client to the virtual login agent. According to the characteristics of the database protocol, the virtual login agent replaces the whole or part of the fields of the virtual authentication success data packet returned by the authentication server to the real client with the whole or part of the fields of the real authentication success data packet, and forwards the replaced authentication success data packet to the real client.

5. The database virtual account proxy identity authentication and proxy access method according to claim 1, It is characterized in that Also includes: After the virtual login agent successfully authenticates the virtual account and the real login agent successfully authenticates the real account, the real login agent identifies some session control fields in the real authentication success data packet according to the database protocol and its version requirements, and then modifies the corresponding session control fields in the virtual authentication success data packet while the virtual login agent forwards the virtual authentication success data packet.

6. The database virtual account proxy identity authentication and proxy access method according to claim 1, It is characterized in that Also includes: After the virtual login agent successfully authenticates the virtual account, there is no more communication traffic between the virtual login agent and the authentication server; After the real login agent successfully authenticates the real account, there is no more communication traffic between the real login agent and the fake client.

7. The database virtual account proxy identity authentication and proxy access method according to claim 1, It is characterized in that After the authentication is successful, proxy access from the real client to the target database is implemented based on the communication pipeline, including: The virtual login agent forwards the request data of the real client to the real login agent through the communication pipeline, and the real login agent then forwards the request data to the target database. Similarly, the real login agent forwards the return data formed by the target database based on the request data to the virtual login agent through the communication pipeline, and the virtual login agent then forwards the return data to the real client. During the forwarding process, the virtual login agent or the real login agent modifies the virtual account to the real account in the data packet, so that the real client can log in to the target database through the virtual account without knowing the target database account password and use the identity authority of the real account to operate on the target database.

8. The database virtual account proxy identity authentication and proxy access method according to claim 1, It is characterized in that The order in which the virtual login agent program and the real login agent program are started is flexibly set according to the implementation method, including: After determining the real client database protocol version, the virtual login agent creates a domain socket and prepares to communicate with the real login agent; then starts the real login agent to dynamically listen for connection requests from the pseudo client; then starts the pseudo client program, the pseudo client connects to the real login agent, and the real login agent connects to the target database.

9. The database virtual account proxy identity authentication and proxy access method according to claim 1, It is characterized in that The subject protocol negotiation data in the request data from the real client to the virtual login agent is different from the corresponding request protocol negotiation data from the real login agent to the target database; The principal protocol negotiation data in the return data from the virtual login agent to the real client is different from the corresponding return protocol negotiation data from the target database to the real login agent.

Citation Information

Patent Citations

  • Login method, terminal device and communication system

    CN105516163A

  • EID security control method and system based on eID

    CN106911627A

  • Method for replacing user name and password in ORACLE10G authentication process based on proxy

    CN115632892A

  • Database account hosting method and device, computer equipment and storage medium

    CN116522308A

  • Remote service management method and device, equipment and storage medium

    CN117459513A