A front-end HTTPS protocol environment building method, device and computer program product

Abstract

The application provides a front-end HTTPS protocol environment building method and device and a computer program product, relates to the technical field of computers, and uses the same technology stack JavaScript for development of the front-end and back-end, the front-end service collects a certificate configuration form entered by a user, and after validity verification, the back-end service calls a plurality of certificate generators to automatically generate a key and a certificate, and performs local storage and management. The front-end service provides certificate information display, list update and download functions. The application integrates a plurality of certificate generation tools, provides a visual operation interface, realizes automatic generation, unified management and convenient use of HTTPS certificates, significantly reduces the technical threshold and operation complexity of HTTPS environment configuration, effectively improves front-end development efficiency, and guarantees multi-environment protocol consistency.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, and computer program product for setting up a front-end HTTPS protocol environment. Background Technology

[0002] During the development phase, the front-end primarily uses a development environment with HTTP as the protocol. Once the functionality is basically stable, testing and acceptance environments are used to verify the functionality, also primarily using HTTP. However, the main protocol used in the production environment is HTTPS, which differs from the development phase. This causes some problems to not be exposed during the development phase but only in the production environment, adversely affecting business stability.

[0003] Currently, protocol inconsistencies can cause the following problems: 1) Front-end dependent resources such as JS and CSS may be blocked from loading insecure resources due to different protocols. This can lead to page resource issues such as image loading failure, missing content, and style corruption. 2) Interface request failure: When a browser requests an interface under the HTTP protocol while under the HTTPS protocol, the request will be intercepted, resulting in data retrieval failure. 3) Cookie incompatibility: If the cookie is set with the Secure attribute, the cookie will only be effective under the HTTPS protocol and will not be effective over HTTP. Subsequent requests will also lack cookies, causing problems such as missing user identity. 4) Inconsistent WebSocket connection protocols: WebSocket initiates wss: / / (encrypted) under the HTTPS protocol and ws: / / (unencrypted) under the HTTP protocol. If the protocols are inconsistent, the WebSocket connection will fail. 5) Failure to call third-party services in the production environment: Some third-party services have protocol requirements in the production environment and only support HTTPS. Therefore, protocol differences in different environments will trigger functional anomalies. When introducing new technologies and functional scenarios, special attention needs to be paid to functional verification under different protocols.

[0004] Enabling HTTPS for a service requires a certificate (SSL / TLS certificate). A certificate is a digital file signed by a Certificate Authority (CA) and contains the website's public key, website information, and issuer information. The certificate information must be consistent with the designated server. During communication between the user and the designated server, encrypted communication is achieved through the information in the certificate, ensuring the security of accessed information.

[0005] Currently, configuring HTTPS for frontends can be achieved using either a local frontend development server or Nginx. Taking the Vue framework as an example, a local development server can be configured by setting the `HTTPS` property of the `devServer` option in the `vue.config.js` file to `true` (the principle is the same for other frameworks), or by using a specified certificate in the HTTPS configuration options. However, this approach is only suitable for a small number of frontend services. Considering that current frontend services mainly adopt a micro-frontend design, with each service having a complex and singular scenario, if the functionality involves multiple frontend services, each service would need to run a local development server, resulting in significant system overhead and high environment configuration costs. Furthermore, in the "HTTPS true" solution, the certificate is generated in real-time and used only once per startup, without being saved to the local disk; and the certificate cannot be configured, which is unsuitable for scenarios requiring specific domain names or complex configurations. The Nginx solution uses the Nginx tool to manually maintain HTTPS-related configurations, but requires additional pre-prepared signing certificates. Currently, certificate issuance is costly and requires the use of third-party tools, which carries risks in learning and using. Therefore, a new solution is urgently needed to assist in building an HTTPS environment. Summary of the Invention

[0006] In view of this, embodiments of the present invention provide a method, apparatus and computer program product for building a front-end HTTPS protocol environment, so as to eliminate or improve one or more defects existing in the prior art, and solve the problem that the process of building an HTTPS environment in the development process of the prior art is complicated and costly.

[0007] One aspect of the present invention provides a method for setting up a front-end HTTPS protocol environment, the method comprising the following steps:

