Biometric SSO Authentication with Encrypted Template Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Single Sign-On (SSO) authentication systems expose users' biometric information to identity providers, leading to privacy breaches and lack of user control over biometric data usage, as biometrics are often decrypted for authentication, making them susceptible to attacks.
Innovation Solution
A method and system using homomorphic hash-based message authentication code (HMAC) encrypt biometric data with Fully Homomorphic Encryption (FHE), allowing authentication without revealing biometric information to the identity provider, leveraging homomorphic operations for secure biometric template comparison and trusted decryption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If biometric information is stored and processed in conventional SSO systems, then authentication functionality is achieved, but user privacy and security are compromised due to exposure of biometric data
Solution Approach 1:
The patent introduces Fully Homomorphic Encryption (FHE) as an intermediary layer between biometric data and processing systems. Biometric templates are encrypted using FHE before storage, and authentication operations are performed on encrypted data without decryption. This mediator prevents direct exposure of biometric information while enabling authentication functionality.
Solution Approach 2:
The patent transforms biometric data from plaintext to encrypted form using FHE, changing the parameter state of the data. This parameter change allows the system to process and compare biometric templates while maintaining them in encrypted form, thus achieving authentication without exposing the actual biometric information.
2Measurement precision
If biometric data is decrypted for authentication processing, then authentication accuracy is improved, but privacy risks and unauthorized access potential increase
Solution Approach 1:
FHE serves as an intermediary that enables accurate biometric matching without requiring decryption. The encryption scheme allows comparison operations to be performed on encrypted templates, maintaining authentication accuracy while preventing privacy breaches that would occur with traditional decryption-based approaches.
Solution Approach 2:
The patent applies encryption to biometric templates in advance (during enrollment) before any authentication operations. This preliminary action ensures that all subsequent processing, including matching and comparison, occurs on encrypted data, thereby maintaining accuracy while eliminating the need for decryption during authentication.
3Reliability
If traditional encryption schemes are used for biometric storage, then data protection is achieved, but decryption is still required for authentication which exposes biometric information
Solution Approach 1:
The patent transitions from traditional symmetric encryption (which requires decryption) to Fully Homomorphic Encryption (which enables computation on encrypted data). This parameter change in the encryption approach allows authentication operations to be performed on encrypted biometric templates without decryption, maintaining data protection while enabling direct processing of encrypted data.
Data Source
AI summary
The present disclosure provides biometric single sign-on authentication via homomorphic hash based message authentication code (HMAC). Conventional methods fails to provide authentication without revealing biometric data. In the present disclosure, when the user initiates a service request, a service provider redirects to an identify provider for authentication. Further, user captures and encrypts his/her biometrics using homomorphic HMAC, creating ciphertext. User submits his/her encrypted biometrics to the identity provider for authentication. The identity provider uses template matching algorithms to compare the user submitted encrypted biometrics (fingerprint, iris) with stored templates. The identity provider then transmits authentication result and the corresponding proof of authentication. Further, the service provider re-computes the authentication tag based on the received decrypted authentication result and the secret nonce. Finally, the service provider provides the requested service to the client machine, only if the re-computed authentication tag matches with the associated decrypted proof.