Integrity Verification

To support Integrity Verification, register the following information:
capam32
To support Integrity Verification, register the following information:
  • File name
  • File path
  • Execution path for the client operating system and the integration method (Java, executable, DLL, or shared object)
The following table lists the details for each integration method:
Integration Method
Registered Data
Java (CSPMClient class)
Script name
: The fully qualified name (including the package name) of the Java class that contains the 
CSPMClient
 instantiation and 
getScriptCredentials
 call, without the class extension.
File path:
 The absolute file path to the class file.
Execution path:
 The absolute file path to the class file. UNIX file paths cannot contain symbolic links.
Example:
 
com.cloakware.cspm.client.CSPMClient
 
UNIX executable ( 
cspmclient
, cspmclient64)
Script name:
 The name of the requestor file that contains the Credential Manager executable call.
File path:
 The absolute path to the requestor file.
Execution path:
 The absolute path from which the requestor is launched. UNIX file paths cannot contain symbolic links.
UNIX shared object library
(libcspmclientc.so,
libcspmclientc64.so)
Script name:
 The name of the requestor file that contains the shared object call.
File path:
 The absolute path to the requestor file.
Execution path:
 The absolute path from which the requestor is being launched. UNIX file paths cannot contain symbolic links.
Windows executable (cspmclient.exe, cspmclient64.exe)
Script name:
 The name of the requestor file that contains the executable call, including the file extension.
File path:
 The absolute path to the application file that contains the executable call.
Execution path:
 The absolute path from which the application is launched.
Windows DLL
Script name:
 The name of the requestor file that contains the call togetCredentials,  including the file extension.
File path:
 The absolute path to the requestor file containing the DLL call.
Execution path:
 The absolute path from which the application is launched.
The absolute file path is the complete path without symbolic links. To print the absolute file path in UNIX, use the commandpwd–P.
Refresh A2A Script Hashes
A2A Client script hashes are used during integrity verification of A2A request scripts or applications. If you update or change an A2A request script or application, refresh the script hashes to avoid false integrity violations.
You can refresh the script hash for all the request applications on the specified request server (A2A Client).
Follow these steps using the UI:
 
  1. Select 
    Credentials
    Manage A2A
    Clients
    . The Client List page appears.
  2. Select the server where the A2A client whose logs you want to view is installed and select 
    VIEW
    . The Client Details page appears.
    When the A2A client is not reachable from the site server, you must log into the site where the A2A client is registered.
  3. Select the 
    Get All Script Hash
     button.
For the CLI:
 
Refresh the script hash by running the 
getAllScriptHash
 CLI command. For further details, see .