[0008] The front-end service collects the certificate configuration form entered by the user through an interactive interface provided by a preset front-end framework; the certificate configuration form records the content required to generate the certificate, including certificate holder identification information, encryption and signature verification information, validity period control information, version serial number information, and certificate chain information; the certificate is used to enable HTTPS service;

[0009] The certificate configuration form is validated for correctness based on preset validation criteria. If the validation passes, a certificate generator type is selected and a certificate generation request is sent to the backend service.

[0010] In response to a certificate generation request, the backend service generates key data and forms a certificate and usage instructions according to the certificate configuration form using the selected certificate generator type. The certificate and usage instructions are stored locally to generate a corresponding download address. The backend service deploys various system dependencies for the certificate generator to call.

[0011] The front-end service reads the certificate and the instructions for use through the interface provided by the back-end service, displays the information based on the interactive interface, updates the certificate list, and provides the download address to the user.

[0012] In some embodiments, the preset front-end framework is built using the Vue progressive framework, the webpack static module bundler, and the elementui component; the back-end service is built using the Koa technology framework based on Node.js, relying on the openssl certificate generator, the mkcert certificate generator, and the node-forge certificate generator; the back-end service provides system dependencies for the openssl certificate generator based on the OpenSSL binary program, provides system dependencies for the mkcert certificate generator based on the Node.js dependency package mkcert binary program, and provides dependencies for the node-forge certificate generator based on the Node.js dependency package.

[0013] In some embodiments, the preset front-end framework is further built using the React framework, Angular framework, and / or Svelte framework;

[0014] The method further includes: invoking the React framework, the Angular framework, or the Svelte framework in response to a user's front-end framework selection instruction.

[0015] In some embodiments, after the backend service generates key data and forms a certificate according to the certificate configuration form using the selected certificate generator type, it also generates and synchronously stores certificate usage instructions, which include:

[0016] Basic certificate information used to indicate the certificate format and validity period;

[0017] Installation configuration information used to indicate the location of the certificate file, server configuration parameters, and installation operations;

[0018] This is used to display configuration information and usage examples for the certificate.

[0019] In addition, information on common problems and solutions for ensuring the operation of the certificate.

[0020] In some embodiments, the method further includes: checking and monitoring the validity period of the certificates stored locally at set intervals; if an expired certificate is found, generating a prompt alarm message and displaying it in the certificate list based on the interactive interface.

[0021] In some embodiments, the method further includes: establishing a relational database to store the certificate and its corresponding user manual, and establishing a query directory to retrieve the certificate and its corresponding user manual;

[0022] A hash value is calculated for the certificate and its corresponding instructions for use, and stored in a preset blockchain network via a preset link. During the calling and querying process, the hash value is retrieved by searching the blockchain network to verify the data integrity of the certificate and its corresponding instructions for use.

[0023] In some embodiments, the method further includes: receiving certificate error messages from users based on the interactive interface, and correcting or regenerating the erroneous certificate based on preset handling rules;

[0024] A log is established to record the process of generating, reading, displaying, downloading, and error feedback of the certificate, and to characterize the running status based on preset statistical features.

[0025] On the other hand, the present invention also provides a front-end HTTPS protocol environment building device, including a processor, a memory, and a computer program / instructions stored in the memory. The processor is used to execute the computer program / instructions, and when the computer program / instructions are executed, the device / implements the steps of the above method.

[0026] On the other hand, the present invention also provides a computer-readable storage medium having a computer program / instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0027] On the other hand, the present invention also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described method.

[0028] The front-end HTTPS protocol environment setup method, apparatus, and computer program product described in this invention collects user-entered certificate configuration forms through a front-end service based on a preset framework. These forms cover key information such as certificate holder, issuer, cryptographic signature, validity period, version serial number, and certificate chain. The system verifies the form's correctness according to preset verification standards, ensuring the accuracy and compliance of the input information. After successful verification, the front-end service selects an appropriate certificate generator type and sends a request to the back-end service. The back-end service utilizes various deployed system dependencies to generate key data and certificates according to the configuration form using the selected generator, stores the certificates locally, and generates download addresses and usage instructions, achieving automated certificate generation and management. The front-end service reads certificates through interfaces provided by the back-end, updates the certificate list, and displays it on the interactive interface, providing intuitive certificate information display and a convenient download entry. This method significantly lowers the technical threshold for setting up an HTTPS environment, allowing developers to quickly complete environment setup without needing in-depth understanding of certificate configuration details. Simultaneously, by integrating multiple certificate generator types, it meets the needs of different scenarios and improves development efficiency. The local storage and management functions of certificates facilitate unified maintenance and access, and the visual interface simplifies the certificate usage process. Overall, this invention greatly improves the efficiency and ease of setting up an HTTPS environment in front-end development, and provides strong assurance for the consistency of development, testing and production environments.

