PAM360 MSP Edition - Getting Started

ManageEngine PAM360 is also available in MSP edition, which has been specially designed taking into consideration the requirements of the Managed Service Providers. If you are an MSP wishing to manage the administrative passwords of your clients separately from a single management console or offer password management services to them, you can leverage the MSP edition.

Passwords can be securely shared between MSP administrators and their respective customers, making sure that users only get access to the passwords they own or ones that are shared with them. The solution offers the flexibility to entrust the control of the password vault to the MSP administrator, the end user or both, as desired.

The MSP edition also follows the basic password entitlement model of PAM360 which means, at any time, one will be able to view only the passwords that are owned and shared. As MSP admin, while you will be able to view the names of the organizations you manage, you will be able to view the data pertaining to all your customers only if you add their resources or if they share the resources with you. Your customers will be able to view the data belonging to their organization only.

This document walks you through the following topics:

1. Prerequisites
2. Installation Steps
3. Silent Install

   3.1 In Windows
   3.2 In Linux

4. Adding Users
5. Adding Organizations

   5.1 Adding Client Organizations
   5.2 Adding Organizations Manually
   5.3 Importing Organizations from a File
   5.4 Replicating Settings Across Client Orgs

6. Granting Privilege to Manage Organization Access
7. MSPOrg

   7.1 Frequently Asked Questions

1. Prerequisites

1. For testing the MSP edition, you need to deploy a separate machine. If you try to install the MSP edition in the same machine where PAM360 is running, it will uninstall the existing PAM360 instance.
2. Download and install the ManageEngine_PAM360_MSP.exe

2. Installation Steps

Click here for detailed steps.

3. Silent Install

A silent install is used to install an application without the need to interact with the UI. This type of installation is helpful for applications with limited installation steps. Before commencing the silent install, certain parameters such as Name, EmailId, Path, etc., are automatically set or manually entered. Execute the commands as instructed below to install the application automatically.

3.1 Steps to Silent Install PAM360 in Windows Server

3.1.1 Primary Server

1. Download the file ManageEngine_PAM360_MSP_64bit.exe.
2. Download the installation file WindowsPrimaryMSP.iss.
3. Open the WindowsPrimaryMSP.iss file in Notepad and edit Name, MailId, Phone, Company, and Country.
   
4. Update the directory path 'szDir' to the desired path and save the file.
   
5. Now, move the WindowsPrimaryMSP.iss file to the directory as updated above.
   
6. If you opt to create your own .iss file for the installation, execute the command: <.exe file name> -a -r -f1"<iis installation directory path>\WindowsPrimaryMSP.iss" -f2"<iis installation directory path>\WindowsPrimaryMSP.log"
   
7. Open the command prompt as an administrator and navigate to the ManageEngine_PAM360_64.bit.exe file location.
   
8. Execute the command: ManageEngine_PAM360_64bit.exe -a -s -f1"<iis installation directory path>WindowsPrimaryMSP.iss" -f2"<iis installation directory path>\WindowsPrimaryMSP.log"

PAM360 will get installed, and the service will start automatically.

3.1.2 Secondary Server

1. Download the file ManageEngine_PAM360_MSP_64bit.exe.
2. Download the installation file WindowsSecondaryMSP.iss.
3. Open the WindowsSecondaryMSP.iss file in Notepad and edit Name, MailId, Phone, Company, and Country.
   
4. Update the directory path 'szDir' to the desired path and save the file.
   
5. Now, move the WindowsSecondaryMSP.iss file to the directory as updated above.
   
6. If you opt to create your own .iss file for the installation, execute the command: <.exe file name> -a -r -f1"<iis installation directory path>\WindowsSecondaryMSP.iss" -f2"<iis installation directory path>\WindowsSecondaryMSP.log"
   
7. Open the command prompt as administrator and navigate to the ManageEngine_PAM360_64.bit.exe file location.
   
8. Execute the command: ManageEngine_PAM360_64bit.exe -a -s -f1"<iis installation directory path>\WindowsSecondaryMSP.iss" -f2"<iis installation directory path>\WindowsSecondaryMSP.log"

PAM360 will get installed, and the service will start automatically.

3.1.3 Steps to Uninstall PAM360 in Windows Server

1. Download the uninstallation file WindowsUninstallMSP.iss.
2. Move the WindowsUninstallMSP.iss file to a desired directory path.
   
3. If you opt to create your own .iss file, execute the command: <.exe file name> -a -r -f1"<iis installation directory path>\WindowsUninstallMSP.iss" -f2"<iis installation directory path>\WindowsUninstallMSP.log"
   
4. Open the command prompt as administrator and navigate to the ManageEngine_PAM360_64.bit.exe file location.
   
5. Execute the command: ManageEngine_PAM360_64bit.exe -a -s -f1"<iis installation directory path>\WindowsUninstallMSP.iss" -f2"<iis installation directory path>\WindowsUninstallMSP.log"

