Platform Packages

Target account platforms define the operational and technical settings that determine how the Privileged Access Manager - Self-Hosted solution manages accounts on different platforms and dependencies. All the platforms supported by the system are configured out-of-the-box with default values for most of the settings, and can be used immediately. The technical settings under each platform include settings that determine how the system handles password management operations, transparent connections, PSM connections, and so on.

When a user requires an additional platform, the new platform can be imported into PAM - Self-Hosted conveniently as a platform package. A platform package is a zip archive file that contains the settings and binaries that comprise the platform.

A platform package contains the following files:



CPM Policy file

An INI file that contains the settings that determine how the system will manage associated passwords. This file is mandatory. You can create a new CPM Policy file, or use an existing one.

PVWA Settings file

An XML file that contains the PVWA settings of the platform. This file is mandatory.

CPM Plug-in files

EXE or DLL executable files and other files with policy settings for a specific CPM plugin. These files are optional. For example, a CPM plugin that manages PMTerminal-compatible accounts requires a prompts and process file to be added.

This section describes how to create a platform package and use it to import a new platform into PAM - Self-Hosted.

Create a Platform Package

This section explains how to prepare the contents of a platform package and then create a zip archive file.

Import a Platform Package

This section explains how to import a platform package into PAM - Self-Hosted.

Only zip files can be imported. All files must be contained in the root path; the zip file must not contain any folders.