Secure authentication facility

• US 20070136581A1
• Filed: 02/13/2006
• Published: 06/14/2007
• Est. Priority Date: 02/15/2005
• Status: Abandoned Application

• Current Assignee: Sig-Tec
• Original Assignee: Sig-Tec
• Inventors: Hoghaug, Thomas, Hoghaug, Robert
• Application Number:
  US11/352,966
• Publication Number:
  US 20070136581A1
• Time in Patent Office: Days
• US Class Current: 713/168
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

Secure authentication facility coordinates user authentication for secure access to systems, software applications, and hardware and software resources. The secure authentication facility provides for user authentication using local or remote authentication devices, to authenticate to local or remote operating system, application software, or other resources. The secure authentication facility sends and receives authentication data by use of secure messaging facility to provide consistent handling of authentication regardless of where the various devices, software, and resources are located. The secure authentication facility comprises a DLL. A developer kit is provided to facilitate use of the secure authentication facility. The invention includes software for facilitating user authentication, and includes methods of providing user authentication.

Claims

1. Software for user authentication to access secure computer resource, comprising:

a. a DLL which communicates with user identification and authentication software;

b. said DLL also communicates with at least one authentication device; and

,

c. said DLL communicates with the user identification and authentication software and the at least one authentication device by sending and receiving messages via secure messaging facility.

2. The software of claim 1, wherein the user identification and authentication software is located remotely.

3. The software of claim 1, wherein at least one of the at least one authentication device is located remotely.

4. The software of claim 1, wherein at least one of the at least one authentication device is located locally.

5. The software of claim 1, wherein the computer resource is located remotely.

6. The software of claim 1, wherein at least one of the said at least one 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.

7. 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.

8. The software of claim 1, wherein said DLL functions when the user is attached to a domain.

9. The software of claim 1, wherein said DLL functions when the user is not attached to a domain.

10. The software of claim 1, further comprising a software developer kit with an application programming interface to said software.

11. The software of claim 1, wherein at least one of said DLL, the at least one authentication device, the user identification and authentication software, and the secure computer resource is located remotely, and remote communication is accomplished under TCP/IP.

12. A method of user authentication comprising the steps of:

a. providing a DLL which communicates authentication data and coordinates authentication among software and hardware elements;

b. providing a software developers kit for adapting operating system or application software to use of the DLL;

c. using the software developers kit to adapt operating system or application software to access the DLL; and

,

d. using the DLL to coordinate user authentication among software and hardware elements.

13. The method of claim 12, wherein at least one of the software and hardware elements are located remotely from the user.

14. The method of claim 13, wherein the DLL communicates authentication data to at least one of the remote software or hardware elements using TCP/IP.