An authentication method and electronic device
By establishing application relationships within electronic devices and using group identifiers and access keys to enable seamless login across applications, the limitations and security issues of single sign-on are resolved, improving user experience and enterprise management efficiency.
Patent Information
- Application Number
- CN202611160818.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-31
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, single sign-on has limitations and low security, especially in multi-application login scenarios, resulting in poor user experience, insufficient account security, and high difficulty for enterprises to manage in a unified manner.
The application relationship between the first application and the authenticated second application is determined by electronic devices. Access credentials are issued in response to the conditions that are met. Local identity verification is performed using a pass key interface. Seamless login across applications is achieved using group identifiers. Access credentials are synchronized through trusted connections to ensure security and flexibility.
It enables seamless login across applications, improves user experience and security, reduces the operation and maintenance costs of enterprises in multi-software matrix scenarios, and enhances the availability and security of identity authentication.
Smart Images

Figure CN123122837A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of identity authentication technology, and in particular to an authentication method and electronic device. Background Technology
[0002] In related technologies, Single Sign-On (SSO) is a popular enterprise business integration solution. It allows users to access other applications from the same user in multiple mutually trusted systems with only one login, without repeatedly entering credentials. For example, during the authentication process in application A, user 1 provides their username and password to the Identity Provider (IdP). After successful verification by the IdP, a token is issued. When application B runs, it can obtain its own access token through token exchange or browser redirection. However, in obtaining its own token, the IdP needs to verify whether the token carried by application B belongs to user 1. Only the same user can achieve authentication, thus limiting the authentication process. Summary of the Invention
[0003] This application provides an authentication method and an electronic device.
[0004] The technical solution of this application embodiment is implemented as follows: This application provides an authentication method, the method including: In response to the authentication request of the first application, the application relationship with the already authenticated second application is determined based on the authentication information carried in the authentication request; In response to the application relationship meeting the target conditions, an access credential indicating successful authentication is issued to the first application, enabling the first application to access the required resources based on the access credential.
[0005] This application provides an electronic device, including: Memory, used to store one or more computer programs; The processor is used to execute computer programs stored in memory to: run a first application and generate a corresponding authentication request based on the acquired authentication information; receive access credentials issued after successful authentication through the first application and access the required resources based on the access credentials; or, There is a communication relationship between the electronic device and the device running the first application; An authentication module executes a computer program stored in memory to: receive an authentication request and, based on the authentication information carried in the authentication request, determine the application relationship with a second application that has already been authenticated; and, in response to the application relationship meeting the target conditions, issue an access credential indicating successful authentication to the electronic device running the first application. Attached Figure Description
[0006] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein: Figure 1 A flowchart illustrating an authentication method provided in an embodiment of this application; Figure 2 A flowchart illustrating an exemplary authentication method provided in this application embodiment. Figure 1 ; Figure 3 This application provides an exemplary flowchart for determining whether target conditions are met. Figure 1 ; Figure 4 This application provides an exemplary flowchart for determining whether target conditions are met. Figure 2 ; Figure 5 A flowchart illustrating an exemplary authentication method provided in this application embodiment. Figure 2 ; Figure 6 A flowchart illustrating an exemplary authentication method provided in this application embodiment. Figure 3 ; Figure 7 A flowchart illustrating an exemplary authentication method provided in this application embodiment. Figure 4 ; Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0007] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It is understood that the specific embodiments described herein are merely for explaining the relevant application and not for limiting the application. Furthermore, it should be noted that, for ease of description, only the parts relevant to the application are shown in the accompanying drawings.
[0008] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.
[0009] Unless otherwise defined, all technical and scientific terms used in this application have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used in this application is for descriptive purposes only and is not intended to be limiting.
[0010] For logins across multiple applications, related technologies typically combine traditional single-application login with multiple-application repeated logins. In this approach, each application independently calls the login interface. After a user logs in through application A, application B still requires them to re-enter their account password, verification code, or secondary verification information, resulting in a poor user experience. Furthermore, account security relies on multiple entry points, leading to a wider exposure surface and making unified enterprise management difficult. To address this issue of repeated logins, related technologies use single sign-on (SSO), which leverages OpenID Connect (OIDC) / Open Authorization (OAuth) token exchanges or SSO redirects to enable login between multiple applications. For example, application A issues a token via IdP, and application B obtains its own access token through a token exchange or browser redirection. However, this process is limited because only the same user can be authenticated. Moreover, the tokens used for exchange are only valid for accessing the corresponding resources; if leaked, these resources can be accessed, resulting in low security.
[0011] This application provides an authentication method implemented by an electronic device, such as... Figure 1 As shown, the process includes the following steps S101 and S102: Step S101: In response to the authentication request of the first application, determine the application relationship with the second application that has been authenticated based on the authentication information carried in the authentication request.
[0012] In the embodiments of this application, the electronic device is a device with authentication function. Exemplary electronic devices may be tablet computers, laptop computers, desktop computers, servers, etc., and there is no limitation on the exemplary electronic devices herein.
[0013] In the embodiments of this application, if an electronic device receives an authentication request from a first application, it can determine the application relationship with a second application that has already been authenticated based on the authentication information carried in the authentication request.
[0014] In the embodiments of this application, the authentication request is an identity authentication request initiated by the first application to the electronic device, used to submit identity-related information, complete the identity consistency verification, and thereby obtain a legitimate access authorization credential. It is a pre-security step in the access control process.
[0015] In embodiments of this application, the information to be authenticated is information capable of determining the application relationship with the second application. After receiving an authentication request, the information to be authenticated is parsed from the authentication request, and then the application relationship between the authenticated second applications is determined based on the information to be authenticated. For example, the information to be authenticated includes, but is not limited to, security context data such as application identifiers, device fingerprints, timestamps, and signatures, which are used for subsequent identity verification and association determination.
[0016] In the embodiments of this application, the second application is an application that has been authenticated by the electronic device. Determining the application relationship means judging whether there is a preset logical association between the first application and the authenticated second application. This logical association can be statically configured or dynamically inferred.
[0017] In the embodiments of this application, the first application and the second application can be web applications or native applications on Windows.
[0018] Step S102: In response to the application relationship meeting the target conditions, issue an access credential indicating that the authentication has been passed to the first application, so that the first application can access the required resources based on the access credential.
[0019] In the embodiments of this application, if the application relationship meets the target conditions, it means that there is a preset logical relationship between the first application and the second application. At this time, the electronic device will issue an authenticated access credential to the first application. That is, since the application relationship between the first application and the second application meets the target conditions, the first application can obtain the access credential to access the required resources. In this way, there is no need to authenticate the first application again.
[0020] In the embodiments of this application, the access credentials may be issued by returning them directly to the first application through a secure channel or by forwarding them through an intermediate proxy server. To ensure transmission security, the access credentials are usually encrypted using Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) and accompanied by a digital signature to prevent tampering.
[0021] In the embodiments of this application, based on access credentials, the first application can access the same resources as the second application, or it can access different resources.
[0022] In this way, if the application relationship between the first application and the already authenticated second application meets the target conditions, the first application can obtain access credentials, regardless of whether the first application and the second application are from the same user, making the transfer of identity between applications more flexible.
[0023] In some embodiments, such as Figure 2 As shown, the electronic device can also perform the following steps S201 to S203: Step S201: In response to the authentication request sent by the second application after completing local identity verification on the access key interface, the second application is authenticated based on the first key carried in the authentication request, and the authentication result is obtained; the first key is a key generated based on the access key; the access key interface is a local verification interface loaded by the browser when the second application runs by calling the identity proxy component.
[0024] In the embodiments of this application, the access key interface is a local verification interface loaded by the browser when the second application runs by calling the identity proxy component. It is a dedicated front-end interactive page hosted by the electronic device (IdP) system and displayed to the user, and serves as the interactive carrier for the entire identity authentication process.
[0025] In the embodiments of this application, when the second application is running on its parent device, it can complete local identity verification on the passkey interface. For example, the second application completes local identity verification as follows: when the second application is running on its parent device, it calls the identity proxy component and launches a browser; the browser loads the electronic device authentication page, then calls the Windows API to display the passkey interface, where the user completes authentication. The user can complete authentication on the passkey interface through biometrics (fingerprint, facial recognition) or a Windows Personal Identification Number (PIN).
[0026] In the embodiments of this application, the access key is usually generated by the user after completing local identity verification through biometrics (such as fingerprints, facial recognition) or device PIN code during the first registration or login, and is uniquely bound to a specific device to ensure the security and non-forgeability of the authentication process, so as to realize the hardware authentication guarantee of Passkey and enhance security.
[0027] In the embodiments of this application, the second application completes local identity verification based on the passkey interface after the device is running. Since the passkey has inherent hardware binding, anti-phishing, and anti-password leakage capabilities, the security and strength of authentication are improved.
[0028] In an embodiment of this application, after completing local hardware-level authentication, the second application can send an authentication request carrying the first key to the electronic device.
[0029] In embodiments of this application, the first key is an encryption key generated based on the access key. Exemplarily, the generation mechanism of the first key relies on the private key portion of the access key and the device fingerprint, ensuring the uniqueness of each device and each authentication.
[0030] Step S202: In response to the authentication result indicating that the first key is consistent with the registration key, it is determined that the second application verification is successful; the registration key is the key generated based on the pass key sent by the second application during the registration phase.
[0031] In embodiments of this application, the electronic device verifies the first key carried in the authentication request sent by the second application. Exemplarily, the authentication key pre-stored by the electronic device is also a key generated based on the access key. This key is sent to the electronic device by the second application during the registration phase, and the electronic device receives and stores it for subsequent authentication of the second application.
[0032] In the embodiments of this application, the registration key sent during the second application registration phase and the first key carried in the authentication request can be keys obtained by the second application using the same method to operate on the same information at different phases, or the same key sent by the second application during both the registration and authentication phases.
[0033] In the embodiments of this application, the first key and registration key can encrypt not only the access key, but also other information. For example, other information may be the device identifier (device fingerprint, device number, serial number, etc.) of the device to which the second application belongs, or a random number, etc. The first key and registration key sent by the second application should be consistent. If they are consistent, it means the second application has passed authentication; if they are inconsistent, it means the second application has failed verification.
[0034] Step S203: In response to the successful verification of the second application, the authentication result is encapsulated into a group identifier and sent to the second application so that the second application can store the group identifier in the secure space; the secure space is the storage space that the second application can access.
[0035] In the embodiments of this application, if the second application verification is successful, the electronic device will encapsulate the authentication result into a group identifier and send it to the second application. The group identifier can be randomly generated identification information for the application group to which the second application belongs, and this group identifier information indicates that the second application has completed authentication on the electronic device.
[0036] In the embodiments of this application, before completing local identity verification on the access key interface, the second application first obtains the stored group identifier from the accessible secure space and determines the group relationship between itself and the application corresponding to the stored group identifier. If they belong to the same group, local identity verification is not required on the access key interface. If there is no group relationship between the second application and the application corresponding to the stored group identifier, local identity verification needs to be completed on the access interface. That is, if the second application completes local identity verification on the access interface, it means that the second application is the first application in the corresponding group to authenticate on the electronic device.
[0037] In the embodiments of this application, the first application in the group is the master application after the electronic device completes the verification. The electronic device will issue a group identifier for the group. The group identifier indicates that other subordinate applications in the group, excluding the master application, can obtain the corresponding access credentials based on the group identifier.
[0038] In embodiments of this application, after obtaining the group identifier issued by the electronic device, the second application stores the group identifier in a secure space. The secure space is a local secure storage space; exemplarily, it can be system secure storage, a trusted environment, a key chain, a credential manager, or a protected application sandbox. This secure space is typically protected at the hardware level by the operating system, restricting access by unauthorized processes and preventing malware from stealing credentials.
[0039] In the embodiments of this application, the secure space is the storage space that the second application can access. For example, the storage space that the second application can access may be the local storage space of the device running the second application, or other devices that have a trusted connection relationship with the device running the second application.
[0040] Thus, when the second application is authenticated as the first application in the same group, it needs to complete local identity verification in the access key interface, and then send the key generated based on the access key to verify its identity. After successful verification, it obtains the group identifier, so that applications belonging to the same group as the second application can obtain the corresponding access credentials based on the group identifier, which improves the flexibility of multi-application authentication.
[0041] In some embodiments, the secure space may be: a local secure area corresponding to the electronic device running the first application and the second application, so that the first application can access it.
[0042] In the embodiments of this application, if the first application and the second application belong to the same device, then after the second application obtains the group identifier, it can store the group identifier in the local security area. For example, the local security area is the content of the security space discussed above.
[0043] In the embodiments of this application, since the first application and the second application belong to the same device, the first application can also access the local security zone. Thus, the authentication information carried in the authentication request sent by the first application to the electronic device may include the group identifier stored therein. Of course, the application relationship between the first application and the application storing the group identifier needs to meet the target conditions.
[0044] In the embodiments of this application, after a user is authenticated through the second application, the electronic device issues a group token to the second application. The second application securely stores this group token in the local security zone of the electronic device running both the first and second applications. Subsequently, other applications within the same application group (e.g., the first application) can automatically read the group token stored in the local security zone and trigger the access credential acquisition process upon startup, without requiring the user to authenticate again. This mechanism is particularly suitable for enterprise multi-software family scenarios, where multiple desktop clients can achieve seamless single sign-on through a shared security space.
[0045] In some embodiments, the security space may be: a local security zone corresponding to the first electronic device running the second application, so that when the second electronic device running the first application is interconnected with the first electronic device, the first application can access the first application across devices.
[0046] In the embodiments of this application, the security space is the local security area corresponding to the first electronic device running the second application. At this time, the second electronic device running the first application is not the same device. In this case, the first application can access the local security area of the first electronic device across devices through the connection relationship between the first electronic device and the second electronic device.
[0047] In the embodiments of this application, a trusted connection needs to be established between the first electronic device and the second electronic device. For example, the trusted connection can be a Bluetooth connection, Wi-Fi Direct, Near Field Communication (NFC), etc. When the second electronic device running the first application is interconnected with the first electronic device, the first application can read and use the group identifier across devices through the secure channel built by the trusted connection, thereby realizing the cross-device use of the group identifier.
[0048] In embodiments of this application, when a second application receives a Group Token issued by an electronic device, it securely stores the Group Token in the local secure area of the first electronic device running the second application. Subsequently, other applications belonging to the same application group as the second application (e.g., the first application running on the second electronic device) can, upon startup, read the Group Token stored in the local secure area of the first electronic device through the trusted connection between the first and second electronic devices and trigger the access credential acquisition process.
[0049] In some embodiments, a local security zone corresponding to the second electronic device running the first application is provided so that the first application can access it; wherein, the information stored in the security space is information synchronized when the first electronic device running the second application and the second electronic device are interconnected.
[0050] In the embodiments of this application, the secure space is the local secure area corresponding to the second electronic device running the first application. At this time, the second electronic device and the first electronic device running the first application are not the same device. In this case, the second application can synchronize the group identifier to the local secure area of the second electronic device running the first application through the connection relationship between the first electronic device and the second electronic device. In this way, when the first application is used later, it can directly read from the local secure area of the second electronic device and trigger the access credential acquisition process without requiring the user to perform identity authentication again.
[0051] In the embodiments of this application, when the second application receives a Group Token issued by an electronic device, it securely stores the Group Token in the local security zone of the first electronic device running the second application. Then, when the first electronic device and the second electronic device are interconnected, the second application can synchronize the group identifier to the local security zone corresponding to the second electronic device running the first application. Subsequently, other applications in the same application group (e.g., the application running on the second electronic device (the first application)) can directly read the Group Token stored in the local security zone of the second electronic device and trigger the access credential acquisition process when they start up.
[0052] In this way, by ensuring that the group token can be obtained by the first application that accesses it, regardless of where the group token is stored, the secure storage and reliable transmission of the group token across different devices and applications can be guaranteed. This avoids the identity authentication unavailability problems caused by dependence on specific clients, network interruptions, or leakage of authentication information in related technologies. As a result, a cross-application identity authentication mechanism with enhanced security and availability can be achieved, improving the centralized management capabilities of enterprises and the ease of user operation in multi-software matrix scenarios.
[0053] In some embodiments, the information to be authenticated includes a group identifier to be authenticated and a first application identifier of a first application. When the electronic device performs the above step S101, "determining the application relationship with the already authenticated second application based on the information to be authenticated carried in the authentication request," as follows: Figure 3 As shown, it may also include the following steps S301 and S302: Step S301: In response to finding the target group identifier that matches the identifier of the group to be authenticated from the preset application group information, obtain multiple application identifiers corresponding to the target group identifier.
[0054] In the embodiments of this application, the information to be authenticated is the group identifier stored in the local security area when the first application starts. For example, the first application can directly access the local security area corresponding to the electronic device running the first application and the second application, or when the second electronic device running the first application is interconnected with the first electronic device, the first application can access the local security area corresponding to the first electronic device running the second application across devices, or read the stored group identifier from the local security area corresponding to the second electronic device running the first application.
[0055] In the embodiments of this application, when the first application reads the group identifiers stored in the secure space, it can identify the relationship between each group identifier and the application corresponding to the group identifier, or identify the application group to which it belongs, and then encapsulate the matching group identifier as the identifier to be authenticated into the authentication request.
[0056] In the embodiments of this application, the authentication request carries not only the group identifier to be authenticated, but also the first application identifier of the first application. The first application identifier is typically assigned during application registration, such as an application ID, package name (e.g., com.example.app), or a globally unique identifier (GUID). The first application identifier is used in the authentication process to identify which application is requesting authentication, so as to subsequently determine whether permission mapping and access credentials have been issued. The group identifier to be authenticated and the first application identifier together constitute the parameters of the authentication request, forming a pair of group identifiers and applications.
[0057] In embodiments of this application, the electronic device pre-stores preset application group information, which includes different group identifiers and multiple application identifiers corresponding to each group identifier, forming a mapping relationship between group identifiers and application identifiers. The preset application group information can be stored in a local cache, a memory-mapped table, a persistent database (such as SQLite or MySQL), or a distributed storage system.
[0058] For example, the set of multiple application identifiers corresponding to group identifier FIN_GROUP_001 may include {FIN_REPORT_123, FIN_ANALYST_456, FIN_AUDIT_789}, while the set of multiple application identifiers corresponding to OFFICE_GROUP_002 may include {DOC_EDITOR_101, EMAIL_CLIENT_202, MEETING_TOOL_303}.
[0059] In embodiments of this application, the electronic device parses the authentication information carried in the authentication request, and then matches it with the authentication group identifier in the authentication information. If the authentication group identifier can be found in the preset application group information, it is determined to be the target group identifier. For example, if the authentication group identifier is OFFICE_GROUP_002, it means that the target group identifier has been found in the preset application group information, and then multiple application identifiers corresponding to the target group identifier are obtained, namely {DOC_EDITOR_101, EMAIL_CLIENT_202, MEETING_TOOL_303}.
[0060] Step S302: In response to the inclusion of a first application identifier among multiple application identifiers, determine that the application relationship satisfies the target condition.
[0061] In the embodiments of this application, satisfying the target condition means that the current first application belongs to a group containing a second application that has been authenticated, thereby allowing other applications in the group to inherit the authentication status. When the first application identifier is included in multiple application identifiers, it indicates that the first application is indeed defined as a legitimate member of the group in the preset application group information. Therefore, the application relationship satisfies the target condition, and the subsequent identity conversion process can proceed.
[0062] For example, assuming the first application identifier is FIN_REPORT_123, and the target group identifier FIN_GROUP_001 corresponds to multiple application identifiers {FIN_REPORT_123, FIN_ANALYST_456}, since the first application identifier FIN_REPORT_123 exists among the multiple application identifiers corresponding to the target group identifier FIN_GROUP_001, it is determined that the application relationship meets the target condition, and the application with the first application identifier FIN_REPORT_123 is allowed to obtain access credentials without repeated authentication.
[0063] In this way, by introducing a combination of the group identifier to be authenticated and the first application identifier, and combining it with the group-application mapping relationship in the preset application group information, the trust relationship between applications can be accurately determined. This ensures that authorization is only granted to applications within the legitimate group, thereby preventing unauthorized applications from impersonating the group authentication results. This ensures the security and compliance of identity transfer. Furthermore, the authentication request only carries the group identifier to be authenticated and the application identifier, without involving the key of the already authenticated application, thus providing a high level of security.
[0064] In some embodiments, the electronic device may further perform the following steps: in response to application group information sent by the second application, storing the application group information in preset application group information; the application group information includes a group identifier and an application identifier of at least one application corresponding to the group identifier.
[0065] In the embodiments of this application, application group information refers to the application group information reported by the second application to the electronic device regarding the application group to which the second application belongs, including the group identifier of the second application and the application identifier of at least one application corresponding to the group identifier.
[0066] For example, the application group information sent by the second application can be information corresponding to a user-defined application group. That is, the application group information sent by the second application in the preset application group information is unchanging, fixed, or has a validity period.
[0067] In embodiments of this application, the preset application group information may store group identifiers sent by multiple authenticated applications, along with corresponding application group information. This information is updated upon receiving application group information sent by a second application. For example, the application group information sent by the second application may be transmitted in JSON or XML format, used to establish and maintain the logical attribution relationship between group identifiers and applications.
[0068] In some embodiments, the electronic device may further perform the following steps: in response to the updated application group information sent by the second application, update the preset application group information based on the updated application group information; the updated application group information includes a group identifier and an application identifier of at least one application corresponding to the group identifier; the updated application group information is information that the second application will trigger to upload when the application included in at least one application appears.
[0069] In the embodiments of this application, updating application group information refers to a modification request submitted proactively by the second application during operation due to business changes, function upgrades, or organizational restructuring. Updating application group information may include adding new member applications or removing deactivated applications.
[0070] For example, when an enterprise replaces the driver manager in the device activation scenario group with a new version of the tool, the second application will upload an updated application group information update request, thereby updating the corresponding entries in the preset application group information.
[0071] For example, when main application A starts and calls plugin B, plugin B recognizes that it has been included in the plugin group of main application A. Main application A will upload and update the application group information, informing the electronic device that the group identifier is Group_A and the identifier of the newly added member application is Plugin_B. Then, after main application A calls plugin B, it calls plugin C. At this time, main application A will upload and update the application group information, informing the electronic device that the group identifier is Group_A and the identifier of the newly added member application is Plugin_C. That is, the application identifier corresponding to the group identifier changes in real time, and this change can be uploaded in real time by main application A to ensure that the preset application group information stored in the electronic device is up-to-date.
[0072] In the embodiments of this application, upon receiving updated application group information, the changes are parsed, and corresponding add, delete, or modify operations are performed in the preset application group information to ensure that the group member relationships remain consistent with the actual situation. This mechanism enables automatic discovery and dynamic expansion of application group relationships without manual intervention, significantly reducing operation and maintenance costs.
[0073] In this way, by responding to and updating application group information sent by the second application, the preset application group information is dynamically maintained. This ensures the real-time nature and accuracy of application group member relationships, thereby supporting subsequent authentication and access credential conversion processes, and ultimately improving the security and efficiency of multi-application collaboration.
[0074] In some embodiments, the information to be authenticated includes application metadata of the first application, such as... Figure 4 As shown, in performing step S101 above, "determining the application relationship with the already authenticated second application based on the authentication information carried in the authentication request," the electronic device can also perform the following steps S401 to S402: Step S401: Based on preset grouping rules and application metadata, determine the associated applications of the first application; the application metadata includes application structured information, the target business being executed by the application, and one or more of the functional roles to which the application belongs.
[0075] In the embodiments of this application, the preset grouping rule refers to a pre-configured set of logical rules used to determine which applications should be grouped into the same group based on application metadata. The application metadata includes, but is not limited to: application structured information, the target business being executed by the application, and the functional role to which the application belongs.
[0076] In the embodiments of this application, the electronic device determines the associated applications of the first application based on preset grouping rules and application metadata.
[0077] For example, an electronic device can infer that the second application is the master application and the first application is the slave application by analyzing the application's startup chain (such as the second application starting the first application) or inter-process communication mode, thereby treating the second application as an associated application of the first application.
[0078] For example, in enterprise software, a master application named VantageService and multiple plugin applications named Addin, although different in name, can be identified as belonging to the same logical group through the startup dependencies, shared namespaces, and functional roles in the application metadata. If the first application is one of the multiple plugin applications named Addin, then the master application named VantageService, as well as the other plugin applications named Addin, are the associated applications of the first application.
[0079] Step S402: In response to the associated application including the second application, determine that the application relationship meets the target condition.
[0080] In the embodiments of this application, after determining the associated application of the first application, the electronic device will determine whether the associated application includes the second application. If it does, it means that the two satisfy the association relationship represented by the preset grouping rule, and the subsequent access credential conversion process can continue; otherwise, the authentication request will be rejected, and the second application will be required to complete the authentication independently.
[0081] In the embodiments of this application, precise control over identity transmission eligibility is achieved by determining whether a second application is included in the associated application. This prevents unauthorized applications from gaining access, thereby ensuring the security of the system and enabling controlled identity propagation under asymmetric permission allocation.
[0082] For example, an electronic device can also maintain a dynamically updated group mapping table to record the group affiliation information of each application. For instance, after a second application is authenticated, upon receiving the first application, it determines whether there is an association relationship represented by the preset grouping rule between the first application and the authenticated second application based on preset grouping rules and application metadata. If so, it directly determines that the application relationship meets the target condition.
[0083] In this way, the system can directly determine whether there is a relationship between the first application and the second application based on the preset group identifier and application metadata. If there is a relationship, the target condition is met, and an access credential indicating that the authentication has been passed is issued to the first application so that the first application can access the required resources based on the access credential. There is no need to issue a group identifier, which improves the diversity of authentication.
[0084] In some embodiments, when the electronic device performs the above step S401, it may perform the following steps: in response to the preset grouping rule being grouped according to the application master-slave relationship, based on the application structured information, identify the master application to which the first application belongs, and determine the identified master application as the associated application.
[0085] In the embodiments of this application, application master-slave relationship grouping refers to grouping a master application (e.g., Launcher, Hub, Shell) and several subordinate applications (e.g., plugins, sub-modules, supporting tools) that it controls or depends on, according to the master-satellite structure that naturally exists in the application ecosystem. This grouping method can reflect the logical control and credential delegation relationship between applications, and realize an identity transfer mechanism in which the master application initiates authentication and automatically benefits from the application. For example, in the Vantage system, VantageService is the master application, and the Addin component of VantageService is the subordinate application, forming a master-slave relationship group.
[0086] In the embodiments of this application, the application structured information is used to describe the topological relationship between the first application and other applications, including process tree startup relationships, inter-process communication (IPC) topology, shared namespaces, service call chains, and other structural signals. By parsing this structured information, it is possible to infer which applications have a master-slave control relationship with the first application, thereby accurately identifying the master application to which the first application belongs. For example, if the second application starts the first application and continuously communicates with the first application through IPC, the first application can be determined to be a slave application of the second application.
[0087] For example, an electronic device can also directly determine whether there is a master-slave relationship between the first application and the authenticated application based on the application metadata of the first application. If there is, the corresponding master application is identified as the associated application. In this way, there is no need to determine whether the associated application contains the second application again. The device can directly issue an access credential indicating that the authentication has been passed to the first application so that the first application can access the required resources based on the access credential.
[0088] In this way, the master-slave relationship is automatically identified through structured information, eliminating the need for manual configuration and improving the automation and accuracy of grouping. Simultaneously, grouping based on the master-slave relationship supports asymmetric permission allocation, meaning the master application assumes primary authentication responsibility, while subordinate applications can obtain authorization simply through logical association. This achieves controlled propagation of identity credentials, enhancing security and management efficiency.
[0089] In some embodiments, when an electronic device performs step S401, it may perform the following steps: in response to a preset grouping rule that is grouped by business scenario, based on the target business performed by the first application, identify the application that performs the same business as the first application, and determine the identified application as an associated application.
[0090] In the embodiments of this application, business scenario grouping refers to grouping the set of applications involved in a user's completion of a specific business objective into an independent business scenario group. For example, a device activation scenario may include Basic Input Output System (BIOS) tools, driver manager, and license service; a remote collaboration scenario may include video conferencing, whiteboard, and file synchronization applications.
[0091] In the embodiments of this application, the target service is the specific business task currently being executed by the first application. The electronic device can match other applications that are executing the same target service based on the business task being executed, so as to obtain the associated application.
[0092] Of course, when an electronic device detects that the first application is executing the device activation process, it can also search for all other applications (applications that have been authenticated) participating in the device activation process and identify the found applications as associated applications of the first application. In this way, there is no need to check whether the associated applications include the second application again, and the device can directly issue access credentials that indicate that the authentication has been passed to the first application, so that the first application can access the required resources based on the access credentials.
[0093] In some embodiments, when the electronic device performs the above step S401, it may perform the following steps: in response to the preset grouping rule being grouped by function, based on the functional role to which the first application belongs, identify the application with the same functional role as the first application, and determine the identified application as an associated application.
[0094] In the embodiments of this application, functional grouping refers to abstracting applications into different functional roles (such as identity providers, resource consumers, data pipelines, audit observers, etc.) and grouping applications with the same functional role together. For example, all resource consumer applications share a scope-restricted credential group, and all data pipeline applications share a credential group with data access privileges. This functional grouping method focuses on the application's role within the system architecture, rather than specific business content or structural relationships.
[0095] In the embodiments of this application, the application metadata of the first application can directly carry the functional role to which the first application belongs, thereby identifying applications with the same functional role as the first application as associated applications. For example, if the first application is a data acquisition tool and the functional role to which the application belongs is a data pipeline, then all applications marked as data pipelines will be identified as associated applications.
[0096] In embodiments of this application, the electronic device can also directly search among the authenticated applications for an application with the same functional role based on the functional role of the first application. If such an application exists, it can directly issue an access credential indicating that the first application has passed authentication, so that the first application can access the required resources based on the access credential.
[0097] Thus, by introducing three grouping rules—grouping by application master-slave relationship, grouping by business scenario, and grouping by function—intelligent division of application groups is achieved. This enables dynamic determination of associated applications based on the actual operating environment and design intent of the application, thereby accurately controlling the scope of identity credential dissemination and improving security and user experience across multiple application scenarios.
[0098] In some embodiments, such as Figure 5 As shown, the electronic device can also perform the following steps S501 to S503: Step S501: In response to the authentication request of the first application, parse the authentication request and obtain the parsing result.
[0099] In the embodiments of this application, when an electronic device receives an authentication request from a first application, it can parse the authentication request and obtain a parsing result.
[0100] In embodiments of this application, the parsing result is intermediate data generated after structured extraction and semantic analysis of the authentication request content. For example, the parsing result may indicate whether the authentication request carries a group identifier or a first key.
[0101] Step S502: In response to the parsing result satisfying the first condition, carry the authentication information to be authenticated based on the authentication request, and convert the access credentials based on the authentication information.
[0102] In the embodiments of this application, the first condition is that the first application identifies the existence of the second application in its application group based on the obtainable group identifier. That is, the parsing result satisfies the first condition that the parsing result is that the authentication request carries the group identifier. This is because the first application will only carry the group identifier after obtaining the group identifier based on the security space it can access, and then determining its application group and the association relationship with the master application in its application group.
[0103] In the embodiments of this application, if the parsing result meets the first condition, it means that the second application associated with the first application has been authenticated. At this time, it is only necessary to convert the access credentials based on the authentication group identifier and the first application identifier in the authentication information, that is, to start the conversion process.
[0104] Step S503: In response to the parsing result not meeting the first condition, authenticate the first application based on the first key carried in the authentication request.
[0105] In the embodiments of this application, the first condition is not met when the first application identifies that there is no second application in the application group to which it belongs based on the obtainable group identifier. That is, the parsing result does not meet the first condition when the parsing result is that the authentication request carries the first key, because only the first application will carry the first key when it needs to authenticate for the first time.
[0106] In the embodiments of this application, if the parsing result does not meet the first condition, it means that no second application that is related to the first application has been authenticated before the first application. In this case, the first application needs to be authenticated based on the first key carried in the authentication request.
[0107] In this way, the corresponding operation can be performed on the first application based on the content carried in the authentication request, thus improving the accuracy of authentication.
[0108] In one embodiment of this application, in response to an authentication request from a first application, the authentication request carries authentication information to be authenticated; the authentication information includes an identifier of the group to be authenticated and an identifier of the first application of the first application; in response to finding a target group identifier that matches the identifier of the group to be authenticated from the preset application group information, multiple application identifiers corresponding to the target group identifier are obtained; in response to the first application identifier being included among the multiple application identifiers, it is determined that the application relationship meets the target condition; the preset application group information includes different group identifiers and multiple application identifiers corresponding to each group identifier; in response to the application relationship meeting the target condition, an access credential indicating successful authentication is issued to the first application, so that the first application can access the required resources based on the access credential. Specifically, in response to application group information sent by a second application, the application group information is stored in the preset application group information; in response to updated application group information sent by the second application, the preset application group information is updated based on the updated application group information; the updated application group information or application group information includes a group identifier and an application identifier of at least one application corresponding to the group identifier; the updated application group information is information that the second application will trigger to upload when at least one application included in the application appears.
[0109] In another embodiment of this application, in response to an authentication request from a first application, the authentication request carries authentication information; the authentication information includes application metadata of the first application; based on preset grouping rules and application metadata, associated applications of the first application are determined; in response to the associated applications including a second application, the application relationship is determined to meet the target conditions; the application metadata includes one or more of the following: application structured information, the target business being executed by the application, and the functional role to which the application belongs; wherein, in response to the preset grouping rules and application metadata, determining the associated applications of the first application includes at least one of the following: in response to the preset grouping rule being grouped according to the application master-slave relationship, based on the application structured information, the master application to which the first application belongs is identified, and the identified master application is determined as an associated application; in response to the preset grouping rule being grouped according to the business scenario, based on the target business executed by the first application, an application executing the same business as the first application is identified, and the identified application is determined as an associated application; in response to the preset grouping rule being grouped according to function, based on the functional role to which the first application belongs, an application with the same functional role as the first application is identified, and the identified application is determined as an associated application.
[0110] In another embodiment of this application, in response to the authentication request sent by the second application after completing local identity verification on the access key interface, the second application is authenticated based on the first key carried in the authentication request, and an authentication result is obtained; the first key is a key generated based on the access key; the access key interface is a local verification interface loaded by the browser when the second application runs by calling the identity proxy component; in response to the authentication result indicating that the first key is consistent with the registration key, it is determined that the second application has been successfully verified; the registration key is a key generated based on the access key sent by the second application during the registration phase; in response to the successful verification of the second application, the authentication result is encapsulated into a group identifier and sent to the second application so that the second application can store the group identifier in a secure space; the secure space is a storage space that the second application can access; the secure space is one of the following: an electronic storage space for running the first application and the second application. The device has a local security zone corresponding to it, which enables the first application to access it; the first electronic device running the second application has a local security zone corresponding to it, which enables the first application to access the device across devices when the second electronic device running the first application is interconnected with the first electronic device; the second electronic device running the first application has a local security zone corresponding to it, which enables the first application to access it; wherein, the information stored in the security space is the information synchronized when the first electronic device running the second application is interconnected with the second electronic device; in response to the authentication request of the first application, the application relationship between it and the authenticated second application is determined based on the authentication information carried in the authentication request; in response to the application relationship meeting the target conditions, an access credential representing successful authentication is issued to the first application, so that the first application can access the required resources based on the access credential, wherein the authentication information is the group identifier and application identifier obtained from the security space.
[0111] like Figure 6 As shown, an exemplary application login authentication method is provided, including the following steps S601 to S611: Step S601: The user opens the application.
[0112] Here, the user clicks the icon on their mobile phone / terminal device to open the target application, and the entire login authentication process officially begins.
[0113] Step S602: Is this your first time logging in?
[0114] Here, the mobile phone / terminal device will read the historical login cache records stored in the device and automatically perform the following logical judgment: verify whether the current account is the first login operation on this device. If so, proceed to step S603; if not, proceed to step S606.
[0115] Step S603: Redirect to the browser and enter your account and password.
[0116] Here, the application will redirect to a browser page, load the server authentication page using the browser, and then call the Windows API to display the passkey interface, where the user completes authentication.
[0117] Step S604: Login successful, register device fingerprint to server.
[0118] Here, the user enters their account and password on the browser page and submits it. The backend account authentication server verifies the legitimacy of the user's identity. After successful verification, the app returns a successful login result to the mobile phone / terminal device. After successful login, the app automatically collects the unique feature information of the current device (device fingerprint, including device model, system identifier, de-identified hardware features, etc.), binds the fingerprint to the current account, and uploads it to the server to complete the registration and storage of the device fingerprint.
[0119] Step S605: The device is trusted and an access credential is issued.
[0120] Here, the server verifies the device fingerprint, marks the device as a trusted device, and then issues encrypted access credentials to the App.
[0121] Step S606: Is the local certificate valid?
[0122] Here, when the application issues access credentials upon first login, an expiration date is set. Here, it can be determined whether the local credentials are valid. If they are valid, step S611 is executed; if they have expired, step S608 is executed.
[0123] Step S607: Automatically verify identity to the server using device fingerprint.
[0124] Here, the mobile phone / terminal device uses its device fingerprint to prove its identity to the server.
[0125] Step S608: Server verification passed.
[0126] Here, the server verifies the device fingerprint of the mobile phone / terminal device. If the verification fails, step S609 is executed; if the verification succeeds, step S610 is executed.
[0127] Step S609: Prompt to log in again.
[0128] Here, the mobile phone / terminal device prompts the user to log in again.
[0129] Step S610: Issuance of new credentials is seamless for the user.
[0130] Here, once the server verifies the credentials, a new certificate is issued, and the user remains unaware of the process.
[0131] Step S611: Apply directly without any further action.
[0132] Here, users can use the application.
[0133] In this way, Passkey hardware authentication is achieved and security is enhanced.
[0134] like Figure 7 As shown, an exemplary authentication method is provided, including the following steps S701 to S706: Step S701: The user opens application A.
[0135] Here, the user (human operator of the Windows device) 71 operates the electronic device's display interface, clicks the icon of application A 72, and launches the application.
[0136] Step S702: Application A initiates a token acquisition request.
[0137] Here, application A (Windows App A) 72 directly calls the AcquireToken() interface within its own process to initiate an authorization request to the identity broker component (Windows Identity Broker) 73 within the same process.
[0138] Step S703: The identity agent component initiates the authorization interaction.
[0139] Here, the identity agent component 73 invokes the system browser 74 via ShellExecute, carries the Proof Key for Code Exchange (PKCE) parameter to launch the authorization website, and begins the authorization process.
[0140] Step S704: The user performs identity verification.
[0141] Here, the user submits account credentials to the server 75 through an HTTPS encrypted channel in the system browser 74 to complete identity verification and confirm authorization.
[0142] Step S705: Loopback redirection returns the token.
[0143] Here, the server generates a group identifier at 75 and sends the Auth Code back to the system browser at 74 via local loopback redirection.
[0144] Step S706: Deliver the authorization code to the system browser.
[0145] Here, the system browser 74 securely delivers the obtained group identifier to the identity agent component 73 that initiated the authorization via local loopback redirection.
[0146] Step S707: Token returned.
[0147] Here, the group identifier is returned to application A72, and application A72 stores the group identifier to the local security zone.
[0148] Step S708, B: Application startup.
[0149] Here, user 71 operates the electronic device's display interface, clicks the icon of application B 76, and launches the application.
[0150] Step S709: B. The application initiates a token acquisition request.
[0151] Here, application B (Windows App B) 76 directly calls the AcquireToken() interface within its own process to request a token from the identity agent component 73 within the same process.
[0152] Step S710: Exchange access credentials.
[0153] Here, the identity proxy component 73 obtains access credentials from the group identifier stored in the local security zone by application B from the server 75.
[0154] Step S711: Return access credentials.
[0155] Here, the identity proxy component 73 will provide the access credentials obtained from the server 75 to application B 76.
[0156] In this way, users only need to complete high-strength authentication once in one application, and other applications can be automatically authorized; suitable for scenarios where enterprises have multiple desktop clients; can perform fine-grained authorization according to application groups, application identification information (AppID), roles, device status and other dimensions; reduce the cost of repeated logins and improve the efficiency of software matrix collaboration.
[0157] This application provides an authentication method that, in response to an authentication request from a first application, determines the application relationship with an already authenticated second application based on the authentication information carried in the authentication request; and, in response to the application relationship meeting a target condition, issues an access credential indicating successful authentication to the first application, enabling the first application to access required resources based on the access credential. The authentication method provided in this application allows the first application to obtain access credentials simply because the application relationship between the first application and the already authenticated second application meets the target condition, regardless of whether the user is a user of the first or second application, making identity transfer between applications more flexible.
[0158] like Figure 8 As shown, an electronic device 8 is provided, comprising: Memory 81 is used to store one or more computer programs; The processor 82 is configured to execute a computer program stored in memory to: run a first application and generate a corresponding authentication request based on the acquired authentication information; receive an access credential issued after successful authentication through the first application and access the required resources based on the access credential; Alternatively, electronic device 8 has a communication relationship with the device running the first application; The authentication module 83 is used to execute a computer program stored in the memory to: receive an authentication request and determine the application relationship with the second application that has been authenticated based on the authentication information carried in the authentication request; and, in response to the application relationship meeting the target conditions, issue an access credential indicating that the authentication has been passed to the electronic device running the first application.
[0159] In one embodiment of this application, the processor 82 is further configured to: run a second application and call an identity agent component through the second application to launch a browser to load a access key interface; perform local identity verification based on authentication information input by the user in the access key interface; receive a group identifier through the second application and store it in a secure space; the secure space is a storage space that the second application can access; Alternatively, electronic device 8 may have a communication relationship with a device running a second application; The authentication module 83 is also used to execute a computer program stored in the memory to: receive an authentication request sent by the second application after completing local identity verification on the access key interface; authenticate the second application based on the first key carried in the authentication request to obtain an authentication result; the first key is a key generated based on the access key; in response to the authentication result indicating that the first key is consistent with the registration key, determine that the second application has been successfully verified; the registration key is a key generated based on the access key sent by the second application during the registration phase; in response to the second application's successful verification, encapsulate the authentication result into a group identifier and send it to the second application. Among them, the electronic device running the first application, the electronic device running the second application, and the electronic device containing the authentication module are the same or different devices.
[0160] In the embodiments of this application, the electronic device running the first application, the electronic device running the second application, and the electronic device containing the authentication module can be the same device, or the electronic device running the first application, the electronic device running the second application, and the electronic device containing the authentication module can be different devices, or any two of them can be the same device.
[0161] This application provides a computer-readable storage medium storing one or more computer programs, which can be executed by one or more processors to implement the authentication method described above. The computer-readable storage medium can be transient or non-transient.
[0162] This application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements some or all of the steps in the above-described authentication method. This computer program product can be implemented specifically through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied as a computer storage medium; in another optional embodiment, the computer program product is specifically embodied as a software product, such as a software development kit (SDK), etc.
[0163] In some embodiments, the storage medium may be a computer-readable storage medium, which may be volatile memory, such as random-access memory (RAM); or non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), solid-state drive (SSD), ferromagnetic random access memory (FRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic surface memory, optical disk, or compact disk-read-only memory (CD-ROM); or it may be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.
[0164] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.
[0165] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0166] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0167] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0168] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
[0169] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborative files (e.g., a file that stores one or more modules, subroutines, or code sections).
[0170] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely descriptive and do not represent the superiority or inferiority of the embodiments.
[0171] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components may be combined, or integrated into another system, or some features may be ignored or not performed.
[0172] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.
Claims
1. An authentication method, the method comprising: In response to the authentication request of the first application, the application relationship with the authenticated second application is determined based on the authentication information carried in the authentication request; In response to the application relationship satisfying the target condition, an access credential indicating successful authentication is issued to the first application, enabling the first application to access the required resources based on the access credential.
2. The authentication method according to claim 1, further comprising: In response to the authentication request sent by the second application after completing local identity verification on the access key interface, the second application is authenticated based on the first key carried in the authentication request, and an authentication result is obtained; The first key is a key generated based on the access key; The access key interface is a local verification interface loaded by the browser when the second application runs by calling the identity proxy component; In response to the authentication result indicating that the first key is consistent with the registration key, it is determined that the second application verification is successful; The registration key is a key generated based on the access key and sent by the second application during the registration phase; In response to the successful verification of the second application, the authentication result is encapsulated into a group identifier and sent to the second application so that the second application can store the group identifier in a secure space; The secure space is the storage space that the second application can access.
3. The authentication method according to claim 2, wherein the secure space is one of the following: The local security zone corresponding to the electronic device running the first application and the second application is accessed by the first application. The local security zone corresponding to the first electronic device running the second application is configured so that when the second electronic device running the first application is interconnected with the first electronic device, the first application can access it across devices. The local security zone corresponding to the second electronic device running the first application is accessed by the first application; wherein... The information stored in the secure space is information synchronized when the first electronic device running the second application is interconnected with the second electronic device.
4. The authentication method according to claim 2, wherein the information to be authenticated includes the identifier of the group to be authenticated and the first application identifier of the first application; The step of determining the application relationship with the already authenticated second application based on the authentication information carried in the authentication request includes: In response to finding a target group identifier that matches the identifier of the group to be authenticated from the preset application group information, multiple application identifiers corresponding to the target group identifier are obtained; In response to the inclusion of the first application identifier among the plurality of application identifiers, it is determined that the application relationship satisfies the target condition; The preset application group information includes different group identifiers and multiple application identifiers corresponding to each group identifier.
5. The authentication method according to claim 4, further comprising one of the following: In response to the application group information sent by the second application, the application group information is stored in the preset application group information; In response to the updated application group information sent by the second application, the preset application group information is updated based on the updated application group information; The updated application group information or application group information includes a group identifier and an application identifier of at least one application corresponding to the group identifier; The updated application group information is the information that the second application will trigger to upload when the application included in the at least one application appears.
6. The authentication method according to claim 1, wherein the information to be authenticated includes application metadata of the first application, and determining the application relationship with the authenticated second application based on the information to be authenticated carried in the authentication request includes: Based on the preset grouping rules and the application metadata, the associated applications of the first application are determined; In response to the fact that the associated application includes the second application, it is determined that the application relationship satisfies the target condition; The application metadata includes structured application information, the target business being executed by the application, and one or more of the functional roles to which the application belongs.
7. The authentication method according to claim 6, wherein determining the associated application of the first application based on the preset grouping rules and the application metadata includes at least one of the following: In response to the preset grouping rule of grouping by application master-slave relationship, based on the application structure information, the master application to which the first application belongs is identified, and the identified master application is determined as the associated application; In response to the preset grouping rule being grouped by business scenario, based on the target business executed by the first application, an application that executes the same business as the first application is identified, and the identified application is determined as the associated application; In response to the preset grouping rule of grouping by function, based on the functional role of the first application, the application with the same functional role as the first application is identified, and the identified application is determined as the associated application.
8. The authentication method according to claim 2, further comprising: In response to the authentication request from the first application, the authentication request is parsed to obtain the parsing result; In response to the parsing result satisfying the first condition, the access credential is converted based on the authentication request carrying the authentication information and the authentication information. In response to the parsing result not meeting the first condition, the first application is authenticated based on the first key carried in the authentication request; The condition is met when the first application identifies that the second application exists in the application group to which it belongs based on the obtainable group identifier.
9. An electronic device, comprising: Memory, used to store one or more computer programs; The processor is configured to execute a computer program stored in the memory to: run a first application and generate a corresponding authentication request based on the acquired authentication information; receive an access credential issued after successful authentication through the first application and access the required resources based on the access credential; or, The electronic device has a communication relationship with the device running the first application; An authentication module is used to execute a computer program stored in the memory to: receive the authentication request and determine the application relationship with the second application that has been authenticated based on the authentication information carried in the authentication request; In response to the application relationship satisfying the target condition, the access credential indicating successful authentication is issued to the electronic device running the first application.
10. The electronic device according to claim 9, The processor is also configured to: run a second application and call an identity agent component through the second application to launch a browser to load the access key interface; and perform local identity verification based on the authentication information input by the user on the access key interface. The second application receives the group identifier and stores it in a secure space; The secure space is the storage space that the second application can access; or, The electronic device has a communication relationship with the device running the second application; The authentication module is also used to execute the computer program stored in the memory to: receive the authentication request sent by the second application after completing local identity verification on the access key interface, and authenticate the second application based on the first key carried in the authentication request to obtain the authentication result; The first key is a key generated based on the access key; In response to the authentication result indicating that the first key is consistent with the registration key, it is determined that the second application verification is successful; The registration key is a key generated based on the access key and sent by the second application during the registration phase; In response to the successful verification of the second application, the authentication result is encapsulated into a group identifier and sent to the second application; The electronic device running the first application, the electronic device running the second application, and the electronic device containing the authentication module may be the same or different devices.
