Secure messaging facility system
Abstract
A secure message facility transfers authentication data between various applications, operating systems, and authentication devices and software in the form of messages. These messages comprise a data structure with a standard header with fields that describe the class, length, and type of message, and routing information. This header information is used to route the message to the appropriate handler. The messages are transferred between applications via the messaging facility DLL and the messaging facility Service. The messaging facility DLL is intended to be loaded by an application. The messaging facility DLL forms the messages, directs them to the appropriate messaging facility service (local or remote) and interprets the responses. The messages sent between the messaging facility DLL and messaging facility Service are extremely flexible and can be used to send any type of data or content of messages.
Claims
exact text as granted — not AI-modifiedIt is claimed:
1 . Software for transfer of user authentication data, comprising:
a. a DLL which communicates with application software; b. said DLL creates a message which includes the authentication data and destination information; and, c. said message communicates the authentication data from an origin and delivers the authentication data to a destination.
2 . The software of claim 1 , wherein said origin and said destination are each selected from a list consisting of local application software, remote application software, operating system, network software, local driver, remote driver, local authentication device and remote authentication device.
3 . The software of claim 1 , wherein at least one of said origin and said destination is an authentication device, and said authentication device is selected from the list consisting of passwords, tokens, SecurID, proximity devices, biometric authentication devices, fingerprint scanner, body feature scanner, body feature sensor, sound recorder, and voice recognition device.
4 . The software of claim 1 , wherein said DLL is compatible with Microsoft Windows NT/2000/2003/XP based 32 bit and 64 bit operating systems.
5 . The software of claim 1 , wherein said DLL is compatible with non-Microsoft Windows NT/2000/2003/XP based operating systems.
6 . The software of claim 1 , wherein said DLL functions when the user is attached to a domain.
7 . The software of claim 1 , wherein said DLL functions when the user is not attached to a domain.
8 . The software of claim 1 , further comprising a software developer's kit with an application programming interface to said software.
9 . The software of claim 1 , wherein at least one of said origin and said destination is located remotely, and remote communication is accomplished under TCP/IP.
10 . A method of transferring user authentication data comprising the steps of:
a. providing a DLL which creates a message which includes the authentication data; b. transferring the message from an origin; and, c. receiving the message by a destination and thereby receiving the authentication data.
11 . The method of claim 10 , wherein at least one of origin and the destination are located remotely.
12 . The method of claim 11 , wherein the transferring of the message utilizes TCP/IP.Join the waitlist — get patent alerts
Track US2014366109A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.