[0029] Additional advantages, objects, and features of the invention will be set forth in part in the description which follows, and will also become apparent in part to those skilled in the art upon studying the description, or may be learned by practice of the invention. The objects and other advantages of the invention can be realized and obtained by means of the structures specifically pointed out in the specification and drawings.

[0030] Those skilled in the art will understand that the objectives and advantages achievable with this invention are not limited to those specifically described above, and that the above and other objectives achievable with this invention will become clearer from the following detailed description. Attached Figure Description

[0031] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, are not intended to limit the scope of the invention. In the drawings:

[0032] Figure 1 This is a flowchart illustrating the method for setting up a front-end HTTPS protocol environment according to an embodiment of the present invention.

[0033] Figure 2 This is a technical framework diagram of a front-end HTTPS protocol environment setup method according to an embodiment of the present invention.

[0034] Figure 3This is a functional framework diagram of a front-end HTTPS protocol environment setup method according to an embodiment of the present invention.

[0035] Figure 4 This is a schematic diagram of the certificate generation logic of the front-end HTTPS protocol environment construction method according to an embodiment of the present invention.

[0036] Figure 5 This is a schematic diagram of the service deployment structure of the front-end HTTPS protocol environment building method according to an embodiment of the present invention. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the embodiments and accompanying drawings. Here, the illustrative embodiments and descriptions of this invention are used to explain the invention, but are not intended to limit the invention.

[0038] It should also be noted that, in order to avoid obscuring the invention with unnecessary details, only the structures and / or processing steps closely related to the solution according to the invention are shown in the accompanying drawings, while other details that are not closely related to the invention are omitted.

[0039] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, element, step, or component, but does not exclude the presence or addition of one or more other features, elements, steps, or components.

[0040] Existing technologies primarily rely on local front-end development servers or middleware such as Nginx to configure HTTPS environments, but these methods suffer from numerous problems. Certificates generated by local development servers cannot be reused and have limited functionality, making it difficult to meet the needs of complex business scenarios. While configuring SSL certificates using middleware like Nginx is feasible, it is costly, technically complex, and unfriendly to developers. These issues result in high costs and low efficiency in setting up HTTPS environments during the development phase, and make it difficult to ensure consistency between development and production environments, affecting the stable operation of applications. This invention primarily addresses the issue of high HTTPS environment costs in business verification or problem-solving scenarios in actual business applications. By providing a one-stop service for HTTPS environment dependencies, it assists front-end developers and other developers in quickly setting up HTTPS environments, reducing the cost of requirement iteration.

[0041] Specifically, this invention provides a method for setting up a front-end HTTPS protocol environment, such as... Figure 1 As shown, the method includes the following steps S101~S104:

[0042] Step S101: The front-end service collects the certificate configuration form entered by the user based on the interactive interface provided by the preset front-end framework; the certificate configuration form records the content required to generate the certificate, including certificate holder identification information, encryption and signature verification information, validity period control information, version serial number information and certificate chain information; the certificate is used to enable HTTPS service.

[0043] Step S102: Verify the correctness of the certificate configuration form based on the preset verification standard. If the verification is successful, select the certificate generator type and send a certificate generation request to the backend service.

[0044] Step S103: In response to the certificate generation request, the backend service generates key data and forms a certificate and usage instructions according to the certificate configuration form based on the selected certificate generator type. The certificate and usage instructions are stored locally and a corresponding download address is generated. The backend service deploys various system dependencies for the certificate generator to call.

[0045] Step S104: The front-end service reads the certificate and usage instructions through the interface provided by the back-end service, displays the information based on the interactive interface, updates the certificate list, and provides the download address to the user.

