Database end-user identifier

• US 20090112981A1
• Filed: 10/14/2008
• Published: 04/30/2009
• Est. Priority Date: 10/25/2007
• Status: Abandoned Application

• Current Assignee: Sentrigo, LLC
• Original Assignee: Sentrigo, LLC
• Inventors: Markovich, Slavik
• Application Number:
  US12/285,747
• Publication Number:
  US 20090112981A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

A user identifier relay, comprising control logic adapted to relay an identifier of an application server user to a database associated with said application server, wherein said relay is performed via a transaction request from said application server to said database.

Claims

1. A user identifier relay, comprising control logic adapted to relay an identifier of an application server user to a database associated with said application server, wherein said relay is performed via a transaction request from said application server to said database.

2. The user identifier relay according to claim 1, wherein said identifier is selected from a group consisting of:

an Internet Protocol (IP) address, a login name, a Uniform Resource Locator (URL), a HyperText Transfer Protocol (HTTP) request method and a user environment variable.

3. The user identifier relay according to claim 1, wherein said control logic is embedded within said application server.

4. The user identifier relay according to claim 1, wherein said control logic is external to the application server.

5. The user identifier relay according to claim 1, further comprising an interface filter adapted to intercept said identifier.

6. The user identifier relay according to claim 1, further comprising an outgoing filter adapted to attach said identifier to said transaction request.

7. The user identifier relay according to claim 6, wherein said outgoing filter is further adapted to implant said identifier in an end-to-end metric of said transaction request.

8. The user identifier relay according to claim 6, wherein said outgoing filter is further adapted to implant said identifier in a connection property of said transaction request.

9. The user identifier relay according to claim 6, wherein said outgoing filter is further adapted to implant said identifier as a note in a Structured Query Language (SQL) query.

10. A system adapted to relay a user identifier, the system comprising:

an application server;

a database associated with said application server; and

control logic adapted to relay an identifier of a user of said application server to said database, wherein the relay is performed via a transaction request from the application server to the database.

11. The system according to claim 10, wherein said identifier is selected from a group consisting of:

an Internet Protocol (IP) address, a login name, a Uniform Resource Locator (URL), a HyperText Transfer Protocol (HTTP) request method and a user environment variable.

12. The system according to claim 10, wherein said control logic is embedded within said application server.

13. The system according to claim 10, wherein said control logic is external to the application server.

14. The system according to claim 10, wherein said control logic comprises an interface filter adapted to intercept said identifier.

15. The system according to claim 10, wherein said control logic comprises an outgoing filter adapted to attach said identifier to said transaction request.

16. The system according to claim 15, wherein said outgoing filter is further adapted to implant said identifier in an end-to-end metric of said transaction request.

17. The system according to claim 15, wherein said outgoing filter is further adapted to implant said identifier in a connection property of said transaction request.

18. The system according to claim 15, wherein said outgoing filter is further adapted to implant said identifier as a note in a Structured Query Language (SQL) query.