Object management for external off-host authentication processing systems

1. A method, comprising:

identifying, by an Information Handling System (IHS), raw data to be stored within an object in an off-host memory of an external off-host authentication processing system coupled to the IHS, wherein the external off-host authentication processing system provides a hardware environment segregated from the IHS;

collecting authentication data from a user by prompting the user;

silently generating a system identification (ID) that uniquely characterizes the IHS without prompting the user;

storing the authentication data, the system ID, and the raw data as part of the object in the off-host memory;

receiving, at the external off-host authentication processing system, a request from a calling application executed by the IHS to access the object stored in the off-host memory;

making a call, via a protected Application Programming Interface (API), to retrieve the object;

collecting, via the IHS, new authentication data from a user by prompting the user;

silently generating, via the IHS, a new system ID without prompting the user;

determining, by the external off-host authentication processing system, that the new authentication data and new system ID match the authentication data and system ID stored in the object; and

retrieving, by the external off-host authentication processing system, the object from the off-host memory.

2. The method of claim 1 , wherein the raw data includes an encryption key or fingerprint template.

3. The method of claim 1 , wherein the authentication data includes a fingerprint template, a magnetic card scan, a Radio Frequency Identification (RFID) scan, a Smart Card scan, a face recognition template, an iris template, a certificate, or a passcode.

4. The method of claim 1 , wherein generating the system ID includes retrieving or generating an identification of a hardware component of the IHS.

5. The method of claim 4 , wherein the system ID includes an identification of a Central Processing Unit (CPU) of the IHS.

6. The method of claim 1 , wherein generating the system ID includes retrieving or generating an identification or signature of a software component installed in the IHS.

7. The method of claim 1 , wherein the external off-host authentication processing system is coupled to the IHS using a protocol that cryptographically tie communications between the external off-host authentication processing system and an embedded controller (EC) of the IHS without intervention by any Operating System (OS) executed by the IHS.

8. The method of claim 1 , further comprising:

receiving, at the external off-host authentication processing system, a request from a calling application executed by the IHS to access the object stored in the off-host memory;

collecting, via another IHS, new authentication data from a user by prompting the user;

generating, via the other IHS, a new system ID without prompting the user;

determining, by the external off-host authentication processing system, that the new authentication data matches the authentication data stored in the object but that the new system ID does not match the system ID stored in the object; and

denying the request.

9. An external off-host authentication processing system, comprising:

an off-host processor; and

a non-transitory, off-host memory coupled to the off-host processor, the off-host memory having program instructions stored thereon that, upon execution by the off-host processor, cause the external off-host authentication processing system to:

receive, from an Information Handling System (IHS) coupled to the external off-host authentication processing system, raw data, authentication data, and a system ID, wherein the authentication data is collected via the IHS by prompting a user, and wherein the system ID is silently generated via the IHS without prompting the user;

store the authentication data, the system ID, and the raw data as part of an object in the off-host memory;

receive a request from a calling application executed by the IHS to access the object stored in the off-host memory, wherein the request includes new authentication data obtained by the IHS from a user by prompting the user and a new system ID silently obtained by the IHS without prompting the user;

determine that the new authentication data and new system ID match the authentication data and system ID stored in the object; and

retrieve the object from the off-host memory.

10. The external off-host authentication processing system of claim 9 , wherein the raw data includes an encryption key or fingerprint template.

11. The external off-host authentication processing system of claim 9 , wherein the system ID includes an identification of a hardware or software component of the IHS.

12. The external off-host authentication processing system of claim 9 , wherein the IHS comprises an embedded controller coupled to a processor, wherein the external off-host authentication processing system is coupled to the embedded controller, and wherein the external off-host authentication processing system provides a hardware environment segregated from the processor.

13. The external off-host authentication processing system of claim 9 , wherein the program instructions, upon execution by the off-host processor, further cause the external off-host authentication processing system to:

receive a request from a calling application executed by another IHS to access the object stored in the off-host memory, wherein the request includes new authentication data obtained by the other IHS from a user by prompting the user and a new system ID obtained by the other IHS without prompting the user;

determine that the new authentication data matches the authentication data stored in the object but that the new system ID does not match the system ID stored in the object; and

deny the request.

14. A non-transitory, off-host memory having program instructions stored thereon that, upon execution by an off-host processor of an external off-host authentication processing system, further cause the external off-host authentication processing system to:

receive, from an Information Handling System (IHS) coupled to the external off-host authentication processing system, raw data, authentication data, and a system ID, wherein the authentication data is collected via the IHS by prompting a user, and wherein the system ID is silently generated via the IHS without prompting the user;

store the authentication data, the system ID, and the raw data as part of an object in the off-host memory;

receive a request from a calling application executed by the IHS to access the object stored in the off-host memory, wherein the request includes new authentication data obtained by the IHS from a user by prompting the user and a new system ID silently obtained by the IHS without prompting the user;

determine that the new authentication data and new system ID match the authentication data and system ID stored in the object; and

retrieve the object from the off-host memory.

15. The off-host memory of claim 14 , wherein the system ID includes an identification of a hardware component or a software component installed in the IHS.

16. The external off-host authentication processing system of claim 14 , wherein the IHS comprises an embedded controller coupled to a processor, wherein the external off-host authentication processing system is coupled to the embedded controller, and wherein the external off-host authentication processing system provides a hardware environment segregated from the processor.

17. The off-host memory of claim 14 , wherein the program instructions, upon execution by the off-host processor, further cause the external off-host authentication processing system to:

receive a request from a calling application executed by another IHS to access the object stored in the off-host memory, wherein the request includes new authentication data obtained by the other IHS from a user by prompting the user and a new system ID obtained by the other IHS without prompting the user;

determine that the new authentication data matches the authentication data stored in the object but that the new system ID does not match the system ID stored in the object; and

deny the request.