GM/T 0089-2020Simple certificate enrollment protocol specification (English PDF)

Foreword

This document is drafted in accordance with GB/T 1.1-2020 "Directives for standardization - Part 1: Rules for the structure and drafting of standardizing documents".

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The issuing authority of this document shall not be held responsible for identifying any or all such patent rights.

This document was proposed by and shall be under the jurisdiction of Cryptography Standardization Technical Committee.

Drafting organizations of this document. Changchun Jilin University Zhengyuan Information Technologies Co., Ltd., Beijing Infosec Technologies Co., Ltd., Koal Software Co., Ltd., Westone Information Industry INC., Feitian Technologies Co., Ltd., Beijing Certificate Authority Co., Ltd., Xingtang Telecommunications Technology Co., Ltd., Shanghai Electronic Certification Authority Co., Ltd., Beijing WatchSmart Technologies Co., Ltd., Beijing HuaDa ZhiBao Electronic System Co., Ltd., Beijing Creative Century Technology Co., Ltd., Shandong Dean Information Technology Co., Ltd.

Main drafters of this document. Zhao Lili, Zhang Qingyong, Zheng Qiang, Zhang Liting, Luo Jun, Zhu Pengfei, Fu Dapeng, Wang Nina, Han Wei, Wang Xuelin, Zhang Yuan, Chen Baoru, Wang Xiaochen, Ma Hongfu.

1 Scope

This document defines a simple protocol for certificate enrollment using the SM2 algorithm.

This document is applicable to guiding the development of a digital certificate authentication system that provides automatic certificate enrollment, as well as the use of SM2 algorithm for automatic enrollment of device certificates.

2 Normative references

The contents of the following documents, through normative references in this text, constitute indispensable provisions of this document. Among them, for dated references, only the edition corresponding to that date applies to this document. For undated references, the latest edition (including all amendments) applies to this document.

GB/T 20518-2018 Information security technology - Public key infrastructure - Digital certificate format GB/T 32918 (all parts) Information security technology - Public key cryptographic algorithm SM2 based on elliptic curves GB/T 35275-2017 Information security technology - SM2 cryptographic algorithm encrypted signature message syntax specification GM/T 0092 Specification of certificate request syntax based on SM2 cryptographic algorithm GM/Z 4001 Cryptology Terminology

3 Terms and definitions

The terms and definitions defined by GM/Z 4001 and the following ones apply to this document.

Client

The device which applies for certificate service.

Note. The client is also called the requester.

Server

The entities which provide certificate services, including CA and RA.

Digital envelope

A data structure which contains a ciphertext encrypted with a symmetric key and the symmetric key encrypted with a public key.

4 Abbreviations

The following abbreviations apply to this document.

CA. Certification Authority CDP. CRL Distribution Point CGI. Common Gateway Interface

Foreword

This document is drafted in accordance with GB/T 1.1-2020 "Directives for standardization - Part 1: Rules for the structure and drafting of standardizing documents".

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The issuing authority of this document shall not be held responsible for identifying any or all such patent rights.

This document was proposed by and shall be under the jurisdiction of Cryptography Standardization Technical Committee.

Drafting organizations of this document. Changchun Jilin University Zhengyuan Information Technologies Co., Ltd., Beijing Infosec Technologies Co., Ltd., Koal Software Co., Ltd., Westone Information Industry INC., Feitian Technologies Co., Ltd., Beijing Certificate Authority Co., Ltd., Xingtang Telecommunications Technology Co., Ltd., Shanghai Electronic Certification Authority Co., Ltd., Beijing WatchSmart Technologies Co., Ltd., Beijing HuaDa ZhiBao Electronic System Co., Ltd., Beijing Creative Century Technology Co., Ltd., Shandong Dean Information Technology Co., Ltd.

Main drafters of this document. Zhao Lili, Zhang Qingyong, Zheng Qiang, Zhang Liting, Luo Jun, Zhu Pengfei, Fu Dapeng, Wang Nina, Han Wei, Wang Xuelin, Zhang Yuan, Chen Baoru, Wang Xiaochen, Ma Hongfu.

1 Scope

This document defines a simple protocol for certificate enrollment using the SM2 algorithm.

This document is applicable to guiding the development of a digital certificate authentication system that provides automatic certificate enrollment, as well as the use of SM2 algorithm for automatic enrollment of device certificates.

2 Normative references the contents of the following documents, through normative references in this text, constitute indispensable provisions of this document. Among them, for dated references, only the edition corresponding to that date applies to this document. For undated references, the latest edition (including all amendments) applies to this document.

GB/T 20518-2018 Information security technology - Public key infrastructure - Digital certificate format GB/T 32918 (all parts) Information security technology - Public key cryptographic algorithm SM2 based on elliptic curves GB/T 35275-2017 Information security technology - SM2 cryptographic algorithm encrypted signature message syntax specification GM/T 0092 Specification of certificate request syntax based on SM2 cryptographic algorithm GM/Z 4001 Cryptology Terminology

3 Terms and definitions the terms and definitions defined by GM/Z 4001 and the following ones apply to this document.

Client

The device which applies for certificate service.

Note. The client is also called the requester.

Server

The entities which provide certificate services, including CA and RA.

Digital envelope