[0046] In step S101, the preset front-end framework is built using the Vue progressive framework, webpack static module bundler, and elementui components to construct an intuitive form interface.

[0047] The content collected from the form fields corresponds to the standard content of the certificate. For example, the following content can be collected:

[0048] 1. Certificate holder identification information, including:

[0049] Common Name (CN): The primary domain name.

[0050] Subject Alternative Name (SAN): The most critical field in modern certificates, this multi-line input box allows a certificate to be associated with multiple domain names or IP addresses. This support for multiple domain names makes SANs highly flexible in practical applications, especially in scenarios where services need to be provided for multiple related domain names.

[0051] Organization (O) represents the name of the certificate holder's organization, such as "ABC Company Ltd." This is typically used in formal corporate certificates to indicate the certificate's affiliation with a specific organization.

[0052] Organizational Unit (OU) refers to a department or unit within an organization, such as "IT Department". Used in conjunction with Organization (O), it provides a more specific location for the certificate within the organizational structure. Locality (L) indicates the region or city where the certificate holder is located, such as "Beijing". This helps provide more detailed geographic location information in the certificate. State (ST) represents the state or province where the certificate holder is located, such as "California". Together with Locality (L), it provides a more precise geographic location. Country (C) uses a two-letter code to indicate the country where the certificate holder is located, such as "CN China". This information is required for generating more formal corporate certificates, especially for internal CAs.

[0053] 2. Encryption and signature verification information are selected by the user through an interactive interface, including the key algorithm and signature algorithm. The key algorithm can be RSA 2048, RSA 4096, ECDSA P-256, etc. The signature algorithm can be SHA256With RSA or SHA384With ECDSA.

[0054] 3. Expiry date control information can be selected by the user through an interactive interface.

[0055] 4. Version serial number information can be set according to requirements.

[0056] 5. Certificate chain information is a collection of certificates, starting with the terminal entity certificate (such as a server certificate) and verifying them sequentially up to the next higher-level CA certificate until the root certificate is found. It contains key information such as the issuer key identifier, subject key identifier, CRL distribution point, and OCSP, used to verify the legitimacy and trustworthiness of the certificates, ensuring that the final certificate is trustworthy.

[0057] In some business development embodiments, the supported preset front-end frameworks also include frameworks such as React, Angular, and / or Svelte for building; correspondingly, the method also includes: invoking the React, Angular, or Svelte framework in response to the user's front-end framework selection instruction.

[0058] In step S102, the front-end performs real-time verification of the certificate configuration form, which can specifically adopt the X.509 standard. This mainly includes format verification, mandatory field verification, and logical verification. For example, it verifies whether the CN and SAN fields conform to the domain name or IP address format, checks to ensure that key fields are filled in, and verifies whether the validity period is reasonable. After successful verification, based on the generator type selected by the user, the front-end serializes all configuration information in the form into a JSON object. This JSON object is then sent to the back-end service via an HTTP request, i.e., a certificate generation request.

[0059] In step S103, the backend service is built using an external certificate generator (openssl), a Node.js-based mkcert certificate generator, and a node-forge certificate generator). The backend service provides system dependencies for the openssl certificate generator based on the OpenSSL binary program, for the mkcert certificate generator based on the mkcert binary program, and for the node-forge certificate generator based on the Node.js dependency package.

[0060] After receiving the request, the backend service performs even stricter security and logic checks to prevent malicious requests that bypass the frontend. Based on the certificate generator type selected in the request, the task is distributed to the corresponding processing module. The OpenSSL module constructs command-line arguments, calls the system-installed openssl command, and executes it through a child process. It is suitable for complex scenarios. The mkcert module uses the mkcert Node dependency package as a library; its advantage is automatic trust, making it ideal for local development. The node-forge module is implemented purely in Node.js and requires no system dependencies. Using the node-forge npm library, certificates and keys are generated directly through code, making it ideal for automated integration and CI / CD.

