File-Signing Input; Image Input; Key Generation Input; Nshkeycertrequest (Token Key) Input - Red Hat CERTIFICATE SYSTEM 8.0 - ADMINISTRATION Admin Manual

Hide thumbs Also See for CERTIFICATE SYSTEM 8.0 - ADMINISTRATION:
Table of Contents

Advertisement

Appendix A. Certificate Profile Input and Output Reference
A.1.4. File-Signing Input
The File-Signing input sets the fields to sign a file to show it has not been tampered with.
This input creates the following fields:
• Key Generation Request Type. This field is a read-only field displaying crmf as the request type.
• Key Generation Request. This input adds a drop-down menu to select the key size to use in the
key generation request.
• URL Of File Being Signed. This gives the location of the file which is to be signed.
• Text Being Signed. This gives the filename.
A.1.5. Image Input
The Image input sets the field to sign an image file. The only field which this input creates is Image
URL, which gives the location of the image which is to be signed.
A.1.6. Key Generation Input
The Key Generation input is used for enrollments in which a single key pair will be generated,
generally user-based certificate enrollments.
This input puts the following fields into the enrollment form:
• Key Generation Request Type. This field is a read-only field displaying crmf as the request type.
• Key Generation Request. This input adds a drop-down menu to select the key size to use in the
key generation request.
A.1.7. nsHKeyCertRequest (Token Key) Input
The Token Key input is used to enroll keys for hardware tokens for agents to use later for certificate-
based authentication.
This input puts the following fields into the enrollment form:
• Token Key CUID. This field gives the CUID (contextually unique user ID) for the token device.
• Token Key User Public Key. This field must contain the token user's public key.
A.1.8. nsNKeyCertRequest (Token User Key) Input
The Token User Key input is used to enroll keys for the user of a hardware token, for agents to use the
token later for certificate-based authentication. This input puts the following fields into the enrollment
form:
• Token Key User UID. This field gives the UID for the LDAP entry of the user of the token device.
• Token Key User Public Key. This field must contain the token user's public key.
420

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the CERTIFICATE SYSTEM 8.0 - ADMINISTRATION and is the answer not in the manual?

Table of Contents