A data structure which contains a ciphertext encrypted with a symmetric key and the symmetric key encrypted with a public key.

4 Abbreviations

The following abbreviations apply to this document.

CA. Certification Authority CDP. CRL Distribution Point CGI. Common Gateway Interface

5 SCEP function

5.1 SCEP entities

5.1.1 Overview

SCEP entities include client and server. The server is composed of CA and RA.

SCEP describes the protocol process and format of the client's enrollment and certification with the server. The entity relationship of SCEP is shown in Figure 1.

5.1.4 RA

RA is a kind of SCEP server. It performs certification and authorization checks on SCEP clients. At the same time, the certification request is forwarded to the CA. The name of the RA shall not appear in the issuer field of the generated certificate.

5.2 Client certification in order to encrypt and sign data according to the syntax format of GB/T 35275, the client shall have an available local certificate.

5.3 Enrollment certification the server can set a policy, to automatically or manually enroll and authenticate the client's request.

5.4 CA/RA certificate distribution If the client has not obtained a CA/RA certificate before, starting any PKI operation, it shall apply for a CA/RA certificate.

5.5 Certificate enrollment the client creates a certificate request according to GM/T 0092 to start the certificate enrollment transaction; and sends it to CA/RA after encapsulating it according to GB/T 35275.

5.7 CRL query

SCEP clients can obtain CRL through one of the following two methods.

5.8 Certificate revocation SCEP does not specify the method for requesting certificate revocation.

6 SCEP security message object

6.1 Overview

SCEP messages with confidentiality requirements adopt a two-layer structure, see GB/T 35275.By simultaneously applying digital envelope and digital signature, the end-to-end transaction information integrity and confidentiality of the information part of the SCEP message are protected.

6.2 SCEP message

6.2.1 SCEP message structure the basic structure of all secure SCEP message objects is the SCEP message.

This structure is composed of the SignedData type in GB/T 35275, as defined in 8.1 in GB/T 35275-2017.There are the following restrictions.

If there is a signed content (the CertRep message is in the SUCCESS status), the content shall be a pkcsPKIEnvelope structure and shall match the messageType attribute.

6.2.2 Signed transaction attributes

6.2.2.7 Signing time (signingTime) the signing time attribute specifies the time for the signer to perform the signing process. This attribute is optional. For its definition, please refer to PKCS#9.

6.3 SCEP message type

6.3.1 Overview

The type of SCEP message shall be specified in the messageType certification attribute. The following subclauses define valid message types, corresponding message data formats, and mandatory certification attributes of this type.

6.3.2 Certificate enrollment this type of MessageData domain contains a GM/T 0092 certificate request.

The certificate enrollment can include any domain defined in GM/T 0092; and shall contain at least the following items.

6.3.3 Certificate enrollment response

6.3.3.1 Overview

This type of messageData attribute contains a simplified SignedData as shown in 6.4.The exact content required for the response depends on the type of request for this message response, which is described in Table 1 and Clause 4.

In addition to the authenticatedAttributes required by valid GB/T 35275, pkiMessage shall also contain the following attributes.

6.3.3.2 Transaction success when the transaction status is set to SUCCESS, the messageData of this message contains a simplified digital envelope as defined in 6.4.Its content depends on the certificate enrollment request, as shown in Table 2.

6.4 Simplified SignedData data type the simplified SignedData data type refers to the simplification of the signed data type SignedData in GB/T 35275.It does not have a signer; is only used to transmit certificates and certificate revocation lists.

7 SCEP transaction

7.1 Obtain a CA certificate

7.1.1 Request message format in order to obtain the CA certificate, the client sends a GetCACert message to the server. There is no relevant data in this message.

7.2 Certificate enrollment

7.2.1 Request message format the PKCSReq message is used for certificate enrollment application.

Prerequisite. Both the client and the CA certification authority have completed the initialization process. The client has been configured with a CA/RA certificate.

7.2.2 Response message format the response message shall be a CertRep message returned by the server, which is divided into three status. SUCCESS, FAILURE, or PENDING.

7.3 Certificate polling

7.3.1 Request message format Triggered by a CertRep whose transaction status is PENDING, the client will periodically send GetCertInitial status query requests to the server, to enter the polling status; until the request is granted and the certificate is sent back; or the request is rejected; or the configured polling time limit (or maximum number of polls) is exceeded.

7.3.2 Response message format the response message of GetCertInitial is the same as in 7.2.2.

7.4 Certificate query

7.4.1 Request message format Through the name of the issuer and the certificate serial number of the certificate to be queried, the client can query the issued certificate from the SCEP server. This transaction is not used to provide general certificate directory services.

7.4.2 Response message format in this case, the CertRep on the server is the same as 7.2.2; except that the status returned by the server is only SUCCESS or FAILURE.

7.5 CRL query

7.5.1 Request message format the client can request the CRL from the SCEP server.

Prerequisite. The certificate of the certification authority has been downloaded to the end entity.

Post-condition. Send the CRL back to the client.

7.6 Obtain the next CA certificate

7.6.1 Request message format when the CA certificate is about to expire, the client needs to retrieve the new CA certificate of the CA that is about to be activated. This is done through the GetNextCACert message. This message has no related request data.

8 SCEP transmission protocol