[0061] During the generation and storage process, the aforementioned tools are invoked to generate an X.509 certificate and private key in memory based on the configuration information received from the front end. The generated certificate and private key files are written to the server's disk, using a secure directory structure and file permissions. Metadata such as the certificate's CN, SAN, validity period, file storage path, creator, and status are persisted to a database, such as MySQL. Based on the certificate type and the target environment (Nginx, front-end technology framework, etc.), a corresponding template is retrieved from a pre-built configuration template library, and variables such as the certificate and key storage path are populated to dynamically generate a ready-to-use user manual. After successful generation, the backend returns the new certificate's ID, status, and other information to the front end.

[0062] In some embodiments, after the backend service generates key data and forms a certificate according to the certificate configuration form using the selected certificate generator type, it also generates and synchronously stores certificate usage instructions. The certificate usage instructions include: basic certificate information to indicate the certificate format and validity period; installation configuration information to indicate the certificate file placement path, server configuration parameters and installation operations; configuration information and usage examples to prompt certificate usage; and information on common problems and solutions to ensure certificate operation.

[0063] In step S104, the frontend automatically calls the backend interface (e.g., GET / api / certificates) to obtain and display a brief list of information for all certificates (name, domain, validity period, status, etc.). Users can filter by project, environment, and status. After a user clicks on a certificate, the frontend calls the details interface (e.g., GET / api / certificates / :id). The backend reads the complete metadata of the certificate from the database and file system, and may even parse the certificate file content (e.g., using openssl x509-text or node-forge libraries), returning information (e.g., issuer, serial number, fingerprint, etc.) to the frontend for detailed display. This visualizes "certificate chain information," etc. On the details page, the dynamic configuration guide generated in step S103 is clearly displayed to the user, who can directly copy and paste it into their Nginx configuration or configuration file.

[0064] The front-end page provides a "Download" button. Clicking this button calls the back-end download API, for example, GET / api / certificates / :id / download. Upon receiving the request, the back-end retrieves the file path from the database based on the certificate ID, reads the certificate and key files, typically packages them into a ZIP archive, and then sends them to the browser as a file stream. Simultaneously, the back-end logs a "Download" audit entry for easy tracking.

[0065] In some embodiments, the method further includes step S105: checking and monitoring the validity period of locally stored certificates according to a set interval period; if an expired certificate is found, generating a prompt alarm message and displaying it in the certificate list based on the interactive interface.

[0066] The system deploys a scheduled task in the backend to automatically perform a check at set time intervals. Each time the task starts, it systematically scans the database for all certificate records marked as "valid," comparing the "expiration time" field of each certificate with the current server time. Based on the comparison results, the system performs different operations:

[0067] When an expired certificate is detected, the system will immediately and automatically update the status of any certificate whose expiration date is later than the current time from "valid" to "expired". When a certificate about to expire is detected, the system will identify those with recent expiration dates, such as those within 7 days. These certificates, although currently valid, are already in a high-risk state.

[0068] On the platform's front-end certificate list page, expired and soon-to-expire certificates are clearly marked, for example, their rows will be displayed with a red or yellow background, or accompanied by a prominent warning icon. Users can immediately see the risk points upon entering the system. To ensure alerts are noticed promptly, the system can also integrate email or team communication tools, such as DingTalk or WeChat Work. Once a risky certificate is detected, the system will automatically send a notification message to the certificate's creator or project manager, urging them to handle it as soon as possible.

[0069] In some embodiments, the method further includes step S106: establishing a relational database to store certificates and their corresponding usage instructions, and establishing a query directory to retrieve certificates and their corresponding usage instructions.

[0070] The relational database can be MySQL or PostgreSQL. This database doesn't directly store the certificate files themselves, but rather meticulously stores all the metadata for each certificate, such as the certificate name, bound domain, creator, creation and expiration dates, status, and most importantly, the file storage path. Simultaneously, the configuration and usage instructions generated by the system for different server software (such as Nginx and Apache) are also stored and managed in a structured manner. Based on this database, the platform frontend provides a powerful query interface, often called a "query directory." Users can quickly filter and search by combining various conditions (such as project name, domain name, validity period, status, etc.), thereby accurately locating the desired object from a massive number of certificates.

[0071] The hash value of the certificate and its corresponding instructions for use is calculated and stored in a preset blockchain network through a preset link. During the call and query process, the hash value is retrieved by searching the blockchain network to verify the data integrity of the certificate and its corresponding instructions for use.

