Show Table of Contents

4.viii. Disabling LDAP Authentication for Token Operations

By default, each user who requests a token operation is authenticated against an LDAP directory. If the user has an entry, then the performance is immune; if the user does not have an entry, then the performance is rejected.

For testing or for sure types of users, and then information technology can be simpler or preferable to disable LDAP authentication. This is not configured in the Enterprise Security Client configuration, only in the Token Processing System configuration, and must exist done by a TPS administrator.

  1. Stop the TPS subsystem. 

    service pki-tps stop

  2. Open up the TPS configuration file. 

    vim /var/lib/pki-tps/conf/CS.cfg

  3. Gear up the hallmark parameters to false. 

    op.operation_type.token_type.loginRequest.enable=faux op.operation_type.token_type.auth.enable=false

    The operation_type is the token operation for which LDAP authentication is being disabled, such every bit enroll, format, or pinreset. Disabling authentication for one operation blazon does not disable it for any other operation types.

    The token_type is the token profile. At that place are default profiles for regular users, security officers, and the users enrolled by security officers. In that location can also be custom token types for other kinds of users or certificates.

    For example: 

    op.                              enroll.userKey.                            loginRequest.enable=false op.                              enroll.userKey                            .pinReset.enable=imitation

  4. Restart the TPS subsystem. 

    service pki-tps start

Editing the TPS configuration is covered in the Certificate System Administrator'south Guide.