Administration Guide > Pluggable Authentication Modules > Working with TDV and PAM > The Manifest File
 
The Manifest File
The manifest.mf file is a simple text file that contains at least the five entries that TDV requires for PAM deployment and undeployment, and ending with a blank line. The manifest file is required for PAM
The possible name-value pairs are listed in the table.
Name
Req.
Description of Value
Manifest-Version
YES
Always set to 1.0 for TDV.
cisext-name
YES
Unique name of the PAM packaged extension applied when deployed to TDV. By convention, the name equals the primary deployment JAR file name, minus the JAR suffix.
cisext-version
YES
Integer version number of the PAM relative to the custom implementation. Defaults to 1 if missing. The version number is important: it is applied to the deployed PAM, and must be supplied as a parameter during PAM undeployment.
cisext-annotation
YES
Description of the TDV extension package. This annotation is visible in Studio for the deployed PAM. It is useful to include the word “PAM” in the object’s name.
cisext-introspectAll
YES
TDV extension introspection action. Defaults to TRUE.
Must be set to TRUE for the PAM to appear in the TDV Web Manager's Add Module Instance configuration dialog box.
cisext-dependencies
NO
TDV extension dependencies. Multiple dependencies are listed on indented lines, followed by an empty line.
Unversioned dependencies are not accepted. An empty line is required between general properties and file-specific properties.
name
NO
Full path and class file name of the JAAS class that is included in the JAR file for the package that describes the PAM. For example:
test/PamTest1.class
cisext-introspect
NO
For PAM, set the value to TRUE, which indicates that TDV should read any included class files.