[0072] To prevent malicious or accidental tampering of certificate files or user manuals after generation, the system employs blockchain technology for evidence preservation. Whenever a new certificate and its user manual are generated and saved, the system immediately calculates a unique digital fingerprint, or cryptographic hash value, for their complete content. Subsequently, the system sends this digital fingerprint, the certificate's unique number, and the current timestamp, through a secure interface and permanently records it in a pre-defined blockchain network, which can be a public or consortium blockchain. The characteristics of blockchain ensure that these records cannot be altered once written and are time-secure. When the integrity of a certificate needs to be verified, such as during a security check before deployment to a production environment, the system recalculates the current digital fingerprint of the certificate file and retrieves the original fingerprint recorded on the blockchain. The two are compared; if they match perfectly, the document is undamaged; if they do not match, the document has been tampered with, and the system immediately issues a serious security alert.

[0073] In some embodiments, the method further includes step S107: receiving certificate error messages from users based on the interactive interface, and correcting or regenerating the erroneous certificate based on preset handling rules.

[0074] The platform provides a user feedback portal on the details page of each certificate. When users encounter problems using certificates, such as distrust in a certain browser or service startup failure after configuration, they can submit a detailed error description and even screenshots through this portal. After receiving the feedback, the system will attempt to handle it automatically based on a preset rule base. For example, if the feedback information contains keywords such as certificate expiration, the system can automatically identify and suggest renewal to the user; if the feedback is a specific configuration error, the system can automatically provide correction suggestions. For complex problems that cannot be handled automatically, the feedback will be generated into a work order and transferred to maintenance personnel for manual handling.

[0075] In some embodiments, the method further includes step S108: establishing a log to record the generation, reading, display, downloading and error feedback processes of certificates, and characterizing the running status based on preset statistical features.

[0076] The system meticulously records every critical operation event that occurs on the platform, including but not limited to: certificate generation, viewing, downloading, deletion, and every user feedback. Each log entry contains complete information about the specific subject's certificate operations.

[0077] All this log data constitutes a health check report for the platform's operation. Based on this data, the system can generate intuitive charts and reports using pre-defined statistical models to characterize its operational status. For example, it can provide a platform usage overview, displaying the total number of certificates, daily generation trends, and the most frequently used generation tools. It can also check system health by viewing the distribution ratio of valid, alarming, and expired certificates. Furthermore, it can analyze user behavior, including the most active users and the most common operation types. Finally, it can identify problem clusters, such as which types of certificates or configurations are most prone to issues and generate the most feedback.

[0078] On the other hand, the present invention also provides a front-end HTTPS protocol environment building device, including a processor, a memory, and a computer program / instructions stored in the memory. The processor is used to execute the computer program / instructions, and when the computer program / instructions are executed, the device / implements the steps of the above method.

[0079] On the other hand, the present invention also provides a computer-readable storage medium having a computer program / instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0080] On the other hand, the present invention also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described method.

[0081] The solution provided by this invention mainly focuses on providing one-stop assistance, specifically, such as... Figure 2 and Figure 3 As shown, this solution includes a front-end page service and a back-end service. The front-end service accepts user certificate configuration input, and the back-end service generates the required certificate. The front-end service provides a certificate download entry point, and the back-end service provides a corresponding interface to respond to the download. The front-end service provides a display page showing how to configure and use the certificate on different tools. The service supports multiple certificate generation capabilities and can respond to front-end certificate generation capability configuration options. The technology stack used in this solution is all JavaScript / Node.js. The front-end service mainly uses Vue, Webpack, and Element UI, while the back-end service mainly uses Node.js, Koa, and Node.js Forge.

[0082] The front-end service primarily uses Vue-based technologies to provide page functionality. The back-end service mainly uses Koa and other technologies to implement service functions. Additionally, certificate generation offers three capabilities: using an external OpenSSL service, and using Node.js's mkcert and Node.js Forge solutions. Once generated, certificates will be stored in a specified directory, supporting functions such as viewing and downloading certificate information. The front-end and back-end are independent, therefore requiring separate deployment. The front-end page access functionality is deployed using the ` / ` prefix, while the back-end context consistently uses ` / api` as the prefix.

[0083] like Figure 4 and Figure 5 As shown, the front-end's main functions include certificate configuration information entry, certificate generation capability selection, certificate information display, and usage instructions. The back-end's main functions include certificate generation, certificate management, and system tools. Certificate generation supports three capabilities: openSSL, mkcert, and node-forge. It also provides certificate information viewing and downloading. OpenSSL is powerful with many parameters, supporting various certificate customization operations, but requires manual management of the CA and certificate trust, making it suitable for internal CAs and scenarios with complex custom parameters. mkcert encapsulates OpenSSL and system trust operations, allowing the browser to trust the certificate; it is not suitable for complex parameter scenarios and is mainly used in local development and testing environments. node-forge is implemented based on pure JavaScript, supporting basic operations such as self-signing and signing, but requires manual management of the CA and certificate trust, making it suitable for local development, testing, and automation scenarios.

[0084] The certificate generation logic of this invention involves both front-end and back-end services. The front-end supports configuring certificate information through a page and performs preliminary verification of user-submitted content. The back-end, based on the user's input information and certificate capabilities, first verifies the user's input content, performs further verification, and then calls the corresponding capabilities to generate the appropriate certificate, facilitating subsequent certificate viewing, downloading, and deletion operations for the user.

[0085] This feature involves both front-end pages and back-end functionality, and since the front-end and back-end are independent, separate front-end and back-end services need to be deployed. The deployment context for the front-end page access functionality is " / ", while the back-end context uses " / api" as the prefix.

[0086] The effects of this invention include:

[0087] 1. Lower the barrier to HTTPS development, reduce the cost for teams and developers who need to use certificates to learn how to configure environment parameters, and summarize the current mainstream solutions so that they can be used as needed. Even beginners who are not familiar with setting up an HTTPS environment can quickly get started and deploy it.

[0088] 2. Improved development efficiency: Automated certificate generation, download, and guidance, eliminating the need for each developer to study and configure individually. Team members can use their own certificates according to their own characteristics. The entry point is unified, supporting multiple environments and project configurations, saving significant communication and documentation costs.

[0089] 3. Knowledge Accumulation: Includes built-in configuration guides for various frameworks, and summarizes and provides solutions to problems encountered during use. Future updates can expand on the principles of certificate usage and related knowledge, facilitating a deeper understanding for certificate users.

[0090] 4. Unified certificate management and lifecycle: The solution supports unified parameter management and customized requirements for different certificate generation capabilities. It also provides unified management functions for generated certificates, such as certificate validity period, expiration reminders, regeneration, and revocation, as well as certificate viewing, exporting, and distribution, offering full-process management capabilities across different lifecycles.

[0091] 5. Supports CI / CD testing and can be integrated with other automation functions to issue temporary certificates for automated testing and CI / CD. In the future, it can support API certificate generation, which is convenient for use in scripted automation scenarios.

[0092] 6. It facilitates future expansion, supports the integration of new tools, or works in conjunction with public certificate authorities (CAs) to achieve automated distribution functions, etc.

[0093] In summary, the front-end HTTPS protocol environment setup method, apparatus, and computer program product described in this invention provide page and back-end generation functions, integrating current mainstream certificate generation methods such as OpenSSL, mkcert, and node-forege. Users can select specific capabilities to generate certificates according to their development needs and requirements. After entering relevant parameters on the page, certificates can be generated with one click, and users can view, download, and access usage instructions. Subsequent certificate management can be unified, including functions such as viewing, downloading, expiration reminders, and re-signing, and can be combined with other tools or automation functions to achieve visualized one-click management. This reduces the cost of certificate usage and environment configuration. This invention enables one-stop development of certificate generation and configuration, unified certificate lifecycle and visualized one-click management, and supports multi-parameter, scalable service configuration.

[0094] This invention enables unified integration of multiple certificate generation capabilities. A single platform supports various certificate generation tools through a front-end visual interface, and outputs standardized certificate results. Users can choose the generation method and complete the entire certificate generation process by performing related operations on the page. Services can also provide automated scripts to fulfill corresponding requirements through APIs and other scripting capabilities. It provides certificate configuration and usage guidance for various environments. After certificate generation, it automatically matches various front-end and back-end service frameworks, providing HTTPS configuration guidance and outputting configuration snippets for various development environments, integrating certificate generation and usage methods. It offers visualized certificate lifecycle management and one-click management capabilities, currently supporting full lifecycle management such as generation, viewing, downloading, and revocation, as well as different types of operations at different stages. All content can be managed through the page, allowing for certificate management across all lifecycle states.

[0095] Those skilled in the art will understand that the exemplary components, systems, and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software, or a combination of both. Whether implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention. When implemented in hardware, it can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this invention are programs or code segments used to perform the desired tasks. The programs or code segments can be stored in a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried in a carrier wave.

[0096] It should be clarified that the present invention is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of the present invention.

[0097] In this invention, features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, and / or combined with or in place of features of other embodiments.

[0098] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, various modifications and variations of the embodiments of the present invention are possible. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for setting up a front-end HTTPS protocol environment, characterized in that, The method includes the following steps: The front-end service collects the certificate configuration form entered by the user through an interactive interface provided by a preset front-end framework; the certificate configuration form records the content required to generate the certificate, including certificate holder identification information, encryption and signature verification information, validity period control information, version serial number information, and certificate chain information; the certificate is used to enable HTTPS service; The certificate configuration form is validated for correctness based on preset validation criteria. If the validation passes, a certificate generator type is selected and a certificate generation request is sent to the backend service. In response to a certificate generation request, the backend service generates key data and forms a certificate and usage instructions according to the certificate configuration form using the selected certificate generator type. The certificate and usage instructions are stored locally to generate a corresponding download address. The backend service deploys various system dependencies for the certificate generator to call. The front-end service reads the certificate and the instructions for use through the interface provided by the back-end service, displays the information based on the interactive interface, updates the certificate list, and provides the download address to the user; The preset front-end framework is built using the Vue progressive framework, webpack static module bundler, and elementui components; the back-end service is built using the Koa technology framework based on Node.js, relying on openssl certificate generator, mkcert certificate generator, and node-forge certificate generator. The preset front-end framework is also built using the React framework, Angular framework and / or Svelte framework. The method further includes: invoking the React framework, the Angular framework, or the Svelte framework in response to a user's front-end framework selection instruction.

2. The method for setting up a front-end HTTPS protocol environment according to claim 1, characterized in that, After the backend service generates key data and forms a certificate according to the certificate configuration form using the selected certificate generator type, it also generates and synchronously stores certificate usage instructions, which include: Basic certificate information used to indicate the certificate format and validity period; Installation configuration information used to indicate the location of the certificate file, server configuration parameters, and installation operations; This is used to display configuration information and usage examples for the certificate. In addition, information on common problems and solutions for ensuring the operation of the certificate.

3. The method for setting up a front-end HTTPS protocol environment according to claim 1, characterized in that, The method further includes: checking and monitoring the validity period of the certificates stored locally at set intervals; if an expired certificate is found, generating a prompt alarm message and displaying it in the certificate list based on the interactive interface.

4. The method for setting up a front-end HTTPS protocol environment according to claim 2, characterized in that, The method further includes: establishing a relational database to store the certificate and its corresponding user manual, and establishing a query directory to retrieve the certificate and its corresponding user manual; A hash value is calculated for the certificate and its corresponding instructions for use, and stored in a preset blockchain network via a preset link. During the calling and querying process, the hash value is retrieved by searching the blockchain network to verify the data integrity of the certificate and its corresponding instructions for use.

5. The method for setting up a front-end HTTPS protocol environment according to claim 1, characterized in that, The method further includes: receiving certificate error messages from users based on the interactive interface, and correcting or regenerating the erroneous certificate based on preset handling rules; A log is established to record the process of generating, reading, displaying, downloading, and error feedback of the certificate, and to characterize the running status based on preset statistical features.

6. A front-end HTTPS protocol environment setup device, comprising a processor, a memory, and computer programs / instructions stored in the memory, characterized in that, The processor is configured to execute the computer program / instructions, and when the computer program / instructions are executed, the device / implements the steps of the method as described in any one of claims 1 to 5.

7. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method as described in any one of claims 1 to 5.

8. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method according to any one of claims 1 to 5.

Images