PKCSICSF(1) openCryptoki PKCSICSF(1)NAME
pkcsicsf - configuration utility for the ICSF token
SYNOPSIS
pkcsicsf [-h] [-l|-a token name] [-b BINDDN] [-c client-cert-file] [-C CA-cert-file] [-k privatekey] [-m mechanism] [-u URI]
DESCRIPTION
The pkcsicsf utility lists available ICSF tokens and allows user to add one specific ICSF token to opencryptoki.
The ICSF token must be added first to opencryptoki. This creates an entry in the opencryptoki.conf file for the ICSF token. It also creates
a token_name.conf configuration file in the same directory as the opencryptoki.conf file, containing ICSF specific information. This
information is read by the ICSF token.
The ICSF token must bind and authenticate to an LDAP server. The supported authentication mechanisms are simple and sasl. One of these
mechanisms must be entered when listing the available ICSF tokens or when adding an ICSF token. Opencryptoki currently supports adding only
one ICSF token.
The system admin can either allow the ldap calls to utilize exisiting ldap configs, such as ldap.conf or .ldaprc for bind and authentica-
tion information or set the bind and authentication information within opencryptoki by using this utility and its options. The information
will then be placed in the token_name.conf file to be used in the ldap calls. When using simple authentication, the user will be prompted
for the racf password when listing or adding a token.
OPTIONS -a token name
add the specified ICSF token to opencryptoki.
-b BINDND the distinguish name to bind when using simple authentication
-c client-cert-file
the client certificate file when using SASL authentication
-C CA-cert-file
the CA certificate file when using SASL authentication
-h show usage information
-k privatekey
the client private key file when using SASL authentication
-m mechanism
the authentication mechanism to use when binding to the LDAP server (this should be either simple or sasl)
-l list available ICSF tokens
-h show usage information
FILES
/etc/opencryptoki/opencryptoki.conf
the opencryptoki config file containing token configuration information
/etc/opencryptoki/token_name.conf
contains ICSF configuration information for the ICSF token
SEE ALSO opencryptoki(7),
pkcsslotd(8).
pkcsconf(8).
3.0 April 2013 PKCSICSF(1)
Check Out this Related Man Page
PAM_SM_CHAUTHTOK(3) Linux-PAM Manual PAM_SM_CHAUTHTOK(3)NAME
pam_sm_chauthtok - PAM service function for authentication token management
SYNOPSIS
#define PAM_SM_PASSWORD
#include <security/pam_modules.h>
PAM_EXTERN int pam_sm_chauthtok(pam_handle_t *pamh, int flags, int argc, const char **argv);
DESCRIPTION
The pam_sm_chauthtok function is the service module's implementation of the pam_chauthtok(3) interface.
This function is used to (re-)set the authentication token of the user.
Valid flags, which may be logically OR'd with PAM_SILENT, are:
PAM_SILENT
Do not emit any messages.
PAM_CHANGE_EXPIRED_AUTHTOK
This argument indicates to the module that the users authentication token (password) should only be changed if it has expired. This
flag is optional and must be combined with one of the following two flags. Note, however, the following two options are mutually
exclusive.
PAM_PRELIM_CHECK
This indicates that the modules are being probed as to their ready status for altering the user's authentication token. If the module
requires access to another system over some network it should attempt to verify it can connect to this system on receiving this flag.
If a module cannot establish it is ready to update the user's authentication token it should return PAM_TRY_AGAIN, this information
will be passed back to the application.
If the control value sufficient is used in the password stack, the PAM_PRELIM_CHECK section of the modules following that control value
is not always executed.
PAM_UPDATE_AUTHTOK
This informs the module that this is the call it should change the authorization tokens. If the flag is logically OR'd with
PAM_CHANGE_EXPIRED_AUTHTOK, the token is only changed if it has actually expired.
The PAM library calls this function twice in succession. The first time with PAM_PRELIM_CHECK and then, if the module does not return
PAM_TRY_AGAIN, subsequently with PAM_UPDATE_AUTHTOK. It is only on the second call that the authorization token is (possibly) changed.
RETURN VALUES
PAM_AUTHTOK_ERR
The module was unable to obtain the new authentication token.
PAM_AUTHTOK_RECOVERY_ERR
The module was unable to obtain the old authentication token.
PAM_AUTHTOK_LOCK_BUSY
Cannot change the authentication token since it is currently locked.
PAM_AUTHTOK_DISABLE_AGING
Authentication token aging has been disabled.
PAM_PERM_DENIED
Permission denied.
PAM_TRY_AGAIN
Preliminary check was unsuccessful. Signals an immediate return to the application is desired.
PAM_SUCCESS
The authentication token was successfully updated.
PAM_USER_UNKNOWN
User unknown to password service.
SEE ALSO pam(3), pam_chauthtok(3), pam_sm_chauthtok(3), pam_strerror(3), PAM(8)Linux-PAM Manual 09/19/2013 PAM_SM_CHAUTHTOK(3)