Conference access method and related device
By presetting trust policies and identity credential mechanisms on the conference server, the problem that external participants cannot access the conference in cross-domain scenarios is solved, cross-domain authentication and access are realized, and the security and reliability of the conference are improved.
Patent Information
- Application Number
- CN202310715265.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2023-06-15
- Publication Date
- 2024-11-15
AI Technical Summary
In cross-domain scenarios, authentication based on digital certificates cannot be implemented, resulting in external participants being unable to access the meeting, affecting the security and reliability of the meeting.
Cross-domain authentication and access is achieved by presetting trust policies on the conference server, verifying external digital certificates and sending identity credentials to them, enabling them to apply for digital certificates from internal trusted certificate authorities.
Ensure that external participants can access the meeting through authentication in cross-domain scenarios, improve the security and reliability of the meeting, and avoid access restrictions due to certificate interoperability issues.
Smart Images

Figure CN118972083A_ABST
Abstract
Description
[0001] This application claims the priority of the Chinese patent application filed with the China Patent Office on May 15, 2023, with application number 202310543989.X and invention name “A method for verifying user identity”, the entire contents of which are incorporated by reference in this application. Technical Field
[0002] The present application relates to the field of computer security technology, and in particular to a conference access method and related devices. Background Art
[0003] In traditional online conference scenarios, the conference host usually creates the conference and sends the generated conference link and key to those who need to attend the conference. Since the conference link and key can be used to join the conference, the traditional conference access method allows anyone to join the conference at will, which is easy to disrupt the conference order, cause the leakage of private conference content, and even endanger public safety.
[0004] Based on this, the related art proposes a conference access solution based on identity authentication, such as a conference access solution based on end-to-end encryption (E2EE). In the conference access solution based on E2EE, the conference host randomly generates a conference security key, and the conference host performs identity authentication with each participant, and sends the ciphertext of the conference security key to the participants who have passed the identity authentication through the E2EE technology, and the ciphertext of the conference security key can only be decrypted by the corresponding participants.
[0005] However, the E2EE-based conference access solution brings about restrictions on secure access in cross-domain scenarios. In cross-domain scenarios, digital certificates used to represent identities in different domains are usually issued by different certificate authorities (CA). Due to the non-interoperability between different CAs, it is impossible to achieve identity mutual trust based on digital certificates in cross-domain scenarios, which makes it impossible for conference hosts to perform identity authentication with cross-domain external participants, which in turn makes it impossible for cross-domain external participants to access the conference. Summary of the invention
[0006] This application provides a conference access method that can ensure that external participants can access the conference through identity authentication in a cross-domain scenario.
[0007] The first aspect of the present application provides a conference access method, which is applied to a conference server. The method includes: the conference server receives a first access request sent by an electronic device, the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate authority that is not trusted by the conference server. The electronic device is an external participant device that needs to access the conference.
[0008] Then, based on the preset trust policy pre-configured on the conference server, the conference server verifies the first digital certificate, wherein the preset trust policy is used to indicate a list of trusted certificates, and the certificate list includes the root certificate corresponding to the first digital certificate. Specifically, verifying the digital certificate actually requires verifying the entire certificate chain to which the digital certificate belongs, and ultimately implementing the trust in the root certificate of the digital certificate. Therefore, by adding trust in the root certificate corresponding to the first digital certificate to the preset trust policy, the verification of the first digital certificate can be completed according to the verification steps of the digital certificate, thereby realizing the recognition and trust of external identities in cross-domain scenarios.
[0009] Secondly, in response to the first digital certificate passing the verification, the conference server sends an identity credential to the electronic device, and the identity credential is used by the electronic device to apply for a digital certificate from a second certificate authority, and the second certificate authority is an institution trusted by the conference server. The first digital certificate authority and the second digital certificate authority belong to different organizations, and the second digital certificate authority and the conference server belong to the same organization. For example, the second digital certificate authority and the conference server belong to enterprise A, and the first digital certificate authority belongs to enterprise B.
[0010] Finally, the conference server receives a second access request sent by the electronic device and allows the electronic device to access the first conference. The second access request is used to request access to the first conference, and the second access request includes a second digital certificate issued by a second certificate authority for the electronic device.
[0011] In this solution, in a cross-domain scenario, by adding a trusted external root certificate in advance, the digital certificate of the external participant can be verified based on the trusted root certificate. In addition, for the external participant who has passed the digital certificate verification, a temporary identity credential is issued to the external participant, so that the external participant can apply for a digital certificate from the internal trusted certificate authority based on the temporary identity credential, and then the external participant can also hold a digital certificate issued by a trusted certificate authority, ensuring that the external participant can pass identity authentication and access the meeting.
[0012] In a possible implementation, the identity credentials sent by the conference server to the electronic device are encrypted credentials, i.e. credentials in encrypted form. Moreover, the encrypted credentials are obtained by encrypting the public key corresponding to the first digital certificate. In this way, if the electronic device is not the real holder of the first digital certificate, the electronic device does not have the private key corresponding to the first digital certificate, and thus cannot decrypt the encrypted credentials.
[0013] In this scheme, the conference server uses the public key of the first digital certificate to encrypt the ciphertext credentials, so that the electronic device needs to use the private key corresponding to the public key of the first digital certificate to execute the ciphertext credentials, thereby verifying whether the electronic device has control over the private key corresponding to the first digital certificate, avoiding the electronic device from using other people's digital certificates to access the conference, and further improving the security of conference access.
[0014] In a possible implementation, the identity credentials sent by the conference server to the electronic device are obtained by encrypting a login password using the public key corresponding to the first digital certificate, and the login password is used for the electronic device to log in to the identity provider (IDP). The IDP is used to provide identity authentication services for the electronic device in the process of the electronic device applying for a digital certificate from the second certificate authority. In other words, the identity credentials sent by the conference server to the electronic device enable the electronic device to complete the identity authentication process in the process of applying for a digital certificate through the IDP, thereby ensuring that the electronic device can successfully apply for a digital certificate issued by the second certificate authority.
[0015] In this solution, by returning the login password for logging into the IDP to the electronic device, the electronic device can implement identity authentication in the certificate application process based on the IDP, effectively utilizing the certificate application process of the existing technology, reducing changes to the existing technology, and improving the compatibility of this solution.
[0016] In one possible implementation, before receiving the first access request sent by the electronic device, the conference server receives a conference creation instruction, which is used to indicate the attendees corresponding to the first conference, and the attendees include the applicants of the first digital certificate. Then, the conference server sends a temporary identity creation request to the IDP to instruct the IDP to create a temporary conference identity for the attendees. In this way, after the IDP successfully creates a temporary conference identity for the attendees, the conference server generates a login password, which is used to enable the attendees with temporary identities created on the IDP to log in to the IDP. In addition, after generating the login password, the conference server can also perform a series of interactions with the IDP based on the login password, so that the attendees who subsequently hold the login password can smoothly log in to the IDP based on the login password.
[0017] That is to say, during the conference creation process, the conference server instructs the IDP to create a temporary conference identity for each participant and obtains the corresponding login password for each participant. After the participant passes the digital certificate verification, the login password is returned to the participant, so that the participant can obtain the temporary identity created in advance by the IDP, thereby ensuring that they can access the conference securely in the future.
[0018] In addition, the temporary identity created by the IDP for the participant as instructed by the conference server may be bound to the first conference, that is, the temporary identity created by the IDP can only be used to access the first conference, but cannot be used to access other conferences.
[0019] In a possible implementation, the conference creation instruction is also used to indicate the operation permissions of the participants in the conference, such as whether the participants can modify or download files in the conference, share the screen or speak, etc. After allowing the electronic device to access the first conference, the conference server sets the operation permissions of the electronic device in the first conference according to the application identity corresponding to the second digital certificate.
[0020] In this solution, the conference server sets corresponding operation permissions for electronic devices based on the identity of the electronic devices when they access the conference based on the requirements of the conference creation instructions, thereby implementing permission settings for each participant and ensuring conference security in cross-domain conference scenarios.
[0021] In one possible implementation, the preset trust policy used by the conference server to verify the first digital certificate is also used to indicate the conference access rights of one or more objects. In the process of the conference server verifying the first digital certificate, the conference server determines the conference access rights of the applicant of the first digital certificate based on the preset trust policy; and determines whether the applicant has the right to access the first conference based on the type of conference requested to join by the first access request and the conference access rights of the applicant. Among them, the condition for the first digital certificate to pass the verification includes that the applicant has the right to access the first conference. That is, if the applicant of the first digital certificate does not have the right to access the first conference, the first digital certificate cannot pass the verification.
[0022] In this solution, by specifying the conference access rights of participants in the preset trust policy, it can be ensured that only participants with access rights to the current meeting can pass the identity authentication during conference access, avoiding other unrelated participants from accessing the meeting due to the conference host's incorrect designation of participants or incorrect distribution of conference links, thereby improving the security of conference access.
[0023] In one possible implementation, the first conference is an end-to-end encrypted conference. The identity authentication of the external participating device is achieved by adding a trusted root certificate to the conference server, and the identity credentials are sent to the external participating device to trigger the external participating device to replace the joining certificate with a digital certificate issued by the trusted internal certificate authority, thereby ensuring that the external participating device can smoothly interact with any device in the end-to-end encrypted conference based on the replaced digital certificate (that is, any two devices in the end-to-end encrypted conference will also verify each other's identity through digital certificates when interacting), ensuring that the external participating device can smoothly access the conference in a conference scenario that uses digital certificates as end-to-end identity authentication credentials.
[0024] In a possible implementation, the identity field of the first digital certificate is used to indicate the user identity or the device identity. That is, the field used to represent the identity in the first digital certificate (such as the common name field) can indicate the identity of the user or the identity of the device, that is, the identity corresponding to the first digital certificate is not limited to the user, but can also be a device.
[0025] In a possible implementation, the second certificate issuing authority supports the Automatic Certificate Management Environment (ACME) protocol. In this way, the second certificate issuing authority can automatically issue the second digital certificate to the electronic device based on the ACME protocol, thereby improving the efficiency of the digital certificate application process.
[0026] The second aspect of the present application provides a conference access method, which is applied to an electronic device that needs to access a conference. The method includes: the electronic device sends a first access request to a conference server, the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate authority; then, the electronic device receives the identity credentials sent by the conference server; secondly, based on the identity credentials, the electronic device applies for a second digital certificate from a second certificate authority, and the second certificate authority is an institution trusted by the conference server; finally, the electronic device sends a second access request to the conference server and accesses the first conference with the permission of the conference server, the second access request is used to request access to the first conference, and the second access request includes a second digital certificate.
[0027] In a possible implementation, the identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the public key corresponding to the first digital certificate. Based on the identity credential, the specific process of the electronic device applying for a digital certificate from the second certificate issuing authority includes: the electronic device first uses the private key corresponding to the public key to decrypt the ciphertext credential to obtain a plaintext credential; then, based on the plaintext credential, the electronic device applies for a digital certificate from the second certificate issuing authority.
[0028] In one possible implementation, the identity credentials are obtained by encrypting a login password using the public key corresponding to the first digital certificate. The login password is used for the electronic device to log in to the IDP, and the IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate authority.
[0029] In a possible implementation, the first conference is an end-to-end encrypted conference.
[0030] In a possible implementation manner, the identity field of the first digital certificate is used to indicate a user identity or a device identity.
[0031] In a possible implementation, the second certificate authority supports the ACME protocol.
[0032] The third aspect of the present application provides a conference server, including: a receiving module, used to receive a first access request sent by an electronic device, the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate issuing authority; a processing module, used to verify the first digital certificate based on a preset trust policy, the preset trust policy is used to indicate a trusted certificate list, and the certificate list includes a root certificate corresponding to the first digital certificate; a sending module, used to send an identity credential to the electronic device in response to the first digital certificate passing the verification, the identity credential is used for the electronic device to apply for a digital certificate from a second certificate issuing authority, and the second certificate issuing authority is a trusted institution; the receiving module is also used to receive a second access request sent by the electronic device and allow the electronic device to access the first conference, the second access request is used to request access to the first conference, and the second access request includes a second digital certificate, and the second digital certificate is issued to the electronic device by the second certificate issuing authority.
[0033] In a possible implementation, the identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the public key corresponding to the first digital certificate.
[0034] In one possible implementation, the identity credentials are obtained by encrypting a login password using the public key corresponding to the first digital certificate. The login password is used for the electronic device to log in to the IDP, and the IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate authority.
[0035] In one possible implementation, the receiving module is also used to receive a conference creation instruction, which is used to indicate the participants corresponding to the first conference, and the participants include the applicants of the first digital certificate; the sending module is also used to send a temporary identity creation request to the IDP, and the temporary identity creation request is used to instruct the IDP to create a temporary conference identity for the participants; the processing module is also used to generate a login password, and the login password is used to enable the participants with temporary identities created on the IDP to log in to the IDP.
[0036] In one possible implementation, the conference creation instruction is also used to indicate the operating permissions of the participants in the conference; after allowing the electronic device to access the first conference, the processing module is also used to set the operating permissions of the electronic device in the first conference based on the application identity corresponding to the second digital certificate.
[0037] In one possible implementation, the preset trust policy is also used to indicate the conference access rights of one or more objects; the processing module is also used to: determine the conference access rights of the applicant of the first digital certificate based on the preset trust policy; determine whether the applicant has the right to access the first conference based on the type of conference requested to be joined by the first access request and the conference access rights of the applicant; wherein the condition for the first digital certificate to pass the verification includes that the applicant has the right to access the first conference.
[0038] In a possible implementation, the first conference is an end-to-end encrypted conference.
[0039] In a possible implementation manner, the identity field of the first digital certificate is used to indicate a user identity or a device identity.
[0040] In a possible implementation, the second certificate authority supports the ACME protocol.
[0041] The fourth aspect of the present application provides a conference access device, characterized in that it includes: a sending module, used to send a first access request to a conference server, the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate authority; a receiving module, used to receive identity credentials sent by the conference server; a processing module, used to apply for a second digital certificate from a second certificate authority based on the identity credentials, and the second certificate authority is an institution trusted by the conference server; the sending module is also used to send a second access request to the conference server and access the first conference with the permission of the conference server, the second access request is used to request access to the first conference, and the second access request includes a second digital certificate.
[0042] In one possible implementation, the identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the ciphertext credential using the public key corresponding to the first digital certificate; the processing module is specifically used to: decrypt the ciphertext credential using the private key corresponding to the public key to obtain a plaintext credential; and apply for a digital certificate from a second certificate authority based on the plaintext credential.
[0043] In one possible implementation, the identity credentials are obtained by encrypting a login password using the public key corresponding to the first digital certificate. The login password is used for the electronic device to log in to the IDP, and the IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate authority.
[0044] In a possible implementation, the first conference is an end-to-end encrypted conference.
[0045] In a possible implementation manner, the identity field of the first digital certificate is used to indicate a user identity or a device identity.
[0046] In a possible implementation, the second certificate authority supports the ACME protocol.
[0047] The fifth aspect of the present application provides a conference server, comprising: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the conference server executes the method of any implementation manner of the above-mentioned first aspect.
[0048] The sixth aspect of the present application provides an electronic device, comprising: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instruction, the electronic device executes the method of any implementation method of the above-mentioned second aspect.
[0049] A seventh aspect of the present application provides a conference system, comprising a conference server as in any implementation of the third aspect and a conference access device as in any implementation of the fourth aspect.
[0050] An eighth aspect of the present application provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on an electronic device, the electronic device can execute any of the methods described above.
[0051] A ninth aspect of the present application provides a computer program product comprising instructions, which, when executed on an electronic device, enables the electronic device to execute any of the methods described above.
[0052] The tenth aspect of the present application provides a chip, which includes a processor and a communication interface, the communication interface is used to communicate with modules outside the chip shown, and the processor is used to run computer programs or instructions so that the device installed with the chip can execute any of the methods described above.
[0053] Among them, the technical effects brought about by any design method from the second aspect to the tenth aspect can refer to the technical effects brought about by different implementation methods in the above-mentioned first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0054] Figure 1 A conference access solution based on E2EE is provided for the embodiment of the present application;
[0055] Figure 2 A schematic diagram of an application scenario provided in an embodiment of the present application;
[0056] Figure 3 A schematic diagram of the structure of an electronic device 301 provided in an embodiment of the present application;
[0057] Figure 4 A flowchart of a conference access method provided in an embodiment of the present application;
[0058] Figure 5 A schematic diagram of the structure of a certificate chain provided in an embodiment of the present application;
[0059] Figure 6 A schematic diagram of a process for an electronic device to apply for a digital certificate from a second certificate issuing authority provided in an embodiment of the present application;
[0060] Figure 7 A schematic diagram of an application architecture of a conference access method provided in an embodiment of the present application;
[0061] Figure 8 A schematic diagram of a process of accessing an E2EE conference provided in an embodiment of the present application;
[0062] Fig. 9 An example diagram of a digital certificate-based conference access provided in an embodiment of the present application;
[0063] Fig.10 A schematic diagram of the structure of a conference server provided in an embodiment of the present application;
[0064] Fig.11 A schematic diagram of the structure of a conference access device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0065] In order to make the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application are described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only embodiments of a part of the present application, rather than all embodiments. It is known to those of ordinary skill in the art that with the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0066] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the descriptions used in this way can be interchanged where appropriate, so that the embodiments can be implemented in a sequence other than that illustrated or described in the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or modules is not necessarily limited to those steps or modules that are clearly listed, but may include other steps or modules that are not clearly listed or inherent to these processes, methods, products or devices. The naming or numbering of the steps that appear in the present application does not mean that the steps in the method flow must be executed in the time / logical sequence indicated by the naming or numbering. The process steps that have been named or numbered can change the execution order according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved. The division of units in this application is a logical division. There may be other division methods when it is implemented in actual applications. For example, multiple units can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection between units can be electrical or other similar forms, which are not limited in this application. In addition, the units or sub-units described as separate components may or may not be physically separated, may or may not be physical units, or may be distributed in multiple circuit units, and some or all of the units may be selected according to actual needs to achieve the purpose of the present application.
[0067] To facilitate understanding, the technical terms involved in the embodiments of the present application are first introduced below.
[0068] (1) Digital Certificate
[0069] A digital certificate, often referred to as a certificate, is a digital certification that marks the identity information of the communicating parties in Internet communications. It is essentially an electronic file that uniquely identifies people and resources. A digital certificate enables secure and confidential communication between two entities.
[0070] Generally speaking, a digital certificate includes a public key, a name, and a digital signature of the CA, where the name can be used to indicate the identity of the user or device applying for the digital certificate.
[0071] (2) Certificate Authority (CA)
[0072] CA is an institution that issues digital certificates. Specifically, CA is an authority responsible for issuing and managing digital certificates, and as a trusted third party in e-commerce transactions, it is responsible for verifying the legitimacy of public keys in the public key system.
[0073] (3) Public Key Infrastructure (PKI)
[0074] Public key infrastructure is a collection of hardware, software, personnel, policies and procedures used to implement functions such as the generation, management, storage, distribution and revocation of keys and certificates based on public key cryptography.
[0075] The PKI system is a combination of computer hardware and software, authoritative institutions and application systems. It provides basic security services for the implementation of e-commerce, e-government, office automation, etc., so that users who do not know each other or are far away can communicate safely through the trust chain.
[0076] (4) Order
[0077] An order is a certificate application object defined in the Automatic Certificate Management Environment protocol. In the ACME protocol, an order represents a user's certificate application request for a digital certificate and is used to track the processing progress of the certificate application request until the digital certificate is issued. In the ACME automatic certificate management environment, the ACME client will send a certificate application request to the ACME server. After confirming the ACME client's certificate application request, the ACME server will create an order for the certificate application request to track the certificate application process. The order contains information about the digital certificate applied for, the authorization required to apply for the digital certificate, and other information.
[0078] (5) Identifier
[0079] The identifier is a field defined in the ACME protocol that identifies the identity represented by the certificate application. The identifier in the order is consistent with the Common Name (CN) field in the last issued digital certificate, indicating the identity represented by the requested certificate. An identifier is an object with two fields, type and value. Identifiers usually need to be unique to distinguish different identities. The type of identifier can be a domain name, email address, or IP address, etc.
[0080] (6) Authorization Object
[0081] Authorization refers to an identity or proof of authorization object defined in the ACME protocol. An ACME authorization object represents the server's authorization of an account to represent an identifier (such as a domain name).
[0082] (7) Challenge
[0083] In the ACME protocol, a challenge is a way for the ACME server to verify that the ACME client has control over the identifier. Each challenge belongs to a specific authorization, and there may be multiple challenge objects under one authorization.
[0084] (8) Token
[0085] In some cases, some types of ACME challenge objects contain a token to identify the uniqueness of the challenge. The token is randomly generated when the challenge is created, and different challenges have different token values. Some types of challenge objects do not distinguish uniqueness through tokens, so tokens may not exist in some types of challenge objects.
[0086] (9)Key Authorization
[0087] The key authorization is a field used to confirm the consistency of the challenge between the ACME client and the ACME server. The key authorization is composed of a random token in the challenge object and the private key of the certificate applicant in a certain way, which can indicate the corresponding challenge object and the identity of the certificate applicant.
[0088] (10) Authenticated Key Exchange (AKE) protocol
[0089] The authenticated key agreement protocol is an important research direction in the field of cryptography. It means that in the presence of an active attacker, two or more users generate a secret value in a certain way to achieve secure communication between them.
[0090] (11) Password-authenticated Key Exchange (PAKE) protocol
[0091] Password authenticated key exchange is an interactive method for two or more parties to establish cryptographic keys based on one or more parties' knowledge of a password. The two or more parties use message exchanges to establish encryption keys based solely on their knowledge of a shared password, so that unauthorized parties (who control the communication channel but do not have the password) cannot participate in the method and brute force password guessing is limited as much as possible, allowing users and servers to efficiently negotiate a secure key starting from a shared low-entropy password.
[0092] (12) Asymmetric Password Authenticated KeyExchange (aPAKE) Protocol
[0093] Passwords are usually simple and easy to remember, while keys are usually complex and difficult to remember. The Password Authenticated Key Exchange (PAKE) protocol allows both parties to convert the local low-entropy password into a high-entropy key and then communicate, so that eavesdroppers or middlemen cannot obtain enough information to brute-force guess the password. This means that weak passwords can be used to achieve strong security. However, traditional password authentication requires storage on the server side, or the plain text password must be transmitted to the server during authentication.
[0094] Therefore, the aPAKE protocol proposes that by establishing a mapping relationship between passwords and keys, authentication can be completed without the communication party knowing the plaintext password in advance. However, if the mapping relationship between passwords and keys is certain, or only uncertainty is provided by plaintext random salt, attackers can calculate the password based on the key through pre-calculation, so the aPAKE protocol cannot provide stronger security than the PAKE protocol.
[0095] (13)Opaque Protocol
[0096] The Opaque protocol is an asymmetric password-authenticated key exchange protocol that can prevent pre-computation attacks. Through the Opaque protocol, user keys can be stored on the server side, and identity authentication can be completed without leaving the local password, thus ensuring that neither the server nor the communication operator can obtain or crack it. By combining the oblivious pseudorandom function (OPRF) with the aPAKE protocol, a method that can resist pre-computation attacks is provided.
[0097] (14) Public key and private key
[0098] The public key is short for public key and is the non-secret half of a key pair used with a private key algorithm. The public key is typically used to encrypt session keys, verify digital signatures, or encrypt data that can be decrypted with the corresponding private key.
[0099] A private key is short for private key and is the secret half of a key pair used with a public key algorithm.
[0100] The public key and private key are a key pair (i.e., a public key and a private key) obtained through an algorithm. One of them is open to the outside world, called the public key; the other is kept by oneself, called the private key. The key pair obtained through this algorithm can be guaranteed to be unique worldwide. When using this key pair, if one of the keys is used to encrypt a piece of data, the other key must be used to decrypt it. If the data is encrypted with the public key, it must be decrypted with the private key. If it is encrypted with the private key, it must also be decrypted with the public key, otherwise the decryption will not be successful.
[0101] (15) Certificate Signing Request (CSR)
[0102] CSR is essentially a block of coded text that a certificate applicant sends to a CA when applying for a digital certificate. CSR generally includes two types of information: one is the relevant identity information of the certificate applicant, and the other is the public key required to be included in the digital certificate. Among them, the relevant identity information of the certificate applicant includes, for example, the following information.
[0103] Common Name (CN): It can be the domain name of the server, such as www.xxxx.com.
[0104] Organization Name: The legal name of the organization, for example "xxxx Co., Ltd."
[0105] Organizational Unit: A department of an organization, such as the IT department.
[0106] City / Location: The city where the organization is located.
[0107] State / County / Region: The specific region where the organization is located, such as Beijing / Shandong.
[0108] Country: The country where the organization is located, such as China.
[0109] Email Address: The email address used to contact the organization.
[0110] (16) Key exchange algorithm (Diffie-Hellman, DH)
[0111] The key exchange algorithm is a public key algorithm, which means that the communicating parties calculate the shared key by exchanging some data without transmitting the key.
[0112] (17) End-to-end encryption
[0113] End-to-end encryption is a method of encrypted communication in which only the communicating users can read the messages. In principle, end-to-end encryption protects against potential eavesdroppers - including telecom providers, internet providers, malicious state agencies, and even communication service providers. In end-to-end encryption, each user has a public-private key pair. Here's an example: suppose Alice and Bob generate a public-private key pair on their phones or computers when they create their accounts, where their public key is stored on the server and their private key is stored on the device. Alice wants to send Bob an encrypted message, and Alice encrypts Alice's message to Bob using Bob's public key. Then, when Bob receives the message, Bob decrypts Alice's message using the private key on his device. When Bob wants to reply, he simply repeats the process, encrypting Bob's message to Alice using Alice's public key.
[0114] (18) Virtual Meeting Room (VMR)
[0115] A virtual conference room is an efficient, convenient, and low-cost network conference room based on the Internet and cloud computing. Users can quickly and efficiently transmit voice, video, and data files with users around the world through mobile products such as mobile phones and computers. Using a virtual conference room can easily enjoy a simple, convenient, and efficient communication experience, freeing you from the limitations of time, space, and location. This is a major advantage of video conferencing compared to traditional physical conference rooms.
[0116] In simple terms, instead of being in the same physical space, team members participating in a meeting join the same virtual space through their mobile devices, laptops or desktops, connected with microphones and cameras. No matter where someone is, as long as they have a device with an internet connection, they can dial into the virtual meeting room and discuss ideas and agendas with others.
[0117] At present, related technologies have proposed conference access solutions based on identity authentication, such as conference access solutions based on E2EE. Figure 1 , Figure 1 An E2EE-based conference access solution is provided for the embodiment of the present application. Figure 1 In the E2EE-based conference access solution shown, in addition to the participants, a public key authentication server is also required. In addition, the participant accessing the conference includes the following multiple steps.
[0118] Step A: elect a conference host, and have the conference host randomly generate a conference security key mk.
[0119] For example, in Figure 1 In the meeting, the meeting host is Alice, and the participants include Bob and Carol.
[0120] Step B, each participant generates a long-term signing key pair (sk Sig ,pk Sig ), where sk Sig is the public key, pk Sig And, after the participant passes the identity authentication on the public key authentication server (for example, identity authentication is performed based on a digital certificate), the participant will generate the public key pk Sig Upload to the public key authentication server and broadcast it through the public key authentication server.
[0121] like Figure 1 As shown, the signature key pair generated by the conference host Alice is (sk A Sig ,pk A Sig ), the signature key pair generated by participant Bob is (sk B Sig ,pk B Sig ), the signature key pair generated by participant Carol is (sk C Sig ,pk C Sig The public key authentication server stores the public key of the signature key pair uploaded by each participant, that is, pk A Sig , pk B Sig , pk C Sig .
[0122] Step C: Each participant generates a temporary key pair (sk Enc , pk Enc ), and use the public key sk in the signing key pair Sig Sign the public key pk in the temporary key pair Enc , and broadcast the public key pk in the temporary key pair through the public key authentication server Enc and its signature.
[0123] like Figure 1 As shown, the signature key pair generated by the conference host Alice is (sk A Enc ,pk A Enc ), the signature key pair generated by participant Bob is (sk B Enc ,pk B Enc ), the signature key pair generated by participant Carol is (skC Enc ,pk C Enc The public key authentication server stores the public key of the signature key pair uploaded by each participant, that is, pk A Enc , pk B Enc , pk C Enc .
[0124] Step D: After the public key authentication server broadcasts, each participant has the public key pk in the signature key pair of other participants. Sig and the public key pk in the temporary key pair A Enc Therefore, each participant can first use the public key pk in the signature key pair Sig Verify the public key pk in the temporary key pair A Enc If the authenticity of the public key pkEnc in the temporary key pair is verified to be legitimate, any two participants can negotiate the pairing key pairk through the key exchange algorithm. i,j =DH(ski Enc ,pkj Enc ).
[0125] Step E: The conference host uses the pairing key pairki,j to encrypt the conference key mk and obtain the ciphertext C i,j =Enc(pairki,j,mk) and send them to the corresponding participants respectively.
[0126] However, the E2EE-based conference access solution brings about restrictions on secure access in cross-domain scenarios. In cross-domain scenarios, digital certificates used to represent identities in different domains are usually issued by different certificate authorities (CA). Due to the non-interoperability between different CAs, it is impossible to achieve identity mutual trust based on digital certificates in cross-domain scenarios, which makes it impossible for conference hosts to perform identity authentication with cross-domain external participants, which in turn makes it impossible for cross-domain external participants to access the conference.
[0127] For example, in Figure 1 In the solution based on the public key authentication server shown, since the cross-domain external users hold digital certificates issued by other CAs, the cross-domain external users have no way to add a trusted long-term signature key pair in the public key authentication server, resulting in the cross-domain external users being unable to subsequently obtain the qualification to access the meeting by interacting with the conference host through the end-to-end encryption solution.
[0128] In view of this, the present application provides a conference access method. In a cross-domain scenario, by pre-adding a trusted external root certificate, the digital certificate of the external participant can be verified based on the trusted root certificate. And for the external participant who has passed the digital certificate verification, a temporary identity credential is issued to the external participant, so that the external participant can apply for a digital certificate from the internal trusted CA based on the temporary identity credential, and then the external participant can also hold a digital certificate issued by the trusted CA, ensuring that the external participant can access the conference through identity authentication.
[0129] See also Figure 2 , Figure 2 The following is a schematic diagram of an application scenario provided by an embodiment of the present application. Figure 2 As shown, the application scenario of the conference access method provided by the embodiment of the present application includes a conference server, an internal CA, an external participant device, an external CA and an IDP. Among them, the conference server and the internal CA belong to the same domain, for example, the network domain of the same company, while the external participant device and the external CA belong to other domains, for example, the network domain of an external company. In addition, the IDP is a device trusted by the conference server and the internal CA. The IDP can be located in the same domain as the conference server and the internal CA, or in a different domain.
[0130] exist Figure 2 In the application scenario shown, the external CA first issues a digital certificate 1 to the external participant device.
[0131] The external participant device sends a conference access request 1 to the conference server, and carries a digital certificate 1 in the conference access request 1 to request to access the conference.
[0132] The conference server verifies the digital certificate 1. If the digital certificate 1 passes the verification, the conference server returns the identity credentials to the external conference participant device.
[0133] Based on the identity credentials returned by the conference server, the external participating device performs identity authentication through the IDP to facilitate the application of a digital certificate from the internal CA.
[0134] After the external participant device passes the identity authentication, the IDP feeds back the identity authentication result to the internal CA, so that the internal CA issues a digital certificate 2 to the external participant device.
[0135] Finally, the external participant device sends a conference access request 2 to the conference server, and carries a digital certificate 2 issued by the internal CA in the conference access request 2 to request access to the conference. Since the digital certificate 2 carried by the external participant device is issued by the internal CA trusted by the conference server, the conference server allows the external participant device to access the conference.
[0136] In this embodiment, the external participating device may be, for example, an electronic device such as a smart phone, a personal computer, a laptop, a tablet computer, a server, etc., the conference server may be, for example, a physical device such as a server or a virtual device such as a virtual machine running on the server, and the IDP may be, for example, a physical device such as a server or a virtual device such as a virtual machine running on the server.
[0137] See also Figure 3 , Figure 3 This is a schematic diagram of the structure of an electronic device 301 provided in an embodiment of the present application. Figure 3 The electronic device 301 shown in the figure may be the external conference participant device or conference server mentioned above.
[0138] like Figure 3 As shown, the electronic device 301 includes a processor 303, and the processor 303 is coupled to a system bus 305. The processor 303 can be one or more processors, each of which can include one or more processor cores. A display adapter (video adapter) 307 can drive a display 309, and the display 309 is coupled to the system bus 305. The system bus 305 is coupled to an input / output (I / O) bus via a bus bridge 311. An I / O interface 315 is coupled to the I / O bus. The I / O interface 315 communicates with a variety of I / O devices, such as an input device 317 (such as a touch screen, etc.), an external memory 321 (for example, a hard disk, a floppy disk, an optical disk or a USB flash drive), a multimedia interface, etc.), a transceiver 323 (which can send and / or receive radio communication signals), a camera 355 (which can capture static and dynamic digital video images) and an external USB port 325. Optionally, the interface connected to the I / O interface 315 can be a USB interface.
[0139] The processor 303 may be any conventional processor, including a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, or a combination thereof. Alternatively, the processor may be a dedicated device such as an ASIC.
[0140] The electronic device 301 can communicate with other electronic devices through the network interface 329 to achieve data transmission during the screen projection process.
[0141] The processor 303 can communicate with the memory 335 through the system bus 305, and fetch instructions and data in the application program from the memory 335, thereby implementing the execution of the program.
[0142] See also Figure 4 , Figure 4 A flowchart of a conference access method provided in an embodiment of the present application. Figure 4 As shown, the conference access method includes the following steps 401-405.
[0143] Step 401: The electronic device sends a first access request to a conference server. The first access request is used to request access to a first conference, and the first access request includes a first digital certificate. The first digital certificate is issued by a first certificate issuing authority.
[0144] In this embodiment, the electronic device is an external participant device that needs to access the conference. The conference server is a server that provides conference management services. For example, the conference server is a server inside enterprise A that provides conference services, and the electronic device is a device of a user in enterprise B, a cooperative enterprise of enterprise A. In addition, the user inside enterprise A has reserved a conference with external enterprise members through the conference server, so the user in enterprise B needs to access the conference held by enterprise A through the electronic device.
[0145] In the process of sending a first access request to the conference server, the electronic device may carry a first digital certificate for characterizing the identity of the electronic device in the first access request, so that the conference server can identify the identity of the electronic device. The first digital certificate is issued by a first certificate authority that the conference server does not trust. For example, when the conference server belongs to enterprise A and the electronic device belongs to enterprise B, the first certificate authority may be a private institution of enterprise B, so the conference server does not trust the first certificate authority.
[0146] Optionally, before the electronic device sends the first access request to the conference server, the electronic device can obtain the conference link sent by the conference server, and then send the first access request to the conference server based on the conference link. Specifically, when creating the first conference, the conference server determines the participants who need to attend the conference based on the user's conference creation instruction, and then after successfully creating the first conference, sends the conference link corresponding to the created first conference to each participant. In this way, after receiving the conference link, the external participant can access the conference link on the electronic device to trigger the sending of the first access request to the conference server.
[0147] Optionally, the identity field of the first digital certificate is used to indicate the user identity or the device identity. That is, the field used to represent the identity in the first digital certificate (such as the common name field) can indicate the identity of the user or the identity of the device, that is, the identity corresponding to the first digital certificate is not limited to the user, but can also be the device. For example, the common name field in the first digital certificate can include but is not limited to the following identities: the user's mobile phone number, the user's email address, the session initiation protocol number, the universally unique identifier (UUID), the Internet Protocol address, the domain name, and the device unique identifier, etc.
[0148] Step 402: Based on a preset trust policy, the conference server verifies the first digital certificate. The preset trust policy is used to indicate a trusted certificate list, and the certificate list includes a root certificate corresponding to the first digital certificate.
[0149] In this embodiment, the conference server is pre-configured with a preset trust policy so that the conference server can verify the external digital certificate. In addition, the preset trust policy is used to indicate a trusted certificate list, that is, a list of trusted digital certificates, and the certificate list includes the root certificate corresponding to the first digital certificate.
[0150] Generally speaking, verifying a digital certificate actually requires verifying the entire certificate chain to which the digital certificate belongs. Figure 5 , Figure 5 A schematic diagram of the structure of a certificate chain provided in an embodiment of the present application. Figure 5 As shown, in the certificate chain, there are usually three levels of institutions, including a root certificate, an intermediate certificate, and an enterprise private certificate (such as a server certificate). Among them, the enterprise private certificate is at the bottom of the certificate chain, and the enterprise private certificate can specifically include the enterprise name, public key, certificate issuer, and digital signature. The digital signature of the enterprise private certificate is obtained by signing the certificate issuer of the enterprise private certificate (i.e., the intermediate certificate). The upper level of the enterprise private certificate is the intermediate certificate, which is the issuer of the enterprise private certificate, and the intermediate certificate specifically includes the intermediate certificate name, public key, certificate issuer, and digital signature. The digital signature of the intermediate certificate is obtained by signing the certificate issuer of the intermediate certificate (i.e., the root certificate). The upper level of the intermediate certificate is the root certificate, which is the issuer of the intermediate certificate, and the root certificate specifically includes the certificate authority name, public key, and digital signature of the root certificate, wherein the digital signature of the root certificate can be a self-signed value.
[0151] In verification Figure 5In the process of verifying the enterprise private certificate shown in , it is necessary to verify the digital signature of each digital certificate in the certificate chain from bottom to top, that is, use the public key of the previous digital certificate to verify the digital signature of the next digital certificate. Since the certificate issuer uses its own private key to sign the next digital certificate and obtain the digital signature of the next digital certificate, the public key of the previous digital certificate can be used to verify whether the digital signature of the next digital certificate is correct during the verification process. In general, the process of verifying the certificate chain is iterative signature verification, starting from the bottom level of the certificate chain, and verifying the digital signature in the certificate level by level. Since the issuers of digital certificates at other levels except the root certificate are all users of the previous digital certificate, the root certificate is actually the trusted starting point of the entire certificate chain. For the verification of all digital certificates, it is ultimately necessary to verify the validity of the root certificate corresponding to the digital certificate.
[0152] Therefore, in this implementation, trust in the root certificate corresponding to the first digital certificate is added to the preset trust policy, and the verification of the first digital certificate can be completed according to the verification steps of the digital certificate, thereby realizing the identification and trust of external identities in cross-domain scenarios.
[0153] It should be noted that Figure 5 The certificate chain shown is an example of this embodiment. In practical applications, the first digital certificate can be a certificate directly issued by a root certificate. There can also be one or more intermediate certificates between the first digital certificate and the root certificate, which is not specifically limited in this embodiment.
[0154] Optionally, the preset trust policy is also used to indicate the conference access rights of one or more objects. For example, assuming that the external enterprise is an enterprise that cooperates with the R&D department of the enterprise, the preset trust policy can indicate that members of external enterprise B can only access meetings held by the R&D department of the enterprise, that is, the types of meetings that participants belonging to external enterprise B can access are meetings held by the R&D department of the enterprise.
[0155] Then, in the process of verifying the first digital certificate, the conference server can determine the conference access rights of the applicant of the first digital certificate based on the preset trust policy; and, based on the type of conference requested to be joined by the first access request and the conference access rights of the applicant, determine whether the applicant has the right to access the first conference; wherein, the condition for the first digital certificate to pass the verification includes that the applicant of the first digital certificate has the right to access the first conference. That is, if the applicant of the first digital certificate does not have the right to access the first conference, the first digital certificate cannot pass the verification. In other words, the verification process of the first digital certificate actually includes the verification of the conference access rights of the applicant of the first digital certificate in addition to the conventional digital certificate verification process.
[0156] In general, by specifying the conference access rights of participants in the preset trust policy, it can be ensured that only participants with access rights to the current meeting can pass the identity authentication during conference access, avoiding other unrelated participants from accessing the meeting due to the conference host's incorrect specification of participants or incorrect distribution of conference links, thereby improving the security of conference access.
[0157] Step 403: In response to the first digital certificate passing verification, the conference server sends an identity credential to the electronic device. The identity credential is used by the electronic device to apply for a digital certificate from a second certificate issuing authority, and the second certificate issuing authority is a trusted authority.
[0158] After the first digital certificate passes the verification, the conference server can consider the identity of the electronic device to be credible. Therefore, in order to ensure that the electronic device can replace the membership certificate with a digital certificate issued by an internally trusted second certificate authority, the conference server sends a temporary identity credential to the electronic device so that the electronic device can apply for a digital certificate from the second certificate authority based on the identity credential. For example, if the conference server belongs to enterprise A, the second certificate authority may also belong to enterprise A, so the conference server trusts the second certificate authority.
[0159] Step 404: The electronic device applies for a second digital certificate from a second certificate issuing authority based on the identity credentials.
[0160] The identity credentials sent by the conference server to the electronic device are used to represent the trusted identity of the electronic device, so that the electronic device can pass the identity authentication process in the process of applying for a digital certificate based on the identity credentials. In this way, based on the identity credentials, the electronic device can apply for a second digital certificate from the second certificate authority. That is, the second digital certificate is issued by the second certificate authority trusted by the conference server.
[0161] Optionally, the second certificate issuing authority may support the ACME protocol, so that the second certificate issuing authority can automatically issue the second digital certificate to the electronic device based on the ACME protocol, thereby improving the efficiency of the digital certificate application process.
[0162] Step 405: The conference server obtains a second access request sent by the electronic device and allows the electronic device to access the first conference, where the second access request is used to request access to the first conference and includes a second digital certificate.
[0163] After acquiring the second digital certificate issued by the second certificate issuing authority, the electronic device re-applies to the conference server for access to the first conference, that is, sends a second access request to the conference server and carries the second digital certificate in the second access request.
[0164] Since the second digital certificate carried by the electronic device in the second access request is issued by a trusted internal certificate authority (ie, the second certificate authority), the electronic device can pass the identity authentication for accessing the conference and is then allowed by the conference server to access the first conference.
[0165] It should be noted that the identity authentication process for the electronic device to access the first conference based on the second digital certificate may be determined based on the type of the first conference, and this embodiment does not specifically limit this. For example, in the case where the first conference is an end-to-end encrypted conference, the identity authentication process for the electronic device to access the first conference may be as follows: Figure 1 The process of authenticating the server based on a public key is shown.
[0166] In addition, when the first conference is an end-to-end encrypted conference, since the end-to-end encrypted conference requires the conference system to uniformly verify the identity of the devices accessing the conference, and the two devices accessing the conference also need to end-to-end verify the identity of the other device, this solution implements the identity authentication of the external participating devices by adding a trusted root certificate to the conference server, and sends identity credentials to the external participating devices to trigger the external participating devices to replace the membership certificate with a digital certificate issued by the trusted internal certificate authority, thereby ensuring that the external participating devices can smoothly interact with any device in the end-to-end encrypted conference based on the replaced digital certificate (that is, any two devices in the end-to-end encrypted conference will also use digital certificates to verify each other's identities when interacting), ensuring that the external participating devices can successfully pass identity authentication in conference scenarios using digital certificates as end-to-end identity authentication credentials.
[0167] Furthermore, when the first conference is an end-to-end encrypted conference, trust in external participating devices and replacement of digital certificates of external participating devices is achieved by adding a trusted root certificate on the conference server. This avoids the complicated process of adding a trusted root certificate on each participating device, so that each participating device can still interact based on mutually trusted digital certificates, reducing the impact of external participating devices joining the conference on each internal participating device.
[0168] Optionally, in the above step 403, the identity credentials sent by the conference server to the electronic device are ciphertext credentials, and the ciphertext credentials are obtained by encrypting the public key corresponding to the first digital certificate. Therefore, after receiving the ciphertext credentials, the electronic device can use the private key corresponding to the public key of the first digital certificate to decrypt the ciphertext credentials and obtain the plaintext credentials; then, the electronic device applies for a digital certificate from the second certificate authority based on the plaintext credentials. Obviously, if the electronic device is not the real holder of the first digital certificate, the electronic device does not have the private key corresponding to the first digital certificate, and thus cannot decrypt the ciphertext credentials.
[0169] By using the public key of the first digital certificate to encrypt the ciphertext credentials by the conference server, the electronic device needs to use the private key corresponding to the public key of the first digital certificate to execute the ciphertext credentials, thereby verifying whether the electronic device has control over the private key corresponding to the first digital certificate, avoiding the electronic device from using other people's digital certificates to access the conference, and further improving the security of conference access.
[0170] For example, when the electronic device applies for a digital certificate from the second certificate authority and the identity authentication is performed through the IDP, the identity credentials sent by the conference server to the electronic device are obtained by encrypting the login password using the public key corresponding to the first digital certificate, and the login password is used for the electronic device to log in to the IDP. The IDP is used to provide identity authentication services for the electronic device when the electronic device applies for a digital certificate from the second certificate authority.
[0171] For example, see Figure 6 , Figure 6 A schematic diagram of a process for an electronic device to apply for a digital certificate from a second certificate issuing authority provided in an embodiment of the present application. Figure 6 As shown, the above step 404 may specifically include the following steps 4041-4047.
[0172] In step 4041, the electronic device uses the private key corresponding to the public key of the first digital certificate to decrypt the identity credentials and obtain the login password.
[0173] Since the electronic device is the actual holder of the first digital certificate, the private key corresponding to the public key of the first digital certificate is stored on the electronic device, so the identity credentials can be decrypted based on the private key to obtain the login password.
[0174] Step 4042: The electronic device logs in to the IDP using the login password, and activates the temporary conference identity pre-created for the electronic device on the IDP.
[0175] In this embodiment, while the conference server sends the identity credentials to the electronic device, the conference server may also send the address of the IDP to the electronic device to instruct the electronic device to log in to the IDP to activate the temporary identity of the conference. Specifically, the conference server may send an identity activation request to the electronic device, the identity activation request including the identity credentials and the address of the IDP, and the identity activation request is used to request the electronic device to activate the temporary identity of the conference created on the IDP through the identity credentials.
[0176] A temporary conference identity is created in advance on the IDP for the participants of the first conference. When the electronic device logs in to the IDP using the login password, the temporary conference identity created in advance for the electronic device on the IDP can be activated, so that the electronic device can subsequently apply for a digital certificate from the second certificate authority based on the temporary conference identity.
[0177] After activating the temporary conference identity on the IDP, it is often necessary to regenerate the corresponding public key and private key for the activated temporary conference identity so that identity authentication services can be provided for the subsequent certificate application process. There are many ways to generate the public key and private key, and the specific examples are shown below.
[0178] Mode 1: reuse the public key and private key corresponding to the first digital certificate held by the electronic device. In this case, the electronic device can transmit the public key corresponding to the first digital certificate to the IDP so that the IDP can record the mapping relationship between the temporary conference identity and the public key.
[0179] Method 2: The electronic device regenerates a new public key and private key, and transmits the regenerated public key to the IDP.
[0180] Method 3: In the supervision scenario, the internal meeting requires the public key and private key of the external user to be specified. In this case, the conference server generates the public key and private key and sends the generated public key and private key to the electronic device. In addition, the conference server can also send the generated public key and private key to the IDP, or the conference server only sends the generated public key to the IDP.
[0181] Step 4043: The electronic device sends a certificate application request to the second certificate authority.
[0182] The second certificate issuing authority is a certificate issuing authority trusted by the conference server. The certificate application request sent by the electronic device is used to request the second certificate issuing authority to issue a digital certificate to the electronic device.
[0183] Step 4044: The second certificate authority returns the IDP information to the electronic device to instruct the electronic device to perform identity authentication through the IDP.
[0184] In this embodiment, the IDP is trusted by the second certificate authority and provides identity authentication services for the second certificate authority. Therefore, after receiving the certificate application request from the electronic device, the second certificate authority instructs the electronic device to perform identity authentication through the IDP first.
[0185] Step 4045, the electronic device logs in to the IDP and cooperates with the IDP to perform identity authentication.
[0186] Since the IDP stores the conference temporary identity and public key corresponding to the electronic device, and the electronic device stores the corresponding public key and private key, after logging into the IDP, the electronic device can cooperate with the IDP to perform identity authentication, thereby verifying that the electronic device does correspond to the conference temporary identity recorded in the IDP. For example, after the electronic device logs into the IDP based on the conference temporary identity, the IDP can authenticate the electronic device by verifying whether the electronic device has the private key of the conference temporary identity.
[0187] Optionally, when the second certificate authority supports the ACME protocol, the electronic device can implement the application for the digital certificate based on the process in the ACME protocol. In addition, the process of the electronic device performing identity authentication on the IDP is actually the process of the electronic device carrying out a challenge based on the requirements of the ACME protocol. In other words, the way the electronic device performs identity authentication on the IDP supports various types of challenges under the ACME protocol. For details, please refer to the challenges defined under the ACME protocol, which will not be repeated here.
[0188] Among them, the IDP can support the aPAKE protocol or the Opaque protocol, which can effectively ensure the security of the electronic device during the identity authentication process.
[0189] Step 4046, the IDP returns the identity authentication result to the second certificate authority.
[0190] After the electronic device completes the identity authentication process through the IDP, the IDP returns the identity authentication result of the electronic device to the second certificate issuing authority to indicate whether the electronic device has passed the identity authentication.
[0191] Step 4047: The second certificate issuing authority issues a second digital certificate to the electronic device.
[0192] When the electronic device passes the identity authentication, the second certificate issuing authority issues a second digital certificate to the electronic device so that the electronic device can hold a digital certificate trusted by the conference server and other participating devices.
[0193] Optionally, in the above embodiment, since the conference server needs to obtain a valid login password before encrypting the login password with a public key and then sending it to the electronic device, in this embodiment, the conference server may interact with the IDP to obtain the login password during the conference creation stage.
[0194] Exemplarily, the conference server receives a conference creation instruction, and creates a first conference based on the conference creation instruction. The conference creation instruction may be issued by the conference organizer to the conference server, and is used to instruct the conference server to create the first conference. In addition, the conference creation instruction is also used to indicate the attendees corresponding to the first conference, and the attendees include the applicant of the first digital certificate. The conference creation instruction may include an identity identifier of the applicant of the first digital certificate, and the identity identifier is the same as the identity identifier in the first digital certificate, such as an identifier such as a mobile phone number or an email address of the applicant of the first digital certificate.
[0195] Then, the conference server sends a temporary identity creation request to the IDP, which is used to instruct the IDP to create a temporary conference identity for the participant. Optionally, the temporary identity creation request can also indicate the validity period of the temporary identity created for the participant. For example, the temporary identity is only valid during the duration of the first conference. In this way, the participant can only apply for a digital certificate from the second certificate authority through the temporary identity during the duration of the first conference, thereby ensuring the security of conference access.
[0196] Based on the temporary identity creation request sent by the conference server, the IDP creates a temporary conference identity for the participant and generates a login password corresponding to each temporary identity. After completing the creation of the temporary identity, the IDP interacts with the conference server, and the conference server generates a login password corresponding to the temporary identity, which is used to decrypt the private key corresponding to the temporary identity generated by the IDP. In this way, after the first digital certificate of the electronic device passes the verification, the conference server can send the login password corresponding to the temporary identity of the electronic device to the electronic device, so that the electronic device can pass the identity authentication of the IDP based on the login password, and then apply to the second certificate authority for a digital certificate.
[0197] Optionally, in some scenarios, due to the special identities of external participants, the meeting organizer may wish to limit the permissions of external participants in the meeting. For example, external participants cannot have recording permissions, file modification permissions, file download permissions, etc., to prevent external participants from leaking sensitive content within the company.
[0198] In this case, the conference creation instruction obtained by the conference server is also used to indicate the operation permissions of the participants in the conference. The operation permissions of different participants in the conference may be different, that is, the conference creation instruction may indicate the specific operation permissions of each participant in the conference. For example, participants within the enterprise have all operation permissions in the conference; while participants outside the enterprise only have the right to speak and the right to view shared content in the conference.
[0199] In this way, after allowing the electronic device to access the first meeting, the conference server can determine the participant corresponding to the electronic device based on the application identity corresponding to the second digital certificate, and then set the operating permissions of the electronic device in the first meeting to ensure that the operating permissions of the electronic device in the first meeting are in line with the content indicated by the meeting creation instruction.
[0200] In this solution, when the conference server obtains a conference creation instruction indicating the operating permissions of each participant in the conference, the conference server sets the operating permissions of the participant in the conference after allowing the participant to join the conference, thereby implementing permission management of the participant and improving security during the meeting.
[0201] A conference access method provided in an embodiment of the present application is introduced above. For ease of understanding, the execution process of the conference access method will be described in detail below with reference to specific examples.
[0202] For example, see Figure 7 , Figure 7 A schematic diagram of the application architecture of a conference access method provided in an embodiment of the present application. Figure 7 As shown, in the application architecture, each conference participant interacts with the conference server through their own electronic devices to access the conference. Among them, a conference application server is deployed on the conference server, which can provide users with conference functions such as conference creation and conference access.
[0203] During the conference creation phase, conference organizer A accesses the conference application service on the conference server through his electronic device and issues a conference creation instruction to the conference application service to create a conference. After receiving the conference creation instruction issued by conference organizer A, the conference application service allocates virtual conference room resources for the conference reserved by conference organizer A to complete the creation of the conference.
[0204] In addition, when the conference organizer A instructs the conference application service to create a conference, the conference organizer A can specify the participants of the conference. In this way, after successfully creating the conference, the conference application service can send an email to each conference participant (for example, Figure 7 The conference notification is sent to the conference participant B, the conference participant C, and the participant sharing a common device shown in FIG. 1 , so that each conference participant can access the conference based on the conference link indicated in the conference notification.
[0205] When each conference participant joins the conference, the conference application service can verify the identity of each conference participant and allow the conference participant to join the conference after the identity of the conference participant is verified. After each conference participant joins the conference, voice, video, file and other data can be exchanged based on the Internet.
[0206] See also Figure 8 , Figure 8 A schematic diagram of a process of accessing an E2EE conference provided in an embodiment of the present application. Figure 8 As shown, the process of accessing an E2EE conference includes the following steps 801-8018. Figure 8 In the process shown, the following devices interact: IDP, certificate authority A, electronic device A, conference server with conference application service deployed, electronic device B and certificate authority B. Among them, IDP, certificate authority A and conference server with conference application server deployed all belong to enterprise A, electronic device A is the device of user Alice, and user Alice is an employee of enterprise A. Certificate authority B belongs to enterprise B, electronic device B is the device of user Bob, and user Bob is an employee of enterprise B.
[0207] also, Figure 8 For the convenience of drawing, the specific step names are not marked.
[0208] Step 801: Certificate authority A issues digital certificate A to electronic device A, and certificate authority B issues digital certificate B to electronic device B.
[0209] Among them, since the certificate issuing authority A is an institution belonging to enterprise A, the identity information of the digital certificate A issued by the certificate issuing structure A to the electronic device A is the identity information of the user Alice of the electronic device A in enterprise A. Similarly, the identity information of the digital certificate B issued by the certificate issuing structure B to the electronic device B is the identity information of the user Bob of the electronic device B in enterprise B.
[0210] For example, see Fig. 9 , Fig. 9 This is an example diagram of a digital certificate-based conference access provided in an embodiment of the present application. Fig. 9 As shown, the digital certificate issued by certificate authority A for user Alice's electronic device A includes the following content: the common name is Alice; the organization is enterprise A; the issuing authority is certificate authority A. The digital certificate issued by certificate authority B for user Bob's electronic device B includes the following content: the common name is Bob; the organization is enterprise B; the issuing authority is certificate authority B.
[0211] Step 802: The conference application service in the conference server receives a conference creation instruction sent by the conference organizer and creates a conference.
[0212] The conference creation instruction received by the conference application service may indicate the participants of the conference to be created, the authority of each participant in the conference, and the duration of the conference.
[0213] Step 803: The conference application service in the conference server sends an identity creation request to the IDP, requesting the IDP to create a temporary conference identity for the conference participants.
[0214] Specifically, the conference application service may be to request the IDP to create a temporary conference identity for each participant in the conference, and the temporary conference identity is used to access the conference created by the conference application service, that is, the identity creation request indicates each participant for which the temporary conference identity is to be created. In addition, the conference application service may indicate the validity period of the created temporary conference identity in the identity creation request, and the validity period may be the same as not exceeding the duration of the conference. For example, the validity period of the temporary conference identity may be the intersection of the duration of the conference and the validity period of digital certificate B, that is, the validity period of the temporary conference identity shall not exceed the duration of the conference and the validity period of digital certificate B.
[0215] In addition, the identity creation request sent by the conference application service can instruct the IDP to create a temporary conference identity corresponding to the current conference for the participant, so that the participant can only access the current conference based on the temporary conference identity, but cannot enter other conferences. In other words, there is a binding relationship between the temporary conference identity and the conference, and the participant cannot access other conferences unrelated to the temporary conference identity based on the temporary conference identity.
[0216] Step 804: After creating a temporary conference identity for the participant, the IDP interacts with the conference application service in the conference server, so that the conference application service generates a login password for each temporary conference identity.
[0217] In this way, for each participant in the conference, the conference application service can obtain the login password of each participant on the IDP.
[0218] Specifically, the process in which the conference application service in the conference server interacts with the IDP to create a temporary conference identity for the participant can be understood as the process in which the conference application service registers the identity for the participant on the IDP. In addition, the conference application service can be a process in which the identity of the participant is registered on the IDP based on the Opaque protocol. Therefore, the specific process in which the conference application service registers the identity of the participant on the IDP can refer to the existing description of the Opaque protocol, and will not be repeated here.
[0219] Step 805: The conference application service in the conference server sends a conference notification to the participants.
[0220] Specifically, the conference application service can send a conference notification to each participant via email, and the conference notification carries a conference link for accessing the conference. In this way, users Alice and Bob, who are participants, can receive the conference notification through their electronic devices and interact with the conference application service based on the conference notification to access the conference.
[0221] Step 806 , electronic device A of user Alice sends a conference access request carrying digital certificate A to the conference application service, and electronic device B of user Bob sends a conference access request carrying digital certificate B to the conference application service.
[0222] For electronic device A, since the digital certificate A carried by electronic device A when requesting to access the conference is issued by the certificate authority A trusted by the conference application service, the conference application service trusts the digital certificate A of electronic device A and can return the login password corresponding to electronic device A to electronic device A. In this way, electronic device A can log in on the IDP based on the login password returned by the conference application service and activate the temporary conference identity created by the IDP for electronic device A. In this way, when the conference application service obtains that the temporary conference identity corresponding to electronic device A is activated on the IDP, it can allow electronic device A to access the conference based on the temporary conference identity.
[0223] For electronic device B, since the digital certificate B carried by electronic device B when requesting to access the conference is not issued by a certificate authority trusted by the conference application service, the conference application service needs to verify the digital certificate B.
[0224] Step 807: The conference application service verifies digital certificate B based on a preset trust policy.
[0225] Among them, the preset trust policy can be added in advance by the user or manager of enterprise A on the conference application service, and the preset trust policy indicates the trusted root certificate. And, because enterprise A trusts enterprise B, the root certificate of enterprise B is added to the preset trust policy. In addition, the preset trust policy can also indicate the conference access rights of different participants. In this way, in the process of verifying digital certificate B by the conference application service, it can be determined whether digital certificate B can pass the verification based on the trusted root certificate indicated in the preset trust policy and the conference access rights of the participants. Only when digital certificate B passes the conventional digital certificate verification and the participant corresponding to digital certificate B has the conference access rights of the current meeting, can it be confirmed that digital certificate B has passed the verification.
[0226] Step 808: After the digital certificate B passes the verification, the conference application service in the conference server uses the public key of the digital certificate B to encrypt the login password of the conference temporary identity corresponding to the user Bob on the IDP to obtain the ciphertext password.
[0227] After the digital certificate B passes the verification, the conference application service can determine the participant identity (ie, user Bob) corresponding to the electronic device B that sent the digital certificate, and then determine the login password of the temporary conference identity corresponding to user Bob on the IDP.
[0228] Step 809: the conference application service in the conference server sends the encrypted password and the address of the IDP to the electronic device B, so as to instruct the electronic device B to decrypt the encrypted password and log in the IDP using the login password obtained after decryption.
[0229] Step 8010, electronic device B uses the private key of digital certificate B to decrypt the ciphertext password and obtain the login password.
[0230] Step 8011, electronic device B logs in to the IDP using the decrypted login password to activate the temporary conference identity of user Bob on the IDP.
[0231] Step 8012: After electronic device B successfully logs in to the IDP, the temporary conference identity of user Bob on the IDP is activated, and the public key and private key of the temporary conference identity are updated to ensure the security of the temporary conference identity.
[0232] Among them, there are many ways for electronic device B to update the public key and private key of the temporary identity of the conference. For details, please refer to the three methods described in the above embodiment, which will not be repeated here. In addition, after electronic device B updates the public key and private key of the temporary identity of the conference, the IDP also stores the updated public key. Furthermore, the IDP may also store the ciphertext corresponding to the updated private key.
[0233] Step 8013: After electronic device B successfully activates the temporary conference identity, the IDP returns a status indication message indicating successful activation of the temporary conference identity to electronic device B.
[0234] Step 8014: Based on the activated temporary conference identity, electronic device B sends a certificate application request to certificate authority A in enterprise A to request certificate authority A to issue a digital certificate to electronic device B.
[0235] In this embodiment, the certificate issuing authority A may be an institution that supports the ACME protocol, and can automatically issue a digital certificate to the electronic device B after the electronic device B completes identity authentication through the IDP.
[0236] Step 8015, based on the ACME protocol supported by certificate authority A, electronic device B initiates a challenge through the IDP to perform identity authentication.
[0237] Step 8016, after electronic device B passes the identity authentication of the IDP, the IDP feeds back the identity authentication result to the certificate authority to indicate that electronic device B passes the identity authentication.
[0238] Step 8017: Certificate authority A issues digital certificate B' to electronic device B.
[0239] like Fig. 9 As shown, the digital certificate B' issued by the certificate authority A for the electronic device B of user Bob includes the following content: the common name is Bob; the organization is enterprise B; the issuing authority is the certificate authority A. In other words, the issuing authority of the digital certificate B' held by the electronic device B becomes the certificate authority A trusted by the conference application service.
[0240] In addition, when the IDP feeds back the identity authentication result to the certificate authority, it indicates the validity period of the verified temporary conference identity, so that the certificate authority A can issue a valid digital certificate B' to the electronic device B. The validity period of the digital certificate B' may not exceed the duration of the conference that the electronic device expects to join.
[0241] Step 8018: Electronic device B of user Bob sends a conference access request carrying digital certificate B' to the conference application service, and is allowed to access the conference by the conference application service.
[0242] In general, if Fig. 9 As shown, for user Alice in enterprise A, user Alice can directly access the conference held by the conference server in enterprise A using the digital certificate issued by certificate authority A in enterprise A. For user Bob in enterprise B, when user Bob accesses the conference using the digital certificate issued by certificate authority B in enterprise B, the conference application service verifies the digital certificate based on the pre-trusted root certificate and triggers user Bob to replace the digital certificate with the digital certificate issued by certificate authority A. Finally, user Bob accesses the conference based on the replaced digital certificate, thereby ensuring that all users accessing the conference hold digital certificates issued by certificate authority A, which can facilitate identity authentication and interaction between users accessing the conference based on mutually trusted digital certificates.
[0243] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. It is understandable that, in order to realize the above functions, the electronic device includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the modules and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.
[0244] The embodiment of the present application can divide the functional modules of the electronic device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.
[0245] The following is a detailed description of the device used to execute the above method in the embodiment of the present application.
[0246] See also Fig.10 , Fig.10 A schematic diagram of the structure of a conference server provided in an embodiment of the present application. Fig.10 As shown, the conference server provided in this embodiment includes: a receiving module 1001, which is used to receive a first access request sent by an electronic device, the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate issuing authority; a processing module 1002, which is used to verify the first digital certificate based on a preset trust policy, and the preset trust policy is used to indicate a trusted certificate list, and the certificate list includes a root certificate corresponding to the first digital certificate; a sending module 1003, which is used to send an identity credential to the electronic device in response to the first digital certificate passing the verification, and the identity credential is used for the electronic device to apply for a digital certificate from a second certificate issuing authority, and the second certificate issuing authority is a trusted institution; the receiving module 1001 is also used to receive a second access request sent by the electronic device and allow the electronic device to access the first conference, the second access request is used to request access to the first conference, and the second access request includes a second digital certificate, and the second digital certificate is issued by the second certificate issuing authority to the electronic device.
[0247] In a possible implementation, the identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the public key corresponding to the first digital certificate.
[0248] In one possible implementation, the identity credentials are obtained by encrypting a login password using the public key corresponding to the first digital certificate. The login password is used for the electronic device to log in to the IDP, and the IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate authority.
[0249] In one possible implementation, the receiving module 1001 is also used to receive a conference creation instruction, which is used to indicate the participants corresponding to the first conference, and the participants include the applicants of the first digital certificate; the sending module 1003 is also used to send a temporary identity creation request to the IDP, and the temporary identity creation request is used to instruct the IDP to create a temporary conference identity for the participants; the receiving module 1001 is also used to receive a login password sent by the IDP.
[0250] In one possible implementation, the conference creation instruction is also used to indicate the operating permissions of the participants in the conference; after allowing the electronic device to access the first conference, the processing module 1002 is also used to set the operating permissions of the electronic device in the first conference based on the application identity corresponding to the second digital certificate.
[0251] In one possible implementation, the preset trust policy is also used to indicate the conference access rights of one or more objects; the processing module 1002 is also used to: determine the conference access rights of the applicant of the first digital certificate based on the preset trust policy; determine whether the applicant has the right to access the first conference based on the type of conference requested to be joined by the first access request and the conference access rights of the applicant; wherein the condition for the first digital certificate to pass the verification includes that the applicant has the right to access the first conference.
[0252] In a possible implementation, the first conference is an end-to-end encrypted conference.
[0253] In a possible implementation manner, the identity field of the first digital certificate is used to indicate a user identity or a device identity.
[0254] In a possible implementation, the second certificate authority supports the ACME protocol.
[0255] See also Fig.11 , Fig.11 This is a schematic diagram of the structure of a conference access device provided in an embodiment of the present application. Fig.11As shown, the conference access device provided in this embodiment includes: a sending module 1101, which is used to send a first access request to a conference server, the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate issuing authority; a receiving module 1102, which is used to receive identity credentials sent by the conference server; a processing module 1103, which is used to apply for a second digital certificate from a second certificate issuing authority based on the identity credentials, and the second certificate issuing authority is an institution trusted by the conference server; the sending module 1101 is also used to send a second access request to the conference server and access the first conference with the permission of the conference server, the second access request is used to request access to the first conference, and the second access request includes a second digital certificate.
[0256] In one possible implementation, the identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the ciphertext credential using the public key corresponding to the first digital certificate; the processing module 1103 is specifically used to: decrypt the ciphertext credential using the private key corresponding to the public key to obtain a plaintext credential; and apply for a digital certificate from a second certificate authority based on the plaintext credential.
[0257] In one possible implementation, the identity credentials are obtained by encrypting a login password using the public key corresponding to the first digital certificate. The login password is used for the electronic device to log in to the IDP, and the IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate authority.
[0258] In a possible implementation, the first conference is an end-to-end encrypted conference.
[0259] In a possible implementation manner, the identity field of the first digital certificate is used to indicate a user identity or a device identity.
[0260] In a possible implementation, the second certificate authority supports the ACME protocol.
[0261] It should be noted that the information interaction, execution process, etc. between the modules / or components in the above device are the same as those in this application. Figure 4-Figure 10 The corresponding method embodiments are based on the same concept. For specific contents, please refer to the description in the method embodiments shown above in this application, which will not be repeated here.
[0262] It should be noted that for the specific implementation of the device and the beneficial effects brought about, please refer to Figure 4-Figure 10 The descriptions in the corresponding method embodiments will not be repeated here one by one.
[0263] The present application also provides a conference system, including: Fig.10 The conference server described in the corresponding embodiment, Fig.11 The conference access device described in the corresponding embodiment.
[0264] An embodiment of the present application also provides a computer-readable storage medium, including instructions, which, when executed on a computer, enables the computer to control an electronic device to execute any one of the implementation methods shown in the aforementioned method embodiments.
[0265] An embodiment of the present application also provides a computer program product, which includes a computer program code. When the computer program code runs on a computer, the computer executes any one of the implementation methods shown in the aforementioned method embodiments.
[0266] An embodiment of the present application also provides a chip system, including a memory and a processor, the memory is used to store computer programs, and the processor is used to call and run computer programs from the memory, so that the chip executes any one of the implementation methods shown in the aforementioned method embodiments.
[0267] It should also be noted that the device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the drawings of the device embodiments provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.
[0268] Through the description of the above implementation methods, the technicians in the relevant field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation method in more cases. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, U disk, mobile hard disk, ROM, RAM, disk or optical disk, etc., including a number of instructions to enable a computer device to execute the methods described in each embodiment of the present application.
[0269] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.
[0270] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a communication device, a computing device, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, communication device, computing device, or data center. The computer-readable storage medium may be any available medium that a computer can store or a communication device, a data center, or other data storage device that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.
[0271] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and 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 embodiment of the present application.
[0272] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
Claims
1. A conference access method, characterized in that: include: receiving a first access request sent by an electronic device, where the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate issuing authority; Verifying the first digital certificate based on a preset trust policy, where the preset trust policy is used to indicate a trusted certificate list, where the certificate list includes a root certificate corresponding to the first digital certificate; In response to the first digital certificate passing the verification, sending an identity credential to the electronic device, the identity credential being used by the electronic device to apply for a digital certificate from a second certificate issuing authority, the second certificate issuing authority being a trusted authority; A second access request sent by the electronic device is received and the electronic device is allowed to access the first conference, wherein the second access request is used to request access to the first conference, and the second access request includes a second digital certificate, and the second digital certificate is issued by the second certificate issuing authority to the electronic device.
2. The method according to claim 1, characterized in that: The identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the public key corresponding to the first digital certificate.
3. The method according to claim 1 or 2, characterized in that: The identity credential is obtained by encrypting a login password using the public key corresponding to the first digital certificate. The login password is used for the electronic device to log in to the identity provider IDP. The IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate authority.
4. The method according to claim 3, characterized in that The method further comprises: receiving a conference creation instruction, wherein the conference creation instruction is used to indicate a participant corresponding to the first conference, wherein the participant includes an applicant for the first digital certificate; Sending a temporary identity creation request to the IDP, wherein the temporary identity creation request is used to instruct the IDP to create a temporary conference identity for the participant; The login password is generated, and the login password is used to enable the participant who has created a temporary identity on the IDP to log in to the IDP.
5. The method according to claim 4, characterized in that Sending identity credentials to the electronic device includes: An identity activation request is sent to the electronic device, wherein the identity activation request includes the identity credential and the address of the IDP, and the identity activation request is used to request the electronic device to activate the temporary conference identity created on the IDP through the identity credential, so that the electronic device can pass the identity authentication of the IDP during the process of applying for a digital certificate from the second certificate authority.
6. The method according to claim 4 or 5, characterized in that: The conference creation instruction is also used to indicate the operation authority of the participant in the conference; After allowing the electronic device to access the first conference, the method further includes: The operation authority of the electronic device in the first conference is set according to the applicant identity corresponding to the second digital certificate.
7. The method according to any one of claims 1 to 6, characterized in that: The preset trust policy is also used to indicate conference access rights of one or more objects; The verifying the first digital certificate includes: Determining conference access rights of an applicant for the first digital certificate based on the preset trust policy; Determining whether the applicant has permission to access the first conference based on the type of the conference requested to be joined by the first access request and the conference access permission of the applicant; The condition for the first digital certificate to pass the verification includes that the applicant has the authority to access the first conference.
8. The method according to any one of claims 1 to 7, characterized in that: The first conference is an end-to-end encrypted conference.
9. The method according to any one of claims 1 to 8, characterized in that: The identity field of the first digital certificate is used to indicate a user identity or a device identity.
10. The method according to any one of claims 1 to 9, characterized in that: The second certificate authority supports the Automatic Certificate Management Environment ACME protocol.
11. A conference access method, characterized in that: include: Sending a first access request to a conference server, where the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, where the first digital certificate is issued by a first certificate authority; Receiving identity credentials sent by the conference server; Applying for a second digital certificate from a second certificate issuing authority based on the identity credentials, where the second certificate issuing authority is an authority trusted by the conference server; A second access request is sent to the conference server and the first conference is accessed with the permission of the conference server, wherein the second access request is used to request access to the first conference and includes a second digital certificate.
12. The method according to claim 11, characterized in that The identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the public key corresponding to the first digital certificate; The applying for a digital certificate from the second certificate issuing authority based on the identity credential includes: Decrypt the ciphertext credential using the private key corresponding to the public key to obtain a plaintext credential; Based on the plaintext credentials, apply for a digital certificate from the second certificate authority.
13. The method according to claim 11 or 12, characterized in that: The method is applied to an electronic device, wherein the identity credential is obtained by encrypting a login password using the public key corresponding to the first digital certificate, the login password is used for the electronic device to log in to an IDP, and the IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate issuing authority.
14. The method according to claim 13, characterized in that The receiving the identity credentials sent by the conference server includes: Receive an identity activation request sent by the conference server, the identity activation request including the identity credential and the address of the IDP, the identity activation request being used to request the electronic device to activate the temporary conference identity created on the IDP through the identity credential, so that the electronic device passes the identity authentication of the IDP during the process of applying for a digital certificate from the second certificate authority.
15. The method according to any one of claims 11 to 14, characterized in that: The first conference is an end-to-end encrypted conference.
16. The method according to any one of claims 11 to 15, characterized in that: The identity field of the first digital certificate is used to indicate a user identity or a device identity.
17. The method according to any one of claims 11 to 16, characterized in that: The second certificate authority supports the ACME protocol.
18. A conference server, characterized in that: include: A receiving module, configured to receive a first access request sent by an electronic device, wherein the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate issuing authority; a processing module, configured to verify the first digital certificate based on a preset trust policy, wherein the preset trust policy is used to indicate a trusted certificate list, wherein the certificate list includes a root certificate corresponding to the first digital certificate; a sending module, configured to send an identity credential to the electronic device in response to the first digital certificate passing verification, wherein the identity credential is used by the electronic device to apply for a digital certificate from a second certificate issuing authority, wherein the second certificate issuing authority is a trusted authority; The receiving module is further used to receive a second access request sent by the electronic device and allow the electronic device to access the first conference, the second access request is used to request access to the first conference, and the second access request includes a second digital certificate, and the second digital certificate is issued by the second certificate issuing authority to the electronic device.
19. The server according to claim 18, characterized in that The identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the public key corresponding to the first digital certificate.
20. The server according to claim 18 or 19, characterized in that: The identity credential is obtained by encrypting a login password using the public key corresponding to the first digital certificate. The login password is used for the electronic device to log in to the IDP. The IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate issuing authority.
21. The server according to claim 20, characterized in that The receiving module is further used to receive a conference creation instruction, where the conference creation instruction is used to indicate a participant corresponding to the first conference, where the participant includes an applicant for the first digital certificate; The sending module is further used to send a temporary identity creation request to the IDP, wherein the temporary identity creation request is used to instruct the IDP to create a temporary conference identity for the participant; The processing module is further used to generate the login password, where the login password is used to enable the participant with a temporary identity created on the IDP to log in to the IDP.
22. The server according to claim 21, characterized in that The sending module is specifically used for: An identity activation request is sent to the electronic device, wherein the identity activation request includes the identity credential and the address of the IDP, and the identity activation request is used to request the electronic device to activate the temporary conference identity created on the IDP through the identity credential, so that the electronic device can pass the identity authentication of the IDP during the process of applying for a digital certificate from the second certificate authority.
23. The server according to claim 21 or 22, characterized in that: The conference creation instruction is also used to indicate the operation authority of the participant in the conference; After allowing the electronic device to access the first conference, the processing module is further configured to set the operation authority of the electronic device in the first conference according to the application identity corresponding to the second digital certificate.
24. The server according to any one of claims 18 to 23, characterized in that: The preset trust policy is also used to indicate conference access rights of one or more objects; The processing module is further used for: Determining conference access rights of an applicant for the first digital certificate based on the preset trust policy; Determining whether the applicant has permission to access the first conference based on the type of the conference requested to be joined by the first access request and the conference access permission of the applicant; The condition for the first digital certificate to pass the verification includes that the applicant has the authority to access the first conference.
25. A conference access device, characterized in that: include: A sending module, configured to send a first access request to a conference server, wherein the first access request is used to request access to a first conference, and the first access request includes a first digital certificate, and the first digital certificate is issued by a first certificate issuing authority; A receiving module, used for receiving the identity credentials sent by the conference server; A processing module, configured to apply for a second digital certificate from a second certificate issuing authority based on the identity credentials, where the second certificate issuing authority is an authority trusted by the conference server; The sending module is further used to send a second access request to the conference server and access the first conference with the permission of the conference server, the second access request is used to request access to the first conference, and the second access request includes a second digital certificate.
26. The device according to claim 25, characterized in that The identity credential is a ciphertext credential, and the ciphertext credential is obtained by encrypting the public key corresponding to the first digital certificate; The processing module is specifically used for: Decrypt the ciphertext credential using the private key corresponding to the public key to obtain a plaintext credential; Based on the plaintext credentials, apply for a digital certificate from the second certificate authority.
27. The device according to claim 25 or 26, characterized in that The identity credential is obtained by encrypting a login password using the public key corresponding to the first digital certificate. The login password is used for the electronic device to log in to the IDP. The IDP is used to provide identity authentication services for the electronic device during the process of the electronic device applying for a digital certificate from the second certificate issuing authority.
28. The device according to claim 27, characterized in that The receiving module is specifically used for: Receive an identity activation request sent by the conference server, the identity activation request including the identity credential and the address of the IDP, the identity activation request being used to request the electronic device to activate the temporary conference identity created on the IDP through the identity credential, so that the electronic device passes the identity authentication of the IDP during the process of applying for a digital certificate from the second certificate authority.
29. A certificate management system, characterized in that: include: The conference server as described in claims 18-24 and the conference access device as described in claims 25-28.
30. A computer storage medium, characterized in that The computer storage medium stores instructions, which, when executed by a computer, cause the computer to implement the method of any one of claims 1 to 17.
31. A computer program product, characterized in that The computer program product stores instructions, which, when executed by a computer, cause the computer to implement the method according to any one of claims 1 to 17.
Citation Information
Cited By
Systems and methods for USB switching in a collaboration system
US12792546B2
Methods and systems for automating connection to a collaborative software platform
US20250240337A1