Upon execution, the PAM360 will  get uninstalled.

3.2 Steps to Silent Install PAM360 in Linux Server

3.2.1 Primary Server

1. Download the file ManageEngine_PAM360_MSP_64bit.bin for Linux.
2. Download the installation file LinuxPrimaryMSP.txt.
3. Open the LinuxPrimaryMSP.txt file in NotePad.
4. Mention the user installation directory's path (USER_INSTALL_DIR) and file overwrite's (-fileOverwrite_) path.
5. Save and move LinuxPrimaryMSP.txt to the directory path mentioned above.
6. If you opt to create your own .txt file for the installation, execute the below commands:
1. chmod a+x ManageEngine_PAM360_64bit.bin
2. ./ManageEngine_PAM360_64bit.bin -r LinuxPrimaryMSP.txt
7. Open the console and navigate to ManageEngine_PAM360_64bit.bin file location.
8. Execute the command: chmod a+x ManageEngine_PAM360_64bit.bin
9. Execute the command: ./ManageEngine_PAM360_64bit.bin -i silent -f /<.txt file installation directory>/LinuxPrimaryMSP.txt

Upon execution, the PAM360 will get installed.

3.2.2 Secondary Server

1. Download the file ManageEngine_PAM360_MSP_64bit.bin for Linux.
2. Download the installation file LinuxSecondaryMSP.txt.
3. Open LinuxSecondaryMSP.txt in Notepad.
   
4. Mention the user installation directory's path (USER_INSTALL_DIR) and file overwrite's (-fileOverwrite_) path.
   
5. Save and move LinuxSecondaryMSP.txt to the directory path mentioned above.
   
6. If you opt to create your own .txts file for the installation, execute the below commands:
   
   1. chmod a+x ManageEngine_PAM360_64bit.bin
   2. ./ManageEngine_PAM360_64bit.bin -r LinuxSecondaryMSP.txt
      
7. Open the console and navigate to ManageEngine_PAM360_64bit.bin file location.
   
8. Execute the command: chmod a+x ManageEngine_PAM360_64bit.bin
9. Execute the command: ./ManageEngine_PAM360_64bit.bin -i silent -f /<.txt file installation directory>/LinuxSecondaryMSP.txt

Upon execution, the PAM360 will get installed.

4. Adding Users (MSP org)

The MSP administration process starts with User Management. The first step is to add users to your MSP organization. You should designate one administrator as Account Manager™ for each of your clients. Proceed with adding users.

5. Adding Organizations

5.1 Adding Client Organizations

After adding users, you need to add your client organizations. Navigate to Admin >> Organizations section and you will find an icon named Organizations. The organizations to be managed by the MSP should be registered with PAM360 here.

You can manually add the client organizations one-by-one or import all the organizations in bulk from a file.

5.2 Adding Organizations Manually

1. Navigate to Admin >> Organizations >> Organizations.
2. Click Add Organization.
   
3. In the pop-up form that opens,
1. Specify a name for the organization being added.
2. Display Name:The name with which you wish to identify the organization being added.
• Only alphanumeric characters without empty spaces are allowed here.
• The name should be a single word.
• The name that you enter here will appear in the dropdown at the top right hand side of PAM360 GU.I
• In addition, the display name will appear in PAM360 login URL.

