CN115334160B - HTTPS certificate issuing method and related equipment thereof - Google Patents
HTTPS certificate issuing method and related equipment thereof Download PDFInfo
- Publication number
- CN115334160B CN115334160B CN202210929148.8A CN202210929148A CN115334160B CN 115334160 B CN115334160 B CN 115334160B CN 202210929148 A CN202210929148 A CN 202210929148A CN 115334160 B CN115334160 B CN 115334160B
- Authority
- CN
- China
- Prior art keywords
- certificate
- https
- https certificate
- management platform
- format
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000004891 communication Methods 0.000 claims abstract description 57
- 238000006243 chemical reaction Methods 0.000 claims description 25
- 230000006870 function Effects 0.000 claims description 15
- 238000010200 validation analysis Methods 0.000 claims description 4
- 238000007726 management method Methods 0.000 description 121
- 238000010586 diagram Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 3
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 235000019800 disodium phosphate Nutrition 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/116—Details of conversion of file system types or formats
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The application belongs to the technical field of communication, and relates to an HTTPS certificate issuing method, an HTTPS certificate issuing device, computer equipment and a storage medium, wherein the method comprises the steps of converting a format into a target format and configuring the HTTPS certificate; building an HTTPS certificate management platform corresponding to the target format; when the APP of the client is started, a HTTPS certificate management platform is established, the client is respectively in communication connection with the server, and the HTTPS certificate to be configured in the HTTPS certificate management platform is automatically issued to the APP for configuration based on the server. Aiming at the condition that the certificate is about to expire or expire, the HTTPS certificate to be configured can be issued in advance, the user can update the latest certificate after opening the application, the flexibility of a certificate fixing mode can be improved, and the user can normally access the network without updating the application.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to an HTTPS certificate issuing method, an HTTPS certificate issuing device, a computer device, and a storage medium.
Background
Currently, the network request of APP (Application) is basically HTTPS (Hyper Text Transfer Protocol over Secure Socket Layer), but HTTPS is not absolutely safe, and the HTTPS can be also be grabbed by setting up an agent. For the case of HTTPS packet grabbing, APP needs to verify the HTTPS certificate when requesting the network in order to prevent grabbing the packet, this way is called certificate fixing.
Currently, the main certificate fixing mode in the market is to embed the HTTPS certificate into the installation package of the APP, however, this causes that when the HTTPS certificate expires or becomes invalid, the APP needs to reissue a version, a new HTTPS certificate is embedded into the APP, the old version HTTPS certificate APP cannot normally access the network, and the APP must be updated to be used, which causes a lot of inconvenience to the user. Therefore, aiming at the condition that the HTTPS certificate is out of date or invalid, the existing certificate fixing mode has the problems of poor flexibility and complicated operation.
Disclosure of Invention
The embodiment of the application aims to provide an HTTPS certificate issuing method, an HTTPS certificate issuing device, computer equipment and a storage medium, which can improve the flexibility of a certificate fixing mode, simplify an operation mode, and can normally access a network without APP updating by a user aiming at the condition that the HTTPS certificate is out of date or invalid.
In order to solve the above technical problems, the embodiments of the present application provide an HTTPS certificate issuing method, which adopts the following technical scheme:
converting the format of an HTTPS certificate to be configured to obtain the HTTPS certificate to be configured in a target format;
building an HTTPS certificate management platform corresponding to the target format, wherein the HTTPS certificate to be configured is stored in the HTTPS certificate management platform;
If the APP of the client is started, establishing communication connection between the HTTPS certificate management platform and the client and a server respectively, and automatically issuing the HTTPS certificate to be configured in the HTTPS certificate management platform to the APP for configuration based on the server.
Further, the step of converting the format of the HTTPS certificate to be configured to obtain the HTTPS certificate to be configured in the target format specifically includes:
converting the HTTPS certificate to be configured in the cer format into the HTTPS certificate to be configured in the base64 coding format by a conversion command.
Further, the step of building an HTTPS certificate management platform corresponding to the target format and detecting whether the configured HTTPS certificate of the APP in the HTTPS certificate management platform meets the issuing time specifically includes:
setting up an HTTPS certificate management platform on the basis of the base64 coding format in the server, wherein the HTTPS certificate management platform comprises functions of adding certificates, deleting certificates, setting certificate validation and setting certificate invalidation, and the HTTPS certificate to be configured comprises a certificate corresponding to at least one APP.
Further, the step of establishing communication connection between the HTTPS certificate management platform and the client and the server respectively, and automatically issuing the HTTPS certificate to be configured in the HTTPS certificate management platform to the APP for configuration based on the server includes:
Establishing communication connection with the HTTPS certificate management platform based on a certificate uploading interface on the server, and establishing communication connection with the APP of the client based on a certificate issuing interface on the server;
uploading at least one to-be-configured HTTPS certificate of the base64 coding format in the HTTPS certificate management platform through the certificate uploading interface configured on the server;
when the client side has APP starting, the HTTPS certificate to be configured in the base64 coding format is issued to the APP of the client side for configuration through the certificate issuing interface configured on the server.
Further, the step of configuring the APP issued to the client specifically includes:
storing the acquired base64 encoding format of the HTTPS certificate to be configured through a preset storage library, and converting the base64 encoding format of the HTTPS certificate to be configured into a data format;
and configuring the HTTPS certificate to be configured in the converted data format based on a network request of an APP.
Further, after the step of automatically issuing the HTTPS certificate to be configured in the HTTPS certificate management platform to the APP for configuration based on the server, the method further includes the steps of:
Detecting whether an expired HTTPS certificate exists in the HTTPS certificate management platform;
and if the invalid HTTPS certificate exists in the HTTPS certificate management platform, deleting the invalid HTTPS certificate through the certificate deleting function.
In order to solve the above technical problems, the embodiments of the present application further provide an HTTPS certificate issuing device, which adopts the following technical scheme:
the conversion module is used for converting the format of the HTTPS certificate to be configured to obtain the HTTPS certificate to be configured in the target format;
the building module is used for building an HTTPS certificate management platform corresponding to the target format, wherein the HTTPS certificate to be configured is stored in the HTTPS certificate management platform;
and the issuing module is used for establishing communication connection between the HTTPS certificate management platform and the client and the server respectively if the APP of the client is started, and automatically issuing the HTTPS certificate to be configured in the HTTPS certificate management platform to the APP for configuration based on the server.
In order to solve the above technical problems, the embodiments of the present application further provide a computer device, which adopts the following technical schemes:
the method comprises a memory and a processor, wherein the memory stores computer readable instructions, and the processor executes the computer readable instructions to realize the steps of the HTTPS certificate issuing method in any embodiment.
In order to solve the above technical problems, embodiments of the present application further provide a computer readable storage medium, which adopts the following technical solutions:
the computer readable storage medium has stored thereon computer readable instructions which when executed by a processor implement the steps of an HTTPS certificate issuing method according to any one of the embodiments described above.
Compared with the prior art, the embodiment of the application has the following main beneficial effects: according to the method, the HTTPS certificate management platform corresponding to the target format is built, communication connection among the HTTPS certificate management platform, the server and the client is built, when the APP in the client is started and a new HTTPS certificate to be configured is generated in the HTTPS certificate management platform, the HTTPS certificate to be configured is automatically uploaded based on communication between the server and the certificate management platform, and the APP of the client automatically acquires the uploaded HTTPS certificate to be configured based on communication between the server and the client to configure. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
Drawings
For a clearer description of the solution in the present application, a brief description will be given below of the drawings that are needed in the description of the embodiments of the present application, it being obvious that the drawings in the following description are some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow chart of one embodiment provided by an HTTPS certificate issuing method according to the present application;
FIG. 3 is a flow chart of one embodiment of step 203 of FIG. 2;
FIG. 4 is a flow chart of one embodiment of step 303 of FIG. 3;
FIG. 5 is a flow chart of one embodiment following step 203 in FIG. 2;
FIG. 6 is a schematic diagram of one embodiment provided by an HTTPS certificate issuing apparatus according to the present application;
FIG. 7 is a schematic structural diagram of one embodiment of a computer device according to the present application.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the applications herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having" and any variations thereof in the description and claims of the present application and in the description of the figures above are intended to cover non-exclusive inclusions. The terms first, second and the like in the description and in the claims or in the above-described figures, are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In order to better understand the technical solutions of the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings.
As shown in fig. 1, the system architecture 100 may include clients (terminal devices) 101, 102, 103, a network 104, a server 105, and an HTTPS certificate management backend 106. The network 104 is used to provide a medium for communication links between the clients 101, 102, 103 and the server 105, and a medium for communication links between the HTTPS certificate management backend 106 and the server 105. The network 104 may include various connection types, such as: wired, wireless communication links, or fiber optic cables, etc.
A user may interact with the server 105 through the network 104 using clients 101, 102, 103 to receive or send messages, etc. Various communication client applications may be installed on clients 101, 102, 103, such as web browser applications, shopping class applications, search class applications, instant messaging tools, mailbox clients, social platform software, and the like.
The clients 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 105 may be a server that provides various services, such as a background server that provides support for pages displayed on the clients 101, 102, 103. The server 105 may be a stand-alone server, or may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and basic cloud computing services such as big data and artificial intelligence platforms.
The HTTPS certificate management daemon 106 may be a management daemon that provides management functions for HTTPS certificates, and may build an operable web interface. The web interface of the HTTPS certificate management backend 106 may be operated and presented through a display screen.
It should be noted that, the HTTPS certificate issuing method provided in the embodiments of the present application is generally executed by a server, and accordingly, the HTTPS certificate issuing method apparatus is generally set in the server.
It should be appreciated that the number of clients 101, 102, 103, network 104, server 105, and HTTPS certificate management daemon 106 in fig. 1 is merely illustrative. There may be any number of clients 101, 102, 103, networks 104, servers 105, and HTTPS certificate management daemons 106, as desired for implementation.
With continued reference to fig. 2, a flowchart of one embodiment of an HTTPS certificate issuing method is shown, in accordance with the present application. The HTTPS certificate issuing method comprises the following steps:
step S201, converting the format of the HTTPS certificate to be configured to obtain the HTTPS certificate to be configured in the target format.
In this embodiment, an electronic device (for example, a server/client shown in fig. 1) on which the HTTPS certificate issuing method operates may implement communication connection with other electronic devices through a wired connection manner or a wireless connection manner, and acquire or send various data and instructions. It should be noted that the wireless connection may include, but is not limited to, 3G/4G connections, wiFi connections, bluetooth connections, wiMAX connections, zigbee connections, UWB (ultra wideband) connections, and other now known or later developed wireless connection means.
In this embodiment, the HTTPS certificate to be configured may refer to an HTTPS certificate that corresponds to a single APP/different APPs in the same client, or that needs to be reconfigured when the configured HTTPS certificate is about to expire or expire. The HTTPS certificates corresponding to the same APP are the same, and the HTTPS certificates corresponding to different APPs may be the same or different, whether in the same client or different clients. Different APPs may be included on different clients, or the same APP may be included. The format of the HTTPS certificate to be configured is different from the format of the HTTPS certificate to be configured, so that the format of the HTTPS certificate to be configured can be converted, and the HTTPS certificate to be configured with the target format in the APP which can be issued to the client is obtained.
Step S202, an HTTPS certificate management platform corresponding to the target format is built, where the HTTPS certificate to be configured is stored in the HTTPS certificate management platform.
In this embodiment, after the HTTPS certificate is generated and format conversion is completed, an operable web interface may be built in the management background, that is, an HTTPS certificate management platform corresponding to the target format is built, the HTTPS certificate to be configured is stored in the HTTPS certificate management platform, and different HTTPS certificates may be respectively stored in different storage areas. The HTTPS certificate management platform is set to be in a target format, so that data transmission and storage are facilitated, and subsequent use is also facilitated.
Specifically, in the HTTPS certificate management platform, various operations may be performed, such as: adding certificates, deleting certificates, setting certificates to take effect, setting certificates to fail, displaying configuration time, adding operators and the like. The HTTPS certificate management platform can better perform unified background management on the configured HTTPS certificate and the HTTPS certificate to be configured.
In step S203, if the APP of the client is started, communication connection between the HTTPS certificate management platform and the client and the server is established, and the HTTPS certificate to be configured in the HTTPS certificate management platform is automatically issued to the APP for configuration based on the server.
In this embodiment, when the APP of the client is started, communication connection between the HTTPS certificate management platform and the client and the server may be established, that is, the HTTPS certificate management platform communicates with the server, and the client communicates with the server. The method specifically comprises the steps of configuring interfaces corresponding to the HTTPS certificate management platform and the client on a server, and realizing communication connection based on the interfaces.
Specifically, based on the communication connection between the server and the HTTPS certificate management platform, the HTTPS certificate management platform can automatically upload the stored and validated HTTPS certificate to be configured to the server, and meanwhile, based on the communication connection between the server and the client, the APP of the client can automatically acquire the HTTPS certificate to be configured to perform certificate configuration.
In the embodiment of the invention, by building the HTTPS certificate management platform corresponding to the target format and establishing communication connection among the HTTPS certificate management platform, the server and the client, when the APP in the client is started and a new HTTPS certificate to be configured is generated in the HTTPS certificate management platform, the HTTPS certificate to be configured is automatically uploaded based on the communication between the server and the certificate management platform, and the APP of the client automatically acquires the uploaded HTTPS certificate to be configured based on the communication between the server and the client for configuration. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
In some alternative implementations, step 201 in fig. 2 specifically includes:
and converting the HTTPS certificate to be configured in the cer format into the HTTPS certificate to be configured in the base64 coding format by a conversion command.
The above conversion command may refer to an instruction for implementing format conversion, and in this embodiment, the conversion command may be: the openssl x 509-form der-in authentication. The HTTPS certificate to be configured in cer format can be converted into the HTTPS certificate to be configured in the base64 encoding format as the target format through the conversion command. Setting the target format to the base64 encoding format is more convenient to transmit and to store and use after receipt.
In some alternative implementations, step 202 in fig. 2 specifically includes:
setting up an HTTPS certificate management platform on the basis of a base64 coding format in a server, wherein the HTTPS certificate management platform comprises functions of adding certificates, deleting the certificates, setting the certificates to be effective and setting certificate invalidation, and the HTTPS certificate to be configured comprises certificates corresponding to at least one APP.
In this embodiment, after converting the format of the HTTPS certificate to be configured into the base64 encoding format, the HTTPS certificate management platform that is set up is also set up based on the base64 encoding format. In the HTTPS certificate management platform, functions such as adding certificates, deleting certificates, setting certificate validation, setting certificate revocation functions and the like can be included. For example: when there is a condition that the configured HTTPS certificate is about to expire or has an expiration condition, the certificate can be added, and the expired and/or expired HTTPS certificate can be deleted. When the HTTPS to be configured is loaded to the HTTPS certificate management platform for storage, information such as the validation time, expiration time, configuration time, and operator of the HTTPS to be configured can be set.
In this embodiment, by setting up an HTTPS certificate management platform in a base64 encoding format, it is beneficial to store an HTTPS certificate to be configured in the base64 encoding format and to transmit and use the HTTPS certificate subsequently. And various operation functions are provided in the HTTPS certificate management platform, so that the management efficiency of certificates in the HTTPS certificate management platform can be improved.
In some alternative implementations, as shown in fig. 3, fig. 3 is a flow chart of a specific embodiment of step 203 in fig. 2. The step 203 executed by the electronic device specifically includes the following steps:
step S301, a communication connection with the HTTPS certificate management platform is established based on the certificate upload interface on the server, and a communication connection with the APP of the client is established based on the certificate issue interface on the server.
Step S302, uploading, through a certificate uploading interface configured on the server, at least one HTTPS certificate to be configured in a base64 encoding format in the HTTPS certificate management platform.
In this embodiment, a certificate upload interface for certificate upload may be configured on the server, and a communication connection with the HTTPS certificate management platform is established through the certificate upload interface. Similarly, a certificate issuing interface for issuing certificates can be configured on the server, and communication connection with the client is established through the certificate issuing interface. Once the HTTPS certificate to be configured in the base64 encoding format has been generated in the HTTPS certificate management platform, the HTTPS certificate to be configured in the base64 encoding format may be uploaded from the HTTPS certificate management platform to the server through the certificate upload interface.
Step S303, when the client side has APP starting, the HTTPS certificate to be configured in the base64 coding format is issued to the APP of the client side for configuration through a certificate issuing interface configured on the server.
As a possible embodiment, when only one APP in the client starts, the client may obtain, from the server through the certificate issuing interface, the HTTPS certificate to be configured in the base64 encoding format, and issue the HTTPS certificate to the APP for configuration.
As another possible embodiment, when there are multiple identical APPs started by different clients and needing to perform certificate configuration, an HTTPS certificate to be configured corresponding to the APP is generated in the HTTPS certificate management platform and issued to the server. When the same APP of different clients acquires the HTTPS certificates from the server, the same APP of a plurality of clients is supported to acquire the same HTTPS certificate at the same time, namely the same HTTPS certificate is issued to a plurality of the same APP to be configured at the same time.
As another possible embodiment, for the case where there are multiple different APP starts in multiple/same clients, and HTTPS certificates corresponding to APPs are different. If the plurality of APPs in the client side all need to carry out HTTPS certificate configuration and the configured HTTPS certificates are different, the HTTPS certificate corresponding to each APP is also generated in the HTTPS certificate management platform, and the HTTPS certificate is issued to the server after the certificate is generated. When a plurality of different APPs of the client start to acquire respective HTTPS certificates from the server, the client supports to acquire a plurality of different HTTPS certificates simultaneously, and each HTTPS certificate is issued to a corresponding APP for configuration.
In this embodiment, by configuring a certificate upload interface and a certificate issue interface on the server, a communication connection with the HTTPS certificate management platform is established based on the book upload interface, and a communication connection with the APP of the client is established based on the certificate issue interface. After the HTTPS certificate to be configured is generated, the HTTPS certificate management platform can automatically upload the HTTPS certificate to be configured, and the client can directly acquire the HTTPS certificate to configure. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
In some alternative implementations, as shown in fig. 4, fig. 4 is a flowchart of a specific embodiment of step S303 in fig. 3 provided in this embodiment. In step S303 executed by the above electronic device, the step of configuring the APP issued to the client specifically includes:
step S401, storing the acquired HTTPS certificate to be configured in the base64 encoding format through a preset repository, and converting the base64 encoding format of the HTTPS certificate to be configured into a data format.
The preset storage library can be NSFileManager or database. The HTTPS credentials to be configured, which have been issued to the base64 encoding format in the APP, may be stored in the NSFileManager/database. Meanwhile, in order to adapt to the format required by the APP configuration, the HTTPS certificate to be configured in the base64 coding format in the NSFileManager/database can be read, and the HTTPS certificate to be configured in the base64 coding format is converted into the HTTPS certificate to be configured in the data format.
Step S402, based on the network request of the APP, the HTTPS certificate to be configured in the converted data format is configured.
The network request may be a network request for configuring a certificate. And triggering the network request by the APP to perform certificate configuration, and after the APP completes the verification of the network request, configuring the HTTPS certificate to be configured in the converted data format.
In this embodiment, the APP of the client obtains the HTTPS certificate to be configured in the base64 encoding format, and stores the HTTPS certificate to be configured in the base64 encoding format through the NSFileManager/database, and performs format conversion for the format required for satisfying configuration, and reads the HTTPS certificate to be configured in the base64 encoding format in the NSFileManager/database to perform format conversion, thereby obtaining the HTTPS certificate to be configured in the data format. After the APP sends out a network request for configuring the certificate, the data format HTTPS certificate to be configured can be configured. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
In some alternative implementations, as shown in fig. 5, fig. 5 is a flowchart of one embodiment after step 203 in fig. 2. The electronic device is further configured to perform the steps of:
in step S501, it is determined whether the HTTPS certificate configured in the HTTPS certificate management platform has been revoked.
Specifically, after at least one HTTPS certificate issue, the HTTPS certificate management platform stores a plurality of configured HTTPS certificates. To ensure resource utilization of the HTTPS certificate management platform, HTTPS certificates that have been configured in the HTTPS certificate management platform may be periodically cleaned up. Cleaning up the expired HTTPS certificates can be achieved by periodically detecting whether the configured HTTPS certificates in the HTTPS certificate management platform are expired. For example: all configured HTTPS certificates were cleaned up once every 3 months on a regular basis. Of course, the periodic time may also be determined based on the validity period of the HTTPS certificate.
In step S502, if there is an already-expired HTTPS certificate in the HTTPS certificate management platform, the already-expired HTTPS certificate is deleted by the certificate deletion function.
Specifically, when detecting that the configured HTTPS certificate is invalid in the HTTPS certificate management platform, the invalid HTTPS certificate may be deleted based on the certificate deletion function of the HTTPS certificate management platform.
In this embodiment, by periodically detecting whether an expired HTTPS certificate exists in the HTTPS certificate management platform, the expired HTTPS certificate is deleted. Therefore, when the newly generated HTTPS certificate is loaded to the HTTPS certificate management platform, the situation that the space is insufficient is avoided as much as possible, and the effective utilization of space resources is facilitated.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by computer readable instructions stored in a computer readable storage medium that, when executed, may comprise the steps of the embodiments of the methods described above. The storage medium may be a nonvolatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a random access Memory (Random Access Memory, RAM).
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the flowcharts of the figures may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily being sequential, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.
With further reference to fig. 6, as an implementation of the method shown in fig. 2, the present application provides an embodiment of an HTTPS certificate issuing apparatus, where an embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
Fig. 6 is a schematic structural diagram of an HTTPS certificate issuing device according to the present embodiment, as shown in fig. 6. The apparatus 600 includes:
the conversion module 601 is configured to convert the format of the HTTPS certificate to be configured to obtain the HTTPS certificate to be configured in the target format.
The building module 602 is configured to build an HTTPS certificate management platform corresponding to the target format, where the HTTPS certificate to be configured is stored in the HTTPS certificate management platform.
And the issuing module 603 is configured to establish communication connection between the HTTPS certificate management platform and the client and the server if the APP of the client is started, and automatically issue the HTTPS certificate to be configured in the HTTPS certificate management platform to the APP for configuration based on the server.
In this embodiment, the HTTPS certificate to be configured may refer to an HTTPS certificate that corresponds to a single APP/different APPs in the same client, or that needs to be reconfigured when the configured HTTPS certificate is about to expire or expire. The HTTPS certificates corresponding to the same APP are the same, and the HTTPS certificates corresponding to different APPs may be the same or different, whether in the same client or different clients. Different APPs may be included on different clients, or the same APP may be included. The format of the HTTPS certificate to be configured is different from the format of the HTTPS certificate to be configured during the configuration, so that the format of the HTTPS certificate to be configured can be converted by the conversion module 601, and the HTTPS certificate to be configured in the target format of the APP which can be issued to the client is obtained.
After the HTTPS certificate is generated and format conversion is completed, an operable web interface can be built in the management background through the building module 602, that is, the HTTPS certificate management platform corresponding to the target format is built, the HTTPS certificate to be configured is stored in the HTTPS certificate management platform, and different HTTPS certificates can be respectively stored in different storage areas. The HTTPS certificate management platform is set to be in a target format, so that data transmission and storage are facilitated, and subsequent use is also facilitated.
Specifically, in the HTTPS certificate management platform, various operations may be performed, such as: adding certificates, deleting certificates, setting certificates to take effect, setting certificates to fail, displaying configuration time, adding operators and the like. The HTTPS certificate management platform can better perform unified background management on the configured HTTPS certificate and the HTTPS certificate to be configured.
When the APP of the client starts, communication connection between the HTTPS certificate management platform and the client and the server can be established based on the issuing module 603, that is, the HTTPS certificate management platform communicates with the server, and the client communicates with the server. The method specifically comprises the steps of configuring interfaces corresponding to the HTTPS certificate management platform and the client on a server, and realizing communication connection based on the interfaces.
Specifically, based on the communication connection between the server and the HTTPS certificate management platform, the HTTPS certificate management platform can automatically upload the stored and validated HTTPS certificate to be configured to the server, and meanwhile, based on the communication connection between the server and the client, the APP of the client can automatically acquire the HTTPS certificate to be configured to perform certificate configuration.
In the embodiment of the present invention, the conversion of the HTTPS certificate to be configured in the target format is completed through the conversion module 601, then an HTTPS certificate management platform corresponding to the target format is built through the building module 602, and communication connection among the HTTPS certificate management platform, the server and the client is established. When an APP in the client starts and a new HTTPS certificate to be configured is generated in the HTTPS certificate management platform, the HTTPS certificate to be configured is automatically uploaded based on communication between the server and the certificate management platform through the issuing module 603, and the APP of the client automatically acquires the uploaded HTTPS certificate to be configured for configuration based on communication between the server and the client. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
In some optional implementations of this embodiment, the conversion module 601 is further configured to convert, by the conversion command, the HTTPS certificate to be configured in cer format into the HTTPS certificate to be configured in the target format that is a base64 encoding format.
In this embodiment, converting the cer format of the HTTPS certificate to be configured into the base64 encoding format is more convenient for transmission and storage and use after receipt.
In some optional implementations of this embodiment, the setup module 602 is further configured to set up an HTTPS certificate management platform on the server based on the base64 encoding format, where the HTTPS certificate to be configured includes a certificate corresponding to at least one APP, and the HTTPS certificate management platform includes functions of adding a certificate, deleting a certificate, setting a certificate to be effective, and setting a certificate to be invalid.
In this embodiment, the HTTPS certificate management platform in the base64 encoding format is built by the building module 602, which is favorable for storing and subsequent transmitting and using HTTPS certificates to be configured in the base64 encoding format. And various operation functions are provided in the HTTPS certificate management platform, so that the management efficiency of certificates in the HTTPS certificate management platform can be improved.
In some optional implementations of this embodiment, the issuing module 603 includes:
And the communication sub-module is used for establishing communication connection with the HTTPS certificate management platform based on a certificate uploading interface on the server and establishing communication connection with the APP of the client based on a certificate issuing interface on the server.
And the uploading sub-module is used for uploading at least one HTTPS certificate to be configured in a base64 coding format in the HTTPS certificate management platform through a certificate uploading interface configured on the server.
And the issuing sub-module is used for issuing the HTTPS certificate to be configured in the base64 coding format to the APP of the client for configuration through a certificate issuing interface configured on the server when the APP is started.
In this embodiment, a certificate upload interface and a certificate issue interface are configured on a server through a communication sub-module, a communication connection with an HTTPS certificate management platform is established based on the book upload interface, and a communication connection with an APP of a client is established based on the certificate issue interface. After the HTTPS certificate to be configured is generated, the HTTPS certificate management platform can automatically upload the HTTPS certificate to be configured through the uploading submodule, and the client side can directly acquire the HTTPS certificate to be configured through the issuing submodule. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
In some optional implementations of this embodiment, the issuing submodule includes:
the conversion subunit is used for storing the acquired base64 encoding format to-be-configured HTTPS certificate through a preset storage library, and converting the base64 encoding format of the to-be-configured HTTPS certificate into a data format.
And the configuration subunit is used for configuring the HTTPS certificate to be configured in the converted data format based on the network request of the APP.
In this embodiment, the APP of the client obtains the HTTPS certificate to be configured in the base64 encoding format, and stores the HTTPS certificate to be configured through the NSFileManager/database, and performs format conversion for the format required by the configuration, and reads the HTTPS certificate to be configured in the base64 encoding format in the NSFileManager/database through the conversion subunit to perform format conversion, thereby obtaining the HTTPS certificate to be configured in the data format. After the APP sends out a network request for configuring the certificate, the configuration subunit can configure the HTTPS certificate to be configured in the data format. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
In some optional implementations of this embodiment, the method further includes a judging module and a deleting module, where:
and the judging module is used for detecting whether the invalid HTTPS certificate exists in the HTTPS certificate management platform.
And the deleting module is used for deleting the expired HTTPS certificate through a certificate deleting function if the expired HTTPS certificate exists in the HTTPS certificate management platform.
In this embodiment, the judgment module periodically detects whether an already-expired HTTPS certificate exists in the HTTPS certificate management platform, and the deletion module deletes the already-expired HTTPS certificate. Therefore, when the newly generated HTTPS certificate is loaded to the HTTPS certificate management platform, the situation that the space is insufficient is avoided as much as possible, and the effective utilization of space resources is facilitated.
In order to solve the technical problems, the embodiment of the application also provides computer equipment. Referring specifically to fig. 7, fig. 7 is a basic structural block diagram of a computer device according to the present embodiment.
The computer device 70 includes a memory 701, a processor 702, and a network interface 703 communicatively coupled to each other via a system bus. It should be noted that only computer device 70 having components 701-703 is shown in the figures, but it is understood that not all of the illustrated components need be implemented, and that more or fewer components may be implemented instead. It will be appreciated by those skilled in the art that the computer device herein is a device capable of automatically performing numerical calculations and/or information processing in accordance with predetermined or stored instructions, the hardware of which includes, but is not limited to, microprocessors, application specific integrated circuits (Application SpecificIntegrated Circuit, ASICs), programmable gate arrays (fields-Programmable Gate Array, FPGAs), digital processors (Digital Signal Processor, DSPs), embedded devices, etc.
The computer device may be a desktop computer, a notebook computer, a palm computer, a cloud server, or the like. The computer device can perform man-machine interaction with a user through a keyboard, a mouse, a remote controller, a touch pad or voice control equipment and the like.
The memory 701 includes at least one type of readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 701 may be an internal storage unit of the computer device 70, such as a hard disk or memory of the computer device 70. In other embodiments, the memory 701 may also be an external storage device of the computer device 70, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the computer device 70. Of course, the memory 701 may also include both internal storage units of the computer device 70 and external storage devices. In this embodiment, the memory 701 is typically used to store an operating system installed on the computer device 70 and various application software, such as computer readable instructions of HTTPS certificate issuing method, and the like. In addition, the memory 701 can also be used to temporarily store various types of data that have been output or are to be output.
The processor 702 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 702 is generally used to control the overall operation of the computer device 70. In this embodiment, the processor 702 is configured to execute computer readable instructions stored in the memory 701 or process data, such as computer readable instructions for executing an HTTPS certificate issuing method.
The network interface 703 may include a wireless network interface or a wired network interface, the network interface 703 typically being used to establish a communication connection between the computer device 70 and other electronic devices.
In the embodiment of the invention, by building the HTTPS certificate management platform corresponding to the target format and establishing communication connection among the HTTPS certificate management platform, the server and the client, when the APP in the client is started and a new HTTPS certificate to be configured is generated in the HTTPS certificate management platform, the HTTPS certificate to be configured is automatically uploaded based on the communication between the server and the certificate management platform, and the APP of the client automatically acquires the uploaded HTTPS certificate to be configured based on the communication between the server and the client for configuration. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
The present application also provides another embodiment, namely, a computer-readable storage medium, where computer-readable instructions are stored, where the computer-readable instructions are executable by at least one processor to cause the at least one processor to perform the steps of the HTTPS certificate issuing method as described above.
In the embodiment of the invention, by building the HTTPS certificate management platform corresponding to the target format and establishing communication connection among the HTTPS certificate management platform, the server and the client, when the APP in the client is started and a new HTTPS certificate to be configured is generated in the HTTPS certificate management platform, the HTTPS certificate to be configured is automatically uploaded based on the communication between the server and the certificate management platform, and the APP of the client automatically acquires the uploaded HTTPS certificate to be configured based on the communication between the server and the client for configuration. Aiming at the condition that the configured certificate in the APP is about to expire or lose efficacy, the HTTPS certificate to be configured can be issued in advance, the latest HTTPS certificate can be updated as long as a user opens the APP, the flexibility of a certificate fixing mode can be improved, the operation mode is simplified, and the user does not need to update the APP and can normally access the network.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a client (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the HTTPS certificate issuing method of the embodiments of the present application.
It is apparent that the embodiments described above are only some embodiments of the present application, but not all embodiments, the preferred embodiments of the present application are given in the drawings, but not limiting the patent scope of the present application. This application may be embodied in many different forms, but rather, embodiments are provided in order to provide a more thorough understanding of the present disclosure. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that modifications may be made to the embodiments described in the foregoing, or equivalents may be substituted for elements thereof. All equivalent structures made by the specification and the drawings of the application are directly or indirectly applied to other related technical fields, and are also within the protection scope of the application.
Claims (10)
1. An HTTPS certificate issuing method, characterized by comprising the steps of:
converting the format of an HTTPS certificate to be configured to obtain the HTTPS certificate to be configured in a target format;
building an HTTPS certificate management platform corresponding to the target format, wherein an HTTPS certificate to be configured of the target format is stored in the HTTPS certificate management platform;
if the APP of the preset client is started, establishing communication connection between the HTTPS certificate management platform and the client and a server respectively, and automatically issuing the HTTPS certificate to be configured in the target format in the HTTPS certificate management platform to the APP for configuration based on the server.
2. The HTTPS certificate issuing method according to claim 1, wherein said step of converting the format of an HTTPS certificate to be configured to obtain said HTTPS certificate to be configured in the target format specifically includes:
converting the HTTPS certificate to be configured in the cer format into the HTTPS certificate to be configured in the base64 coding format by a conversion command.
3. The HTTPS certificate issuing method according to claim 2, wherein said step of building an HTTPS certificate management platform corresponding to said target format specifically comprises:
Setting up an HTTPS certificate management platform on the basis of the base64 coding format in the server, wherein the HTTPS certificate management platform comprises functions of adding certificates, deleting certificates, setting certificate validation and setting certificate invalidation, and the HTTPS certificate to be configured comprises a certificate corresponding to at least one APP.
4. The HTTPS certificate issuing method according to claim 2, wherein the step of establishing communication connections between the HTTPS certificate management platform and the client and a server, and automatically issuing the HTTPS certificate to be configured in the HTTPS certificate management platform to the APP based on the server, includes:
establishing communication connection with the HTTPS certificate management platform based on a certificate uploading interface on the server, and establishing communication connection with the APP of the client based on a certificate issuing interface on the server;
uploading at least one to-be-configured HTTPS certificate of the base64 coding format in the HTTPS certificate management platform through the certificate uploading interface configured on the server;
when the client side has APP starting, the HTTPS certificate to be configured in the base64 coding format is issued to the APP of the client side for configuration through the certificate issuing interface configured on the server.
5. The HTTPS certificate issuing method of claim 4, wherein the step of configuring the APP issued to the client includes:
storing the acquired base64 encoding format of the HTTPS certificate to be configured through a preset storage library, and converting the base64 encoding format of the HTTPS certificate to be configured into a data format;
and configuring the HTTPS certificate to be configured in the converted data format based on a network request of an APP.
6. The HTTPS certificate issuing method according to claim 3, further comprising, after the step of automatically issuing the HTTPS certificate to be configured in the HTTPS certificate management platform to the APP for configuration based on the server, the steps of:
detecting whether an expired HTTPS certificate exists in the HTTPS certificate management platform;
and if the invalid HTTPS certificate exists in the HTTPS certificate management platform, deleting the invalid HTTPS certificate through the certificate deleting function.
7. An HTTPS certificate issuing device, comprising:
the conversion module is used for converting the format of the HTTPS certificate to be configured to obtain the HTTPS certificate to be configured in the target format;
The building module is used for building an HTTPS certificate management platform corresponding to the target format, wherein the HTTPS certificate to be configured of the target format is stored in the HTTPS certificate management platform;
and the issuing module is used for establishing communication connection between the HTTPS certificate management platform and the client and the server respectively if the APP of the preset client is started, and automatically issuing the HTTPS certificate to be configured in the target format in the HTTPS certificate management platform to the APP for configuration based on the server.
8. The HTTPS certificate issuing device according to claim 7, wherein said conversion module is further configured to convert said HTTPS certificate to be configured in cer format into said HTTPS certificate to be configured in base64 encoding format by a conversion command.
9. A computer device comprising a memory having stored therein computer readable instructions which when executed by the processor implement the steps of the HTTPS certificate issuing method of any one of claims 1 to 6.
10. A computer readable storage medium having stored thereon computer readable instructions which when executed by a processor implement the steps of the HTTPS certificate issuing method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210929148.8A CN115334160B (en) | 2022-08-03 | 2022-08-03 | HTTPS certificate issuing method and related equipment thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210929148.8A CN115334160B (en) | 2022-08-03 | 2022-08-03 | HTTPS certificate issuing method and related equipment thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115334160A CN115334160A (en) | 2022-11-11 |
| CN115334160B true CN115334160B (en) | 2024-03-29 |
Family
ID=83921834
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210929148.8A Active CN115334160B (en) | 2022-08-03 | 2022-08-03 | HTTPS certificate issuing method and related equipment thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115334160B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107689957A (en) * | 2017-08-31 | 2018-02-13 | 云宏信息科技股份有限公司 | A kind of digital certificate management method, electronic equipment, storage medium |
| CN109639661A (en) * | 2018-12-04 | 2019-04-16 | 深圳前海微众银行股份有限公司 | Server certificate update method, device, equipment and computer readable storage medium |
| CN110519239A (en) * | 2019-08-09 | 2019-11-29 | 苏州浪潮智能科技有限公司 | A kind of protocol configuration method, device, equipment and readable storage medium storing program for executing |
| WO2020233308A1 (en) * | 2019-05-22 | 2020-11-26 | 深圳壹账通智能科技有限公司 | Self-checking method, apparatus and device based on local certificate, and storage medium |
| CN112073433A (en) * | 2020-09-25 | 2020-12-11 | 微医云(杭州)控股有限公司 | SSL certificate updating method and device, electronic equipment and storage medium |
| CN113179323A (en) * | 2021-04-29 | 2021-07-27 | 杭州迪普科技股份有限公司 | HTTPS request processing method, device and system for load balancing equipment |
| CN113810501A (en) * | 2021-09-23 | 2021-12-17 | 福信富通科技股份有限公司 | Method for managing HTTPS certificate |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180302787A1 (en) * | 2017-04-13 | 2018-10-18 | Synchronoss Technologies, Inc. | Systems and methods for securely provisioning hypertext transfer protocol secure (https) pins to a mobile client |
| US10432613B2 (en) * | 2017-08-23 | 2019-10-01 | Dell Products L. P. | HTTPS enabled client tool |
-
2022
- 2022-08-03 CN CN202210929148.8A patent/CN115334160B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107689957A (en) * | 2017-08-31 | 2018-02-13 | 云宏信息科技股份有限公司 | A kind of digital certificate management method, electronic equipment, storage medium |
| CN109639661A (en) * | 2018-12-04 | 2019-04-16 | 深圳前海微众银行股份有限公司 | Server certificate update method, device, equipment and computer readable storage medium |
| WO2020233308A1 (en) * | 2019-05-22 | 2020-11-26 | 深圳壹账通智能科技有限公司 | Self-checking method, apparatus and device based on local certificate, and storage medium |
| CN110519239A (en) * | 2019-08-09 | 2019-11-29 | 苏州浪潮智能科技有限公司 | A kind of protocol configuration method, device, equipment and readable storage medium storing program for executing |
| CN112073433A (en) * | 2020-09-25 | 2020-12-11 | 微医云(杭州)控股有限公司 | SSL certificate updating method and device, electronic equipment and storage medium |
| CN113179323A (en) * | 2021-04-29 | 2021-07-27 | 杭州迪普科技股份有限公司 | HTTPS request processing method, device and system for load balancing equipment |
| CN113810501A (en) * | 2021-09-23 | 2021-12-17 | 福信富通科技股份有限公司 | Method for managing HTTPS certificate |
Non-Patent Citations (1)
| Title |
|---|
| 电力调度证书系统的特点及应用;王文;鲁玉华;陶静娜;马骁;刘刚;梁野;李勃;陈贵凤;;电网技术(第12期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115334160A (en) | 2022-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5429912B2 (en) | Authentication system, authentication server, service providing server, authentication method, and program | |
| JP6515207B2 (en) | Internet access authentication method and client, and computer storage medium | |
| CN113630377B (en) | Single sign-on for hosted mobile devices | |
| US20130339949A1 (en) | Provisioning of a Virtual Machine by Using a Secured Zone of a Cloud Environment | |
| CN108718347B (en) | Domain name resolution method, system, device and storage medium | |
| US20100043052A1 (en) | Apparatus and method for security management of user terminal | |
| JP2010504670A (en) | How to get and check public key certificate status | |
| CN113271296B (en) | Login authority management method and device | |
| US20120192263A1 (en) | Access gateway and method for providing cloud storage service | |
| JP6248641B2 (en) | Information processing system and authentication method | |
| CN110895603B (en) | Multi-system account information integration method and device | |
| CN110971703B (en) | Service request method, device, server and storage medium based on connection pool | |
| CN113783829B (en) | Method and device for realizing equipment access across platforms | |
| CN112866385A (en) | Interface calling method and device, electronic equipment and storage medium | |
| WO2019095388A1 (en) | Remotely-assisted processing method and device | |
| CN115334160B (en) | HTTPS certificate issuing method and related equipment thereof | |
| TWI505100B (en) | Method for sharing and synchronizing data in local area network | |
| CN110650014B (en) | Signature authentication method, system, equipment and storage medium based on hessian protocol | |
| CN112364334A (en) | Single sign-on method and device, electronic equipment and storage medium | |
| CN111030900A (en) | Authentication-free login method and device and electronic equipment | |
| CN113434824B (en) | Software service authorization management method, device, equipment and storage medium | |
| CN110945503A (en) | User authentication service providing method, web server and user terminal | |
| CN115330396A (en) | Payment state acquisition method and device, computer equipment and storage medium | |
| CN113179293A (en) | Method for remotely operating clients in batch by Web end | |
| CN112580975A (en) | Business process processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |