Methods for authenticating a user
The method uses an identity broker and service provider to generate a verifiable identity token, addressing vulnerabilities in SSO authentication by ensuring secure, efficient, and regulatory-compliant user authentication across services.
Patent Information
- Application Number
- DE102023002170
- Authority / Receiving Office
- DE · DE
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-30
- Publication Date
- 2024-12-05
AI Technical Summary
Existing user authentication methods, such as single sign-on (SSO) authentication, rely heavily on intermediary services, making them vulnerable to compromise and unsuitable for sensitive or regulated services, and require repeated physical identity document verification, which is cumbersome.
A method involving an identity broker and a trusted identity service provider, where users electronically record personal identifiers and identity documents, generating a unique identity token verifiable across services, reducing the need for repeated physical verification and intermediary trust.
Ensures secure, efficient authentication independent of intermediary trust, allowing seamless access to sensitive services while complying with regulatory requirements, and reducing the need for multiple physical identity checks.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] The invention relates to a method for authenticating a user according to the preamble of claim 1.
[0002] Known methods for identifying a user who wishes to use a service offered by a service provider, for example, to process a payment, provide information, and / or publish information, are based on the presentation of a physical identity document, such as a passport issued by national authorities. During such identification or authentication, actual characteristics of the user that individually and uniquely identify that user (hereinafter referred to as personal characteristics) are compared with the information provided in the physical identity document. For example, actual physical biometric characteristics (fingerprint, iris structure, retinal structure, and / or two- or three-dimensional facial features) are compared with the description provided by the physical identity document.The physical identity document may include such a description in machine-readable form. However, it is also possible for the physical identity document to be associated with a description of personal characteristics stored elsewhere (e.g., on a server or in a blockchain).
[0003] The process of such identification is complex and typically requires technical tools, such as a camera, a fingerprint reader, or a Light Detection and Ranging (LiDAR) sensor. Therefore, for a user who wishes to use services from multiple service providers, there is a need for an identification method that avoids or reduces the effort of repeatedly recording personal identifiers and comparing them with a physical identity document assigned to them.
[0004] Single sign-on (SSO) authentication methods are also known, with which a user registers and authenticates with a single intermediary service. SSO authentication requires user identification. According to these SSO authentication methods, third-party providers of additional services delegate authentication to the intermediary service using a request token, which may include user information, including personal identifiers.
[0005] Based on this information, the intermediary service authenticates the user the first time they use a third-party service, for example, by requesting a username and password and / or a one-time password (OTP). If authentication is successful, the intermediary service confirms the user's authenticity, for example, by returning the request token cryptographically signed by the intermediary service.
[0006] If the same user subsequently (repeatedly) claims the same or a different third-party provider, the intermediary service simply confirms the authenticity of the previously verified user. This eliminates the need for repeated authentication processes.
[0007] However, such SSO authentication methods have the disadvantage of relying on a high level of trust in the intermediary service. If the intermediary service is compromised (for example, through a cryptographic attack on its private key used to sign request tokens), every third-party provider that relies on the intermediary service to correctly verify the user's authenticity is also compromised.
[0008] Therefore, such SSO authentication procedures are not applicable for services that require special protection or services that are subject to special regulation regarding the identification of a user (for example, to prevent money laundering).
[0009] Therefore, there is a need for a method for authenticating a user that is independent of the trust position of an intermediary service, in particular an identity intermediary, and that avoids or reduces the multiple comparison of a physical identity document with personal identifiers of a user.
[0010] The invention is based on the object of providing an improved method for authenticating a user to use a service of at least one third-party provider.
[0011] The object is achieved according to the invention by a method having the features of claim 1.
[0012] Advantageous embodiments of the invention are the subject of the subclaims.
[0013] In a method for authenticating a user who wishes to use a third-party service, the user registers with an identity intermediary. Both the identity intermediary and the third-party provider are provided as computer-implemented methods.
[0014] The user electronically captures a physical identity document and provides it to the identity intermediary as an electronic identity document. A physical identity document is defined here and below as a physically unique document that can be assigned to a single user based on the information it contains. For example, a physical identity document can be issued as an ID card, driver's license, or passport by a national government authority. Physical identity documents can also be issued by other, non-governmental organizations, for example, as an electronic health card or a work ID card.
[0015] The physical identity document preferably contains electronically readable information identifying the assigned user, for example, an electronically stored biometric passport photograph, a data set with at least one fingerprint, or similar. This information and / or information attributable to the user via a storage location independent of the physical identity document are transferred to the electronic identity document.
[0016] The user provides the identity provider with at least one personal identifier configured for comparison with the electronic identity document, preferably a biometric identifier (e.g., a two-dimensional camera image of facial features, a three-dimensional LiDAR image of facial features, and / or a fingerprint). Preferably, such personal identifiers are captured and provided that can be used to authenticate the user in accordance with the business, legal, or regulatory requirements that are relevant for using the third-party provider's service.
[0017] Preferably, the personal identifiers are recorded automatically using a user device assigned to the user (smartphone, tablet, computer with webcam or similar).
[0018] The identity broker provides the electronic identity document and at least one personal identifier to an identity service provider. The identity service provider is designed as a computer-implemented process of a particularly trustworthy service provider, preferably a government or government-supervised service provider.
[0019] The identity service provider checks that the at least one personal identifier matches the information in the electronic identity document. If the match is found, the identity service provider creates an identity token whose validity is publicly verifiable and which is assigned to the user. For example, the identity token can be signed with a private key of the identity service provider and stored in a blockchain or other distributed ledger technology (DLT). The identity service provider provides the identity token to the identity broker.
[0020] The identity broker registers the user with at least one third-party provider using a single sign-on (SSO) authentication common to all third-party providers and provides the identity token.
[0021] The at least one third party provider verifies the identity of the user by checking the validity of the identity token with the identity service provider and / or the identity intermediary.
[0022] One advantage of the procedure is that it relieves the user of the burden of repeatedly recording personal identifiers and / or repeatedly comparing personal identifiers with a physical identity document, while simultaneously achieving authentication trustworthiness independent of the identity intermediary. This makes the procedure also applicable to third-party providers of particularly sensitive or government-regulated services.
[0023] It is possible, but not required, that when using the service of a third-party provider and / or the identity intermediary for the first time, a user is already registered with the identity service provider, i.e. has stored at least one personal identifier with reference to a physical and / or electronic identity document.
[0024] Furthermore, it is not necessary for the identity service provider to assign a user only a single physical identity document. For example, a driver's license can be captured for an initial user assignment and assigned to the user profile as an electronic identity document. Based on this assignment, the identity service provider can process authentication requests for third-party services that require comparatively low levels of protection.
[0025] If a service with a higher level of security subsequently requests identity verification, another physical identity document (e.g., an ID card) can be captured as an electronic identity document and provided to the identity service provider. The identity service provider then assigns this additional electronic identity document to the already registered user. The additional electronic identity document can be captured in addition to or instead of a previously captured and assigned identity document.
[0026] Furthermore, if the identity service provider has added or replaced physical identity documents of a different type (identity card instead of driving license), or if other information recorded in the associated user profile has changed, involved parties, in particular third parties and / or the identity intermediary, may be informed of such a change.
[0027] For example, third parties can register to receive notifications about a user being included in a list of so-called Politically Exposed Persons (PEPs).
[0028] This embodiment is particularly advantageous for the implementation of anti-money laundering measures and for the control of PEPs, since such measures or such a group of persons can change dynamically. The proposed embodiment therefore enables a particularly prompt implementation of such controls in real time or with minimal delay, thus contributing to the effective implementation of anti-money laundering and anti-terrorism measures.
[0029] In a further embodiment, the identity broker records the date of birth and / or current age of a user and creates an anonymized identity token that includes this date of birth and / or current age, but in which other personal information, in particular information about a last name, a first name, and / or an address, has been removed or replaced with pseudonyms. Based on such an anonymized or pseudonymized identity token, a third-party provider can perform an age check for the user in an anonymized form (for example, without disclosing the user's identity). This enables particularly data-efficient business requirements.
[0030] In one embodiment of the method, the user is forwarded by the identity broker or a third-party provider to the identity service provider for registration. If the user uses services from a third-party provider and is not yet registered with the identity service provider, the forwarding can be done via the information broker. The identity broker captures the physical identity document and at least one personal identifier in the manner described above and forwards the data obtained from it to the identity service provider.
[0031] In a further development of this embodiment, it is also possible for the identity intermediary to capture and provide special information and / or personal characteristics according to the requirements of the identity service provider, preferably using the user device.
[0032] An advantage of this embodiment is that additional registration and, consequently, additional collection of user data and personal identifiers by the identity service provider can be avoided.
[0033] Embodiments of the invention are explained in more detail below with reference to drawings.
[0034] Showing: Fig. 1 schematically shows a system architecture for the distribution and updating of identity tokens, Fig. 2 schematically shows a flow chart for the distribution and updating of identity tokens and Fig. 3 schematically shows an extended system architecture for the distribution and updating of identity tokens.
[0035] Corresponding parts are provided with the same reference numerals in all figures.
[0036] Fig. Figure 1 shows a schematic overview of a system architecture for the distribution and updating of identity tokens 4. One embodiment of a method for creating, distributing and updating identity tokens 4 comprises eight steps S1 to S8, which are described in Fig. 1 partially shown, but only following based on Fig. 2 will be explained in more detail.
[0037] Identity tokens 4 are generated by an identity service provider 3 and provided to an identity broker 1. Each identity token 4 is unique and assigned to a single (in Fig. 1 not shown). The user presents himself to the identity service provider 3 by means of a user device 2, which can usually be designed as a mobile device (smartphone, tablet, notebook), but in principle also as a personal computer (PC) or as any Internet-connectable Internet of Things (IoT) device. The creation and provision of identity tokens 4 is described below using Fig. 2 is explained in more detail.
[0038] To record the physical parameters, the user device 2 has Fig. 1 has sensors not shown in detail, for example, a camera and / or a biometric sensor (for example, a finger or palm sensor). Furthermore, the user device 2 has input means not shown in detail for reading data from the identity document, for example, a smart card reader or a near field communication (NFC) interface.
[0039] Preferably, at least one sensor is configured as a Light Detection and Ranging (LiDAR) sensor for detecting three-dimensional, at least partially reflective surfaces. A LiDAR sensor can, for example, capture the user's face in its three-dimensional structure. This can prevent the feigning of a false physical identity by using photos or videos of a stranger.
[0040] The identity broker 1 is configured to log in to a plurality of third-party providers 6 or to log in to use services for a user using a single single sign-on (SSO) authentication 7 (for example, using a single combination of a user name and an associated password).
[0041] Third-party providers 6 may, for example, be merchants, banks, financial institutions, or account information services. In particular, third-party providers 6 may also offer services that require special protection (with regard to user authentication), such as payment transactions or confidential information.
[0042] According to the invention, the identity broker 1 transmits the identity token 4, which it has obtained for the respective user from the identity service provider 3, together with the SSO authentication. A third-party provider 6 can therefore trust the registration or login of a user, even when using SSO authentication 7, to the same extent that it would trust the verification of an identity based on a comparison of a physical identity document with the user's physical appearance by the identity service provider 3.
[0043] To detect and prevent identity theft, the system architecture further provides a validation and risk analysis procedure 8 which, at the request of the identity service provider 3, checks the conformity of an identity claimed by a user (according to a presented physical identity document) with his actual identity (according to biometric and other parameters captured by the user device 2) in a manner explained in more detail below.
[0044] The data connections between the user device 2 and the identity broker 1, between the identity broker 1 and the identity service provider 3 and between the identity service provider 3 and the validation and risk analysis process 8 are preferably designed as cloud data connections 9, i.e. at least one end of this data connection is connected to a distributed cloud service.
[0045] Fig. Figure 2 shows a schematic flowchart for the distribution and updating of identity tokens 4.
[0046] In a first step S1, a user registers with an identity broker 1 to create an identity token 4 (i.e., to obtain a digital identity). For example, the identity broker 1 can be accessed via a computer-implemented method on a user device 2, for example via an app on a mobile device (smartphone, tablet, or notebook).
[0047] In a subsequent second step (S2), the user's physical identity is verified by capturing a physical (i.e., unique) identity document that is uniquely assigned to the user. For example, the identity document can be an identity card, driver's license, or passport issued by a government authority. However, identity documents issued by other institutions (e.g., banks or health insurance companies) are also possible, provided they meet the security requirements arising from the intended use of the digital identity.
[0048] To determine physical identity, the user's physical parameters, such as, and preferably, biometric parameters (face, fingerprint, iris and / or retinal structure), are recorded. Corresponding parameter values are read from the identity document and compared with the physically recorded parameters.
[0049] To capture the physical parameters, the user device 2 has sensors, for example, a camera and / or a biometric sensor (for example, a finger or palm sensor). Furthermore, the user device 2 has input means for reading data from the identity document, for example, a smart card reader or a near field communication (NFC) interface.
[0050] Preferably, at least one sensor is configured as a Light Detection and Ranging (LiDAR) sensor for detecting three-dimensional, at least partially reflective surfaces. A LiDAR sensor can, for example, capture the user's face in its three-dimensional structure. This can prevent the feigning of a false physical identity by using photos or videos of a stranger.
[0051] The user's physical parameters are recorded to the extent, accuracy and reliability required for identification in accordance with applicable specifications, standards, regulations or legal requirements.
[0052] If the physically recorded parameters match the corresponding parameter values read from the identity document, the identity document is recognized as assigned to the user. Otherwise, the user's request to assign the identity document is rejected.
[0053] If the identity document is successfully assigned to the user, all or some of the data readable from the identity document, in particular the authorizations contained therein, are read and sent to an identity service provider 3 in a subsequent third step S3. Such data can be taken from the following exemplary and non-exhaustive list: - Name first Name - a string or number associated with the physical identity document (e.g. an ID number) - Place of birth - Place of issue of the identity document - Validity period of the identity document - Issuer of the identity document.
[0054] Furthermore, in the third step S3, the physically recorded parameters (e.g., a photo of the face, a LiDAR scan of the face and / or a fingerprint) are transmitted to the identity service provider 3.
[0055] In addition, data may be transmitted that identify the identity intermediary 1 or the geographical location where the identity verification was carried out according to the first step S1.
[0056] Furthermore, the identity intermediary 1 can provide additional data, for example, data characterizing the user's purchasing behavior or the use of online services. In particular, the identity intermediary 1 can provide data relevant for a risk assessment of the user, for example, regarding the risk of payment default. Such data can be taken from the following exemplary and non-exhaustive list: - user expenditure averaged over a predetermined period - averaged user logins to an online service over a predetermined period - average usage times for an online service over a predetermined period - cryptographic strength of a password used by the user - Data on bank details and / or payment processing.
[0057] In a subsequent fourth step S4, the identity service provider 3 issues an identity token 4 that is globally unique (i.e., across all users) and is assigned to the user device 2 (and / or another Internet of Things (IoT) hardware device connectable via the Internet) and to the identity broker 1. The identity token 4 can be assigned to the user device 2 and the identity broker 1, for example, using a decentralized ledger (Distributed Ledger Technology, DLT), for example, using a blockchain.
[0058] The generated identity token 4 is transmitted to the identity broker 1. The identity broker 1 can check the validity of the identity token 4, for example, by querying a DLT, and / or store it.
[0059] In a subsequent fifth step S5, the generated identity token 4 is assigned to a user profile at the identity broker 1. For a comparison and / or verification of the status and validity of the user information stored with the identity service provider 3, data is exchanged between the identity broker 1 and the identity service provider 3 via a suitable data interface 5.
[0060] Such data interfaces 5 may, for example, be provided as cloud or web access, as an application programming interface (API) or as a software development kit (SDK), via Bluetooth, Wide Local Area Network (WLAN), a satellite connection or another wireless communication interface.
[0061] In particular, the data interface 5 is designed for high availability, so that changes concerning a user at the identity service provider 3, for example a revocation of an identity document, can be recorded directly by the identity intermediary 1.
[0062] This allows Identity Intermediary 1 to verify the collected and stored user information at any time using a standard verification procedure that typically meets nationally regulated security requirements. Such standard verification procedures may, for example, within the national regulatory framework of the Federal Republic of Germany, include a verification in accordance with the requirements of the Federal Financial Supervisory Authority (BaFin), in particular a verification in accordance with the requirements of the Money Laundering Act (GWG).
[0063] The identity intermediary 1 has the option of accessing the electronic services of various third-party providers 6 via a single single sign-on (SSO) authentication 7. The third-party providers 6 can, for example, act as additional intermediaries, merchants, banks, or financial institutions.
[0064] When using their electronic services, the identity intermediary 1 transmits the identity token 4, which replaces the physical identity of the user in a manner that satisfies the security requirements (i.e., the presentation of a physical identity document and its comparison with the physical, for example, biometric, characteristics of the user), to a third-party provider 6 in a sixth step S6. The transferred identity token 4 can be verified by the identity service provider 3 in real time or with a delay that is sufficiently short for the respective intended use, for example by querying the blockchain in which the assignment of the identity token 4 is recorded.
[0065] This means that a user does not have to undergo verification of his physical identity multiple times (to each individual third-party provider 6), but only once to the identity intermediary 1. At the same time, this ensures that at the time of registration or logging in of a user with a third-party provider 6, his physical identity has been verified in accordance with the applicable security requirements (for example, in accordance with a verification that satisfies the Money Laundering Act).
[0066] In an optional seventh step S7, the data stored with the identity service provider 3 are updated, for example by adding an additional identity (corresponding to an additional physical identity document) or by changing an existing identity (for example in a part of a name).
[0067] With such an update or addition, a re-registration of the user with the identity provider 1 according to the first to third steps S1 to S3 is not required. Re-registration with any of the previously used third-party providers 6 is also not necessary. Instead, the new or changed user data is stored with the identity service provider 3 and assigned to the user in the manner already described (for example, using blockchain or another DLT). In particular, the assignment can be publicly visible and verifiable (i.e., also by any third-party provider 6).
[0068] In an eighth step S8 (following the sixth step S6 or the seventh step S7), the identity token 4 is verified, for example, by one of the third-party providers 6. The validity of the identity token 4 is verified in real time or with a sufficiently short delay for the respective intended use, and the risk of identity fraud is determined by the identity service provider 3. Depending on the determined risk, a further verification of the user's physical identity is initiated.
[0069] Validation and risk analysis procedure 8 carries out identity validation and a determination of the risk of identity fraud, for example, based on parameters (related to the respective user) that may be taken from the following non-exhaustive list: - chronological history of past transactions - Volume of past transactions (e.g. monetary value of purchased goods or cash payments received) - Frequency of past transactions - geographical location or area where the user is located according to the request for verification of the identity token 4, - politically exposed persons potentially affected by the validation of identity token 4 - Activities related to the user's account (for example, reports of a lost or stolen password) - Frequency of booking - risk metrics or indicators provided by third parties, such as one or more third-party providers 6, to capture potential malicious behavior.
[0070] An advantage of the proposed procedure is that use cases that require a particularly high level of authentication reliability, for example use cases associated with payment transactions with a required level of reliability defined by national or industry-specific standards such as BaFin or GWG conformity, can be implemented with a single sign-on procedure that only has to meet comparatively low requirements for the reliability of authentication.
[0071] Normally, access to services provided by various banks, financial institutions, or information services, such as account information services, is not possible via SSO authentication 7. The proposed system architecture enables identity intermediaries 1 to log in using SSO authentication 7 even for the use of such particularly sensitive services.
[0072] A user is no longer required to physically verify his identity through a plurality of services, as the interchangeable identity token 4 can be distributed by one (preferably a single) identity intermediary 1 and validated by request to the identity service provider 3.
[0073] Third-party providers 6, such as merchants, are enabled to receive validated identity tokens 4 without requiring the visibility of personal data. This makes it easier for third-party providers 6 to comply with data protection regulations, for example, the General Data Protection Regulation in the Federal Republic of Germany.
[0074] The proposed method thus enables the issuance of identity tokens 4 according to an identity claimed with a physical identity document based on data captured from the actual user (e.g., with cameras, LiDAR sensors, and / or other biometric sensors). Such identity tokens 4 can be distributed and updated to third-party providers 6 that use SSO authentication 7 of the identity broker 1. This does not require any interaction from the identity broker 1 and / or the third-party providers 6.
[0075] The validation and risk analysis procedure 8 checks the status, in particular the validity status, of identity tokens 4. This can prevent misuse, especially identity theft.
[0076] Each time an identity token 4 is requested, the risk of misuse is checked using the validation and risk analysis procedure 8. The check is performed indirectly (at the request of the identity broker 1) by the identity service provider 3 or directly by the identity broker 1. The following data, listed only as examples and not exhaustive, may be included in the check and risk assessment: - Timeline of previous transactions - Volume of previous transactions - Frequency of previous transactions - geographical location - the risk that politically exposed persons are affected by a transaction - the activities associated with the user account, in particular reports of loss or theft of passwords - Frequency of booking - Risk metrics / assessment metrics provided by third parties to evaluate malicious activities - Activities and / or publications on social media.
[0077] In one embodiment of the method, a user-related trust value is determined based on such a risk assessment, for example, between 0 and 100. If the trust value is below a predetermined threshold (for example, 20 or less), the user is requested by the identity intermediary 1 or the identity service provider 3 when logging in with a third-party provider 6 to undergo another physical identity verification (i.e., to present the physical identity document again and to record their actual data, for example, biometric data, required for comparison). This re-verifies the match between the actual identity and the claimed identity.
[0078] This embodiment is advantageous when credit is claimed by users for whom late payment and / or default has been registered and who can thus be legally identified and forced to pay.
[0079] Fig. Figure 3 shows schematically a system architecture for an embodiment of the method in which, deviating from the Fig. The system architecture shown in Figure 1 provides for direct communication between the identity service provider 3 and the third-party providers 6.
[0080] According to this embodiment, in an additional ninth step S9, a third-party provider 6 sends an identity token 4 (which was transmitted to it by the identity intermediary 1 when a user registered) together with an identifier of the identity intermediary 1 (for example, a character string) with a query to the identity service provider 3.
[0081] In addition, this query can also send further data about the user, such as an email address and / or other personal data. Hardware identifiers attributable to the user can also be transmitted, such as an International Mobile Subscriber Identity (IMSI) number assigned to the user from a Subscriber Identity Module (SIM), a Media Access Control (MAC) address of a network adapter on user device 2 or other user hardware, a Vehicle Identification Number (VIN) of a user vehicle, or another hardware identifier unique to a piece of hardware.
[0082] When a user registers for the first time with a third-party provider 6 via the identity intermediary 1, such data is collected and / or (insofar as it has already been collected and stored with the identity intermediary 1) exchanged and subsequently transmitted by the identity intermediary 1 to the identity service provider 3 and assigned to the data stored for the respective user and the respective third-party provider 6.
[0083] If a third-party provider 6 requires updated data about a user, it sends the user's identity token 4 with an identifier to the identity service provider 3. Optionally, additional user data is sent to the identity service provider 3 in the form already described.
[0084] The identity service provider 3 can, in a similar manner, assign and store one or more data records for a user, for example, two or more addresses, telephone numbers, or identifying data obtained from the user device 2 or other hardware not shown in detail here, such as an International Mobile Subscriber Identity (IMSI) number of a Subscriber Identity Module (SIM), a Media Access Control (MAC) address of a network adapter, a Vehicle Identification Number (VIN) of a vehicle, or another identifier uniquely related to a hardware. A user can be assigned by comparing all such data records with the identifier provided by the third-party provider 6.
[0085] In addition, the third-party provider 6 can arrange for the identity service provider 3 to send a request for a one-time password (OTP) and / or a one-time identifier and / or passphrase in the form of a personal identification number (PIN) (for example, a request for the user's date of birth) to the user. Based on the user's response to this request, the identity service provider 3 can verify the match between the user's actual identity and the claimed identity at the time of the request (i.e., immediately before the transaction requested by the user from the respective third-party provider 6).
[0086] An OTP can also be requested in the form of a biometric feature, for example, a biometric feature known as a FaceID, derived from a photograph of the user's face. In this case, a backend of the third-party provider 6 can transmit a data set to the identity service provider 3 containing the respective actually recorded biometric feature, so that the identity service provider 3 can compare this actually recorded biometric feature with a biometric feature stored with it.
[0087] After verifying the identity token 4 and comparing it with the identifier, the identity service provider 3 transmits updated information and details about the user to the third-party provider 6, which the third-party provider 6 can use to verify that the actual identity matches the claimed identity, without the need for physical identity verification or additional security checks.
[0088] If an identity token 4 loses its validity, for example, as a result of a risk assessment by the validation and risk analysis process 8, which detects exceptionally high transaction volumes or frequencies or contact with politically exposed persons, the user is redirected to the identity intermediary 1 or the identity service provider 3 to repeat and / or complete their physical identification. In doing so, the third-party provider 6 can initiate or support the transmission of captured (e.g., biometric) and / or physically verified data.
[0089] Under the regulations applicable in the Federal Republic of Germany, for example, regarding money laundering, it is necessary to collect a PLN, a one-time verification (one-time password or one-time PIN), and / or a biometric feature to confirm the user's identity. For this purpose, the third-party provider 6 can directly request the user to enter such confirming information. The request can be transmitted directly or indirectly, depending on the transmission path of the identity token 4 via the identity service provider 3 and based on the data collected by the third-party provider.
[0090] For example, identity confirmation can be performed using any data stored by identity service provider 3 (e.g., by providing the date of birth, place of birth, an ID or tax identification number, or a similar identifier). In addition, identity service provider 3 can send additional randomly generated PINs to third-party provider 6 via various communication channels (short message (SMS), a messenger service, a proprietary digital environment of third-party provider 6, a QR code, or similar) via identity intermediary 1.
[0091] If the user confirms such a request (i.e. enters or provides the correct answer to the request), this answer is transmitted directly to the identity service provider 3 or via the identity intermediary 1 to the identity service provider 3, depending on the communication path of the identity token 4.
[0092] Known methods of user identification require the use of a separate, dedicated application, for example an app installed on a smartphone such as the TruelD app from the provider WeblD, which runs as a wallet app in a specially protected runtime environment.
[0093] Using such an application, the user can enter a code (or a similar response to a request for identity confirmation, such as a date and / or place of birth).
[0094] Advantageously, the proposed embodiment enables a third-party provider 6 or an identity provider 1 to perform user identification independently of such a separate application within their respective own infrastructure or within their own information technology (IT) ecosystem. This facilitates user identification, in particular reducing the number of user interactions required for identification. Furthermore, the robustness of user identification is improved, as it is enabled independently of the availability of an additional application. List of reference symbols 1 Identity intermediary (ID merchant) 2 user devices 3 Identity service providers (ID providers) 4 identity tokens 5 Data interface 6 third-party providers 7 Single Sign-on (SSO) Authentication 8 Validation and risk analysis procedures 9 Cloud data connection S1 to S9 first to ninth step
Claims
[1] Method for authenticating a user to use a service provided by at least one third party provider (6), characterized by , that - the user registers with an identity provider (1), - the user electronically records a physical identity document and provides it to the identity intermediary (1) as an electronic identity document, - the user provides the identity intermediary (1) with at least one personal identifier, preferably a biometric identifier, set up for comparison with the electronic identity document, - the identity intermediary (1) provides the electronic identity document and the at least one personal identifier to an identity service provider (3), - the identity service provider (3) checks the conformity of the at least one personal identifier with the electronic identity document and, if there is a match, creates a publicly verifiable identity token (4), assigns it to the user and makes it available to the identity intermediary (1), - the identity intermediary (1) registers the user with at least one third-party provider (6) using a single sign-on (SSO) authentication (7) common to all third-party providers (6) and thereby provides the identity token (4), - the at least one third-party provider (6) verifies the identity of the user by checking the validity of the identity token (4) with the identity service provider (3) and / or with the identity intermediary (1), wherein the identity intermediary (1), the identity service provider (3) and the third-party provider (6) are provided as computer-implemented methods. [2] Method according to claim 1, characterized bythat the identity intermediary (1) and / or a third party provider (6) forwards the user to the identity service provider (3) for registration via the identity intermediary (1). [3] Method according to one of the preceding claims, characterized by that the identity service provider (3), when checking the conformity of the personal identifiers with the electronic identity document, determines by means of a validation and risk analysis procedure (8) whether updated and / or additional personal identifiers of the user are to be recorded. [4] Method according to one of the preceding claims, characterized by that at least one third-party provider (6) verifies the identity of the user by transmitting the user's identity token (4) and an identifier assigned to the identity intermediary (1) to the identity service provider (3). [5] Method according to one of the preceding claims, characterized bythat at least one personal identification number is designed as a feature of a vehicle assigned to the user.
Citation Information
Patent Citations
procedure for issuing a virtual version of a document
DE102016221699A1
Computer-implemented systems for distributed authorization and federated privacy exchange
US20210218742A1
Cited By
Method, user device, authentication program and transaction system with data object for authenticating the user device during transactions
DE102025104083A1
