Following are main steps to be taken when configuring the ADSS SCVP Service. The order in which the steps are defined is not important since it is easy to go back to an earlier step and also make changes later if required.


Steps

Description

Step 1:

Use the Key Manager module to generate the keys needed for the ADSS SCVP Service to sign the response. At least one SCVP response signing key is required with purpose "SCVP Response Signing".

Step 2:

Register all the root and/or intermediate CAs that will be involved in path building/validation in ADSS Trust Manager module.

Note: Registering the intermediate CAs can shorten the path discovery/validation process overheads and time.

Step 3:

Define an SCVP Validation Policy to how a certificate path can be discovered and/or validated for registered/non-registered CAs. Client applications refer to the SCVP Validation Policy within their request messages sent to the ADSS SCVP Service.

Step 4:

Import the CRLs against the CAs that will be involved in path validation in CRL Monitor module to determine the revocation status if you wish to use the locally held CRLs for revocation checking.

Step 5:

Use the ADSS SCVP Service Manager to start/stop/restart the service. ADSS SCVP Service is required to be restarted when an SCVP Validation Policy is added/updated/deleted.


Following is the detail of the above mentioned steps:



See also

Configuring the SCVP Service

Access Control
Transactions Log Viewer
Logs Archiving
Alerts
Management Reporting
Operating the SCVP Service in FIPS 201 Compliant Mode
SCVP Service Interface URLs