(For example, if you assign xyz as the display name, the login URL for the organization will be https://:/xyz).

3. Account Manager: You can designate any administrator at your end (MSP) as the Account Manager for the organization being added. As the name indicates, the account manager will be the point of contact for the organization being managed and will have privileges to add and manage resources on behalf of the organization. The Account Manager with the role Admin in PAM360 will be able to manage the users of the organization too. You can designate only one account manager per organization being managed. The same administrator can be made the account manager for multiple client organizations.
4. Fill-in other details like Department, Location etc. as required and click Save.
   

5.3 Importing Organizations from a File

You can import multiple organizations from a file using the import wizard. Click here to view sample files and learn more about file formats supported for importing. Ensure that the entry for each organization is in a new line.

To import organizations,

1. Navigate to Admin >> Organizations >> Organizations >> Import From File.
   
2. In the pop-up form that opens,
1. Choose the file type and file format.
2. Browse and select the file containing the organizations details.
3. Click Next.
   
4. In the pop-up form that opens, check if the fields are auto-filled with respect to the column names in the imported file. You can also map the fields with the corresponding attributes of the client organizations.
   
5. Click Finish.

The result of every line imported will be logged as an audit record.

5.4 Replicating Settings Across Client Orgs

PAM360 allows MSP admins to replicate resource/user group structure and the settings across all managed client organizations.

To set this up, follow the steps:

1. Navigate to Admin >> Organizations >> Organizations >> Replicate Settings Across Client Orgs.
2. Select the required options using the checkboxes.
3. Click Save to save changes.

Listed below are a few replication settings that can be applied to all the client organizations from the MSP organization.

1. Replicate user groups across all client orgs - Replicates the user groups of the MSP organization across all client organizations.
2. Replicate user group settings across all client orgs - Replicates the user group permission and privileges of MSP organization across all client organizations.
3. Replicate resource groups across all client orgs - Replicates the resource groups of the MSP organization across all client organizations.
4. Replicate resource group to user group share settings across all client orgs - Replicates the resource group to user group share configuration of MSP organization across all client organizations.
5. Replicate the resource/account level additional fields across all client orgs - Replicates the MSP organization's resources' and accounts' additional fields across all client organizations.
6. Replicate user roles across all client orgs - Replicates the available user roles of the MSP organization across all client organizations.
7. Replicate resource types across all client orgs - Replicates the resource types of MSP organization across all client organizations with the password reset listeners and database attributes as required.
8. Replicate password policies across all client orgs - Replicates the available password policies of the MSP organization across all client organizations with the default password policy setting as required.
9. Replicate audit operation type settings across all client orgs - Replicates the available operation types of the MSP organization across all client organizations.
10. Replicate audit purge settings across all client orgs - Replicates the configured audit purge settings of the MSP organization across all client organizations.
    

6. Granting Privilege to Manage Organization Access

In addition to designating an administrator as Account Manager, you can grant access privileges to the client organization to any other member of your MSP organization. An administrator with this permission will be granted admin privileges within the client organization. Similarly, if permission is granted to a password administrator or a password user, they will have their respective privileges.

PAM360 requires approval before managing a client organization to ensure greater security. An administrator at the MSP can initiate organization access for a client organization, but they need to be approved by some other administrator at the MSP. It is not possible to approve the request by the one who initiates it or the one for whom it is being initiated. This is to ensure that no administrator can acquire manage permission for themselves or grant that privilege to anyone else without the approval of another administrator. This essentially means that the MSP organization should have a minimum of three administrators to carry out this process.

For example, assume the scenario when Admin A wants to provide access to Admin B for organization ABC. In this case, both Admin A (the proposer) and Admin B (the admin designate) cannot approve the access permission. Another admin, say Admin C, will have to approve the client organization request.

To mange client organizations at user/user group level, do the steps that follow:

1. Log in to your MSP account and navigate to the Users/User Groups tab.
2. Click the User Actions/Actions icon against the desired user and select Manage Organization Access or Manage User Organization Access from the dropdown.
   
3. In the pop-up form that opens, select the required client organizations from the Organization List for which the user/user group to be provided with access and move it right to the Grant Access section.
4. Select the name of the request approver and click Save.
   

The administrator approves the request by navigating to Admin >> Access Review and selecting User Organization Requests or User Group Organization Requests.

• Manage user organization access
• Manage user group organization access
• Grant permission to the user organization access requests
• Grant permission to the user groups organization access requests
  

You can also generate report for a client organization to know more about the users and user groups managed in it. To do this, navigate to Admin >> Organizations >> Organizations and click the report icon beside the desired client organization. In the window that opens, you will get the list of users and user groups managed at different levels.

7. MSPOrg (The default org)

By default, one organization named MSPOrg will be available. This default org is basically your organization (MSP's organization). The passwords that you add here will pertain to your own organization and not that of your clients.

7.1 Frequently Asked Questions

7.1.1 How to Manage Password for Client Organizations?

Once the organization is added, you will see the list of organizations being managed by you (i.e. for which you have access permission or for which you are the account manager) on the top band of the PAM360 GUI.

Select the required organization and proceed with resource addition. You can then share the passwords with your clients. On the other hand, if you are providing Password Management Service, you will ask your client to add passwords themselves.

7.1.2 How to access any specific client org?

You can access your MSP org as usual by accessing the URL https://<PAM360-Host-Name>:8282/. You can select the required client organization from the top band of the PAM360 GUI.

7.1.3 How do your clients access PAM360?

After creating an organization, you clients can connect to their organization and view/manage passwords by typing the URL as explained below:

https://<Host Name:<port>/<Name of the org>

For instance, assume that the name of the organization of your client is abc and PAM360 is running on the host pam360host, then the URL to connect to an organization will be: https://pam360host:8282/abc.

For information on how to perform various password management features, refer to the respective sections of the help documentation.

7.1.4 How to delete a client organization?

You can be eligible to delete a client organization in PAM360 only if you are an MSPOrg administrator. Additionally, you should also have any of the following privileges:

1. Be the Account Manager of the client organization you want to delete.
2. Hold Manage Organization Access permission for the client organization you want to delete.

To delete an organization,

1. Navigate to Admin >> Organizations and locate the client organization that you want to delete.
2. Click on the Actions icon beside the client organization and select Delete Organization from the drop-down list.
   
3. Click OK to confirm deletion. Note that deleting a client organization will also delete all resources and users added under it.