Certificate Revocation Request Submission Tool

The purpose of the Certificate Revocation Request (CRR) Submission Tool is to facilitate the process of creating a CRR. The tool is designed with the support line in mind, and assumes it is for internal (i.e. within the Identity Manager service managing company) usage.

It retrieves all the necessary data (for the CRR submission) throughout the execution process by asking the user for particular inputs. The expected input from the user is following:

  • Certificate Serial Number (if not known, it can be omitted)
  • Certificate Signing Request Identifier (if not known, it can be omitted)
  • Legal Name (if not known, it can be omitted)
  • Revocation Reason (select one from the displayed list)
  • Reporter (name or identifier of the person issuing the revocation request).

Note: At least one of 1, 2 and 3 has to be provided.

Running Tool

At startup, the Certificate Revocation Request Submission Tool takes only one command line argument: --submission-url, that should be followed by the url to the certificate revocation request submission endpoint.

Example:

java -jar crr-submission-tool-<VERSION>.jar --submission-url http://<<CORDA_DOMAIN>>/certificate-revocation-request

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.