You must have unzipped the ssoDiagnosticTools.zip file and set your JAVA_HOME environment variable, as described in Getting Started With the OpenSSO Diagnostic Tool.
Important: The Tamper Detection test expects the checksum files to be in the diagnostic-tool-zip-root/services/tamperdetection/backup directory, where they were generated when you ran the Create Checksum tests. Therefore, make sure that the checksum files are in this same directory before you run the Tamper Detection test.
Log in to the system where OpenSSO Enterprise is deployed and change to the directory where you unzipped the ssoDiagnosticTools.zip file.
Invoke the Diagnostic Tool. For example, in GUI mode on Solaris Systems: ./ssodtool.sh
Under Category, select Tamper-Detection.
In Configuration Directory, specify one of the following paths:
OpenSSO Enterprise server configuration path. For example: /opensso
Web container directory path where the OpenSSO Enterprise server bits are deployed. For example, for Sun Java System Application Server 9.1:
Under Select Test, specify Create Detect Tamper.
Click Run Selected.
The Diagnostic Tool uses the checksum file in the diagnostic-tool-zip-root/services/tamperdetection/backup directory to determine if any files have changed since the checksum file was created. The tool determines if a file:
Existed and was changed
Existed and was deleted.
Did not exist and was added
To save the results as an HTML file, click Save All Results.
The Diagnostic Tool logs all test results in the diagnostic-tool-zip-root/ssodtool.log file. Optionally, as required by your deployment, check and save this log file.
Repeat this procedure to run the test for the other path in Step 4.
Examine the results to determine if your OpenSSO Enterprise deployment has been tampered with since you created the checksum files.