Connected: An Internet Encyclopedia
RFC 1422 - 3.4.1.2 User Registration

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1422
Up: 3. Architecture
Up: 3.4 Roles and Responsibilities
Up: 3.4.1 Users and User Agents
Prev: 3.4.1.1 Generating and Protecting Component Pairs
Next: 3.4.1.3 CRL Management

### 3.4.1.2 User Registration

Most details of user registration are a local matter, subject to policies established by the user's CA and the PCA under which that CA has been certified. In general a user must provide, at a minimum, his public component and distinguished name to a CA, or a representative thereof, for inclusion in the user's certificate. (The user also might provide a complete certificate, minus the signature, as described in RFC 1424.) The CA will employ some means, specified by the CA in accordance with the policy of its PCA, to validate the user's claimed identity and to ensure that the public component provided is associated with the user whose distinguished name is to be bound into the certificate. (In the case of PERSONA certificates, described below, the procedure is a bit different.) The certifying authority generates a certificate containing the user's distinguished name and public component, the authority's distinguished name and other information (see Section 3.3) and signs the result using the private component of the authority.

Next: 3.4.1.3 CRL Management

Connected: An Internet Encyclopedia
RFC 1422 - 3.4.1.2 User Registration