Chapter 5. Registration Authority
134
The RA also supports a range of reusable Perl objects. This enables administrators to build their own
enrollment work flow.
5.1.3. Roles
The RA currently supports the following roles:
• End Users — people who submit enrollment requests
• RA Agents — privileged RA users. They are responsible for daily operations such as request
approval.
• Administrator — the person responsible for installing and configuring the RA. An Administrator has
the necessary privileges to issue RA Agent status to End Users.
5.1.4. Interfaces
The RA provides three main interfaces: End User (or End Entity, EE); Agent; and Administrator.
5.1.4.1. End User Interface
The End User interface provides the following enrollment options:
SCEP Enrollment
In a SCEP enrollment scenario, you use the EE interface to submit a request in order to retrieve a
one-time PIN. The RA agent is notified of the request and, after validating the requestor, approves
it. Approving the request generates a PIN.
The manager gives this PIN to the router installer. On the router, the installer enters the URL to the
RA and provides the one-time PIN. The enrollment can then be initiated.
Enrolling a Server Certificate
In a server certificate enrollment scenario, a server administrator provides site information and the
server certificate request in the enrollment form. The RA Agent is notified of the request and, after
validating the requestor, approves it.
The request is then forwarded from the RA to the CA, which in turn generates a certificate and
returns it to the RA. The RA sends a notification to the server administrator who collects the
certificate by following a URL provided in the notification (typically an email).
Enrolling a User Certificate
In a user certificate enrollment scenario, the user accesses an enrollment page where user
information is collected, and key generation is initiated. The RA Agent is notified of the request
and, after validating the requestor, approves it.
The RA sends a notification to the user, who then collects the certificate by visiting a specified
URL.
In addition to enrolling user certificates, you can use the end entity interface to renew a valid user
certificate in your browser. The renewal feature reuses the keys and the CSR of the selected user
certificate to generate a new certificate.
Содержание CERTIFICATE SYSTEM 7.3 - ADMINISTRATION
Страница 1: ...Red Hat Certificate System 7 3 Administration Guide Publication date May 2007 updated March 25 2010 ...
Страница 15: ...xv Index 525 ...
Страница 16: ...xvi ...
Страница 38: ...Chapter 1 Overview 16 Figure 1 4 Certificate System Architecture ...
Страница 82: ...Chapter 2 Installation and Configuration 60 rpm ev rhpki manage ...
Страница 154: ...132 ...
Страница 194: ...172 ...
Страница 238: ...216 ...
Страница 244: ...222 ...
Страница 246: ...224 ...
Страница 286: ...264 ...
Страница 292: ...270 ...
Страница 318: ...Chapter 13 Certificate Profiles 296 Parameter IssuerType_n IssuerName_n ...
Страница 321: ...Freshest CRL Extension Default 299 Parameter PointName_n PointIssuerName_n ...
Страница 371: ...Configuring Mappers 349 Figure 15 9 Selecting a New Mapper Type 6 Edit the mapper instance and click OK ...
Страница 398: ...376 ...
Страница 412: ...390 ...
Страница 472: ...450 ...
Страница 500: ...Appendix A Certificate and CRL Extensions 478 Parameter namen Table A 8 IssuerAlternativeName Configuration Parameters ...
Страница 506: ...484 ...
Страница 528: ...506 ...
Страница 546: ...524 ...