diff options
| author | Endi S. Dewata <edewata@redhat.com> | 2015-06-30 11:33:02 -0400 |
|---|---|---|
| committer | Endi S. Dewata <edewata@redhat.com> | 2015-07-17 22:22:10 -0400 |
| commit | 9d3450e3adb89f764b01a839b5524a2577849496 (patch) | |
| tree | afa3d6c9f3cfbd51fe85f96ef9896260c0f01bda /base/java-tools/man/man1/pki.1 | |
| parent | ed5b182d0d409665fc3cab3cac349f54da623181 (diff) | |
| download | pki-9d3450e3adb89f764b01a839b5524a2577849496.tar.gz pki-9d3450e3adb89f764b01a839b5524a2577849496.tar.xz pki-9d3450e3adb89f764b01a839b5524a2577849496.zip | |
Added pki-audit man page.
A new man page has been added for the pki <subsystem>-audit CLI.
Due to database upgrade issue the command is currently only
available in TPS.
https://fedorahosted.org/pki/ticket/1437
Diffstat (limited to 'base/java-tools/man/man1/pki.1')
| -rw-r--r-- | base/java-tools/man/man1/pki.1 | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/base/java-tools/man/man1/pki.1 b/base/java-tools/man/man1/pki.1 index 41ee3d3da..3de8f6e92 100644 --- a/base/java-tools/man/man1/pki.1 +++ b/base/java-tools/man/man1/pki.1 @@ -102,7 +102,9 @@ Alternatively, the connection parameters can be specified as a URI: where the URI is of the format \fI<protocol>://<hostname>:<port>\fP. .SS Authentication -Some commands require authentication. These are commands that are restricted to particular sets of users (such as agents or admins) or those operations involving certificate profiles that require authentication. +Some commands require authentication. These are commands that are restricted +to particular sets of users (such as agents or admins) or those operations +involving certificate profiles that require authentication. To execute a command without authentication: @@ -133,7 +135,11 @@ To authenticate with a username by interactively prompting for a password: Prompting for a user password is not suitable for automated batch processing. .SS Client Authentication Setup -A client certificate associated with the desired PKI server must be used for client authentication. This can be done by importing the client certificate into an NSS security database and passing the values to the relevant options provided by the \fBpki\fP CLI framework. + +A client certificate associated with the desired PKI server must be used for +client authentication. This can be done by importing the client certificate +into an NSS security database and passing the values to the relevant options +provided by the \fBpki\fP CLI framework. To achieve this, execute the following commands to set up an NSS security database for use by the \fBpki\fP client, import the client certificate into the NSS database, and list information (including the nickname of the client certificate) stored in the NSS database: |