ManageEngine® PAM360 FAQ

Yes, you can change the default port as explained below:

• Login to PAM360 as an Administrator. Navigate to Admin >> Configuration >> PAM360 Server. 
• Enter the required port beside the Server Port field, and click Save.
• Restart PAM360 for this configuration to take effect.

• Login as an administrator. Navigate to Admin >> Settings and click Mail Server Settings.
• Fill in the required URL in the Access URL field and save the settings.

This will serve as your custom web URL for PAM360 from now on.

PAM360 is an on-premise tool installed in a physical server or virtual machines (VM). You can access PAM360's web interface from any machine on the network connected to the same LAN network using the web browsers.

PAM360 comes bundled with a tailored version of TomCat webserver which allows users to access the webpage and also the JVM which performs the product operations. You can use the below steps to configure the Bind IP address for both these components.

Steps for changing webserver bind IP

1. Stop the PAM360 service.
2. Navigate to <PAM360 installation folder>/conf directory and take a backup of the file named server.xml.
3. Open Wordpad as an administrator and open server.xml under <PAM360 installation folder>/conf directory.
   1. Look for the port="8282" and add the entry address="<IP addresses of the application server>" next to it.
   2. Save the file.
4. Start the PAM360 service. This time the Tomcat webserver will start using the bind IP that you have specified.

Steps for changing JVM bind IP

1. Stop the PAM360 service.
2. Navigate to <PAM360 installation folder>/conf directory and take a backup of the file named wrapper.conf.
3. Open Wordpad as an administrator and open wrapper.conf under <PAM360 installation folder>/conf directory.
   1. Look for the word wrapper.app.parameter.1 and add the following line below wrapper.app.parameter.1.
      
      • wrapper.app.parameter.2=-Dspecific.bind.address=<IP addresses of the application server>
   2. Save the file.
4. Now, rename <PAM360 installation folder>/logs folder to logs_older and start the PAM360 service.
5. Connect to the login page and try using the product features such as Password reset. The source IP for these operations will be the IP Address that you have configured.

In general, users are notified of their PAM360 accounts only through emails. If a user does not get the notification emails, verify:

• if you have configured the mail server settings properly, with the details of the SMTP server in your environment.
• if you have provided valid credentials as a part of mail server settings, as some mail servers require the same for mails to be received.
• if the 'Sender E-Mail ID' is properly configured, as some mail servers reject emails sent without the From address or mails originating from unknown domains.

You can use one of the following three authentication mechanisms out of PAM360:

• Active Directory: When enabled, the authentication request is forwarded to the configured domain controller and based on the result, the user is allowed or denied access into PAM360. The user name, password and the domain are supplied in the PAM360 login screen. This scheme works only for users whose details have been imported previously from AD, and is available only when the PAM360 server is installed on a Windows system.
• LDAP Directory: When enabled, the authentication request is forwarded to the configured LDAP directory server and based on the result, the user is allowed or denied access into PAM360. The username, password and the option to use LDAP authentication are supplied in the PAM360 login screen. This scheme works only for users whose details have been imported previously from the LDAP directory.
• PAM360 Local Authentication: The authentication is done locally by the PAM360 server. Irrespective of AD or LDAP authentication being enabled, this scheme is always available for the users to choose in the login page. This scheme has a separate password for users and the AD or LDAP passwords are never stored in the PAM360 database. However, for security reasons, we recommend that you disable the local authentication for users after enabling AD/LDAP authentication.
• Azure AD: Once you integrate PAM360 with Azure Active Directory (Azure AD) in your environment, you can allow users to use their Azure AD credentials to log in to PAM360 in both Windows and Linux platforms. To use this authentication, PAM360 should first be added as a native client application in your Azure AD portal . 
• Smartcard Authentication: Enabling this feature will mandate users to possess a smartcard, and also know their Personal Identification Number (PIN). Note that smartcard authentication will bypass other first factor authentication methods like AD, LDAP or Local Authentication.
• RADIUS Authentication: You can integrate PAM360 with RADIUS server in your environment and use RADIUS authentication to replace the local authentication provided by PAM360. The users who will be accessing PAM360 using their RADIUS server credentials will have to be added as users in PAM360 first. When you do so, you need to ensure that the "username" in PAM360 is the same as the username used for accessing the RADIUS server. 
• SAML SSO: PAM360 acts as the Service Provider (SP) and it integrates with Identity Providers (IdP) using SAML 2.0. The integration basically involves supplying details about SP to IdP and vice-versa. Once you integrate PAM360 with an IdP, the users have to just login to the IdP and then, they can automatically login to PAM360 from the respective IdP's GUI without having to provide the credentials again. PAM360 supports integration with Okta, AD FS, and Azure AD SSO.

PAM360 comes with five pre-defined roles:

• Privileged Administrator
• Administrators
• Password Administrator
• Password Auditor
• Password User

Apart from these default roles, any administrator can be promoted as a Super Administrator with the privilege to view and manage all the resources. Click here for details on the access levels of the default roles.

If you were already given a valid PAM360 account, you can use the 'Forgot Password?' link available in the login page to reset your password. The username/email ID pair supplied should match the one already configured for the user. The password will be reset for that user and the new password will be sent to the respective email address. However, you wouldn't need this option if AD/LDAP authentication is enabled.

The PAM360 web console always uses the HTTPS protocol to communicate with the PAM360 server. The PAM360 server comes with a default self-signed SSL certificate, which the standard web browsers will not recognize, thereby issuing a warning. You can ignore this warning while you're testing or evaluating the product. However, if you're rolling it out in production, we recommend that you install an SSL certificate bought from an authorized Certificate Authority (CA) that is recognized by all standard web browsers. Know More

Ensuring secure storage of passwords and offering solid defense against intrusion are the top priorities of PAM360. The following measures ensure high level security for your passwords:

• Passwords are encrypted using Advanced Encryption Standard (AES), and stored in the database. AES is currently the strongest encryption algorithm known, and has been adopted as an encryption standard by the U.S. Government.
• The database which stores all the passwords accepts connections only from the host that it is running on, and is not visible externally.
• Role-based, fine-grained user access control mechanism ensures that users can view and access passwords only based on the permissions granted to them.
• All transactions between the PAM360 console and the server take place through HTTPS.
• PAM360's in-built password generator helps you generate strong passwords.

PAM360 offers RESTful APIs and SSH-based CLI APIs that can be used for Application-to-Application/Database password management. The applications connect and interact with PAM360 through HTTPS. An application's identity is verified first by verifying the validity of its SSL certificate, and then by verifying the source IP/hostname in which it resides. Each application/database must be registered as an API User in PAM360. During this  registration, the hostname/IP of the application server has to be supplied and a unique authentication token that uses the REST API will be generated. This token needs to be sent along with the API requests for authentication. In addition to these security checks, each application/database can only access the information that are explicitly delegated to them by an administrative user. Refer to this document to know more about sharing/delegating passwords.

Yes, you can install your own SSL certificates. Follow the steps below:

• Navigate to "Admin >> Configuration >> PAM360 Server".
• Choose the Keystore Type as JKS, PKCS12 or PKCS11 whichever you chose while generating the CSR.
• Browse and upload the Keystore File. 
• Enter the same Keystore Password, you entered while generating the CSR.
• Modify the Server Port, if required.
• Hit Save. Restart the PAM360 service once, for the certificate change to take effect.

PAM360 runs as a HTTPS service. It requires a valid CA-signed SSL certificate with the principal name as the name of the host on which it runs. By default, on first time startup, it creates a self-signed certificate, which will not be trusted by the user browsers. Thus, while connecting to PAM360, you need to manually verify the certificate information and the host name of PAM360 server carefully and should force the browser to accept the certificate.

To make the PAM360 server trusted by web browsers and users:

• Obtain a new signed certificate from a CA for the PAM360 host. [OR]
• Configure an existing certificate obtained from a CA with wild-card principal support for the PAM360 host.

There are different ways to generate the signed SSL certificates:

• By using the "Certificate Management" module of PAM360.
• By using the OpenSSL or Keytool (bundled with Java) to create your certificates, get them signed by a CA and use them with PAM360.
• By installing a wild card certificate.

You can decide the mode of generating the signed SSL certificates based on what your security administrators recommend. The detailed steps for using each of the above methods are provided under the links below.

1. Generating Signed SSL certificates using the Certificate Management module of PAM360
2. Generating Signed SSL certificates using OpenSSL
3. Generating Signed SSL certificates using Keytool
4. Generating Signed SSL certificates by installing a wild card certificate

1. Generating Signed SSL certificates using the Certificate Management module of PAM360

You can generate signed SSL certificates through the Certificate Management module of PAM360 and also apply the certificate changes (Certificate Keystore) directly from the PAM360 console. This involves three processes:

1.1 Generating a Certificate Signing Request (CSR):

To request and acquire certificates from a Local CA through PAM360, you need to first generate a Certificate Signing Request (CSR). Here are the steps for the same:

1. Navigate to the "Certificates >> Create CSR".
2. Click the Create button. The Create CSR page is displayed.
3. Select either of the options Create CSR or Create CSR From KeyStore, based on whether you want to create a new CSR or create a CSR from an already existing private key, respectively.
   1. If you have selected Create CSR, fill in the details, such as Common Name, SAN, Organization Unit, Organization Location, State, Country, Key Algorithm and Key Size. Select the Key Algorithm and Keystore Type. Enter the Validity and Store Password. 

      

   2. If you have selected Create CSR From KeyStore, browse and attach the required private key file along with the Private Key Password.
4. Click the Create button. You will be redirected to a window where the CSR content is displayed. You can copy the CSR content or export it to a mailbox.
   • Email - Select this option to send the certificate file via email to the specified mail id.
   • Export CSR / Private Key - Select this option to export the CSR or the corresponding private key alone based on your requirement.
5. View the saved CSRs under "Certificates >> Create CSR". 

1.2 Signing the Certificate:

PAM360 provides the option to sign and issue certificates to all clients in your network either from your Microsoft Certificate Authority or using a custom root CA certificate that is trusted within your environment.

Follow the below steps to sign the certificate:

• Navigate to "Certificates >> Create CSR". 
• Select the required CSR from the table and click Sign from the top menu. 
• In the pop-up window displayed, provide the name of the server that runs the internal certificate authority, CA Name and choose the certificate template based on your requirement. Click Sign Certificate. The CSR is signed now and the issued certificate can be viewed under "Certificates >> Certificates".

1.3 Applying the Certificate Keystore for PAM360 web server:

To apply the certificate Keystore, first you need to create it.

1. Navigate to "Certificates >> Certificates". Click the signed certificate link under the heading Common Name. In the certificate details page displayed, click the Export icon present at the top right corner of the screen. The certificate file will be downloaded to your local machine.
2. Now, navigate to "Certificates >> Create CSR". 
3. Click the Import Certificate icon corresponding to the CSR of the signed certificate. Browse and choose the certificate file downloaded in your local machine and click Import. Now, the certificate will be bonded with the private key to form a Keystore.
4. Now navigate back to "Certificates >> Certificates" and click the certificate link under the heading Common Name. In the certificate details page displayed, scroll down and click the Export link. This will download the certificate Keystore to your local machine.
5. The final step is to navigate to "Admin >> Configuration >> PAM360 Server" and do the following:
   • Choose the Keystore Type as JKS, PKCS12 or PKCS11, whichever you chose while generating the CSR.  
   • Browse and upload the Keystore File. 
   • Enter the same Keystore Password, you entered while generating the CSR.
   • Modify the Server Port, if required.
   • Hit Save. Restart the PAM360 service once, for the certificate change to take effect.

2. Generating Signed SSL certificates using OpenSSL

OpenSSL mostly comes bundled with the Linux distributions. If you are using the Windows server and do not have OpenSSL installed, download it from http://www.slproweb.com/products/Win32OpenSSL.html. Make sure the 'bin' folder under the OpenSSL installation is included in the 'PATH' environment variable.

2.1 Create the public-private key pair that will be used for the SSL handshake

1. Open the command prompt.
2. Execute 'openssl genrsa -des3 -out <privatekey_filename>.key 1024'

<privatekey_filename> is the filename you specify to store the private key.

3. You will be prompted to enter a pass-phrase for the private key. Enter 'passtrix' or a pass-phrase of your choice. (Though it is not documented, Tomcat has issues with passwords containing special characters, so use a password that has only alpha characters)
4. A file will be created in the name <privatekey_filename>.key in the same folder.

2.2 Create a Certificate Signing Request (CSR) for submission to a certificate authority to create a signed certificate with the public key generated in the previous step

1. Execute 'openssl req -new -key <privatekey_filename>.key -out <certreq_filename>.csr'
   • <privatekey_filename>.key is the one used in the previous step.
   • <certreq_filename>.csr is the filename you specify to carry the certificate creation request to the CA (certificate authority).
2. You will be prompted to enter a series of values that are part of the distinguished name (DN) of the server hosting PAM360.
3. Enter values as required. Importantly, for the 'Common Name' supply the fully qualified name of the server hosting PAM360 (with which it will be accessed through the browsers).
4. A file will be created in the name <certreq_filename>.csr in the same folder.

2.3 Submit the CSR to a Certificate Authority (CA) to obtain a CA signed certificate

Some of the prominent CAs are Verisign, Thawte, RapidSSL. Check their documentation / website for details on submitting CSRs and this will involve a cost to be paid to the CA. This process usually takes a few days time and you will be returned your signed SSL certificate and the CA's root certificate as .cer files. Save them both in the same working folder where files from steps 1 and 2 are stored

2.4 Import the CA-signed certificate to a keystore

1. Open command prompt and navigate to the same working folder.
2. Execute 'openssl pkcs12 -export -in <cert_file>.cer -inkey <privatekey_filename>.key -out <keystore_filename>.p12 -name PAM360 -CAfile <root_cert_file>.cer -caname PAM360 -chain'

   where,

   • cert_file.cer is the signed SSL certificate with the .cer extension.
   • privatekey_filename.key is the private key file with a .key extension.
   • keystore_filename.p12 name is the keystore that will be generated with a .p12 extension.
   • root_cert_file.cer is the CA's root certificate with a .cer extension.
3. When prompted for a password, enter the same password, you used in step 1 for the private key. This requirement is due to an inherent limitation in tomcat, which requires the two passwords to match.
4. Now, a keystore file in the name <keystore_filename>.p12 will be generated in the same folder.

2.5 Configure the PAM360 server to use the keystore with your SSL certificate

This is the final step in generating Signed SSL certificates using OpenSSL.

1. Copy the <keystore_filename>.p12 generated in step 4 to the <PAM360_Install_Folder>\conf folder.
2. Open command prompt and navigate to the <PAM360_Install_Folder>\conf folder.
3. Open the file server.xml and do the following changes:
   • Search for the entry 'keystoreFile', which will have the default value set to 'conf/server.keystore'. Change the value to 'conf/<keystore_filename>.p12'.
   • Starting from version 9700, the keystore password is encrypted and cannot be updated directly in the server.xml file.In order to manuallyupdate the keystore password in the .xml file, disable the encryption first,bychanging the value'keystorePassEncrypted=true'to 'keystorePassEncrypted=false'.
4. Now, set the value of 'keystorePass' to "passtrix" or the password you specified in the previous step while creating the keystore.
5. Add a new entry keystoreType= PKCS12 or PKCS11 next to the keystorePass entry.
6. Save the server.xml file.
7. Restart the PAM360 server and connect through the web browser. If you are able to view the PAM360 login console without any warning from the browser, you have successfully installed your SSL certificate in PAM360.

3. Generating Signed SSL certificates using Keytool

3.1 Create the public-private key pair that will be used for the SSL handshake

1. Go to the <PAM360_Home>/jre/bin folder.
2. Execute the command:
   "./keytool -genkey -alias PAM360 -keyalg RSA -sigalg SHA256withRSA -keypass <privatekey_password> -storepass <keystore_password> -validity <no_of days> -keystore <keystore_filename>

   where,
   <keystore_password> is the password to access the keystore, <privatekey_password> is the password to protect your private key. Note that due to an inherent limitation in tomcat, these two passwords have to be the same. (Though it is not documented, Tomcat has issues with passwords containing special characters, so use a password that has only alpha characters)
   <no_of_days> is the validity of the key pair in number of days, from the day it was created

3. The above command will prompt you to enter details about you and your organization.
   • For the 'first and the last name', enter the FQDN of the server where PAM360 is running.
   • For other fields, enter the relevant details.
4. A keystore file will be created in the name <keystore_filename> in the same folder, with the generated key pair.

3.2 Create a Certificate Signing Request (CSR) for submission to a certificate authority to create a signed certificate with the public key generated in the previous step

1. Go to the <PAM360_Home>/jre/bin folder.
2. Execute the command: "keytool -certreq -keyalg RSA -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -file <csr_filename> -keystore <keystore_filename>".

   Note: The <csr_filename> that you choose should have the .csr extension.

3. A CSR file in the name <csr_filename> will be created in the same folder.

3.3 Submit the CSR to a Certificate Authority (CA) to obtain a signed certificate

Some of the prominent CAs are Verisign, Thawte, RapidSSL. Check their documentation / website for details on submitting the CSRs. Please note that this is a paid service. This process usually takes a few days of time. You will receive your signed SSL certificate and the CA's certificate as .cer files. Save both the files in the <PAM360_Home>/jre/bin folder.

3.4 Import the CA-signed certificate to the PAM360 server

1. Go to the <PAM360_Home>/jre/bin folder using command prompt.
2. If you have a single file as the certificate bundle(p7b), then run the below command:

   "keytool -import -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <your_ssl_bundle.p7b>"

   where,

   • <boundlessness> is the certificate bundle obtained from the CA, a .p7b file saved in the previous step. The <privatekey_password>,<keystore_password> and <keystore_filename> are the ones used in the previous steps.
   • If you have 3 files, the root, the intermediate and the actual certificates in .cer format, then you need to import each one of them using the below commands.
     • "keytool -import -alias root -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <rooter>"
     • "keytool -import -alias inter -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <inter.cer>"
     • "keytool -import -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <your_ssl_cert.cer>"
3. Now, copy the <keystore_filename> to the <PAM360_Home>/conf folder.

3.5 Configure the PAM360 server to use the keystore with your SSL certificate

This is the final step in generating Signed SSL certificates using Keytool.

1. Go tothe <PAM360_Home>/conf folder.
2. Open the fileserver.xml.
3. Search for the entry 'keystoreFile', which will have the default value set to "conf/server.keystore". Change the value to "conf/<keystore_filename>", where <keystore_filename> is the one used in the previous steps.
4. Starting from version 9700, the keystore password is encrypted and cannot be updated directly in the server.xml file.In order to manually update the keystore password in the.xml file, disable the encryption first, bychanging the value 'keystorePassEncrypted=true' to 'keystorePassEncrypted=false.

   Note: This step is applicable only if you're using the version 9700 or above.

5. Set the value of 'keystorePass' to "passtrix" or the password you specified in the previous step while creating the keystore.
6. Restart the PAM360 server and connect through the web browser. If youare able to view the PAM360 login console without any warning from the browser, you have successfully installed your SSL certificate in PAM360.

   Note: Tomcat, by default, accepts only the JKS (Java Key Store) and PKCS #12 format keystores. In case, the keystore is of PKCS #12 format, include the following option in the server.xml file along with the keystore name, keystoreType="PKCS12? This notifies tomcat that the format is PKCS12. Restart the server after this change.

4. Generating Signed SSL certificates by installing an existing wild card supported SSL certificate:

1. Go to the <PAM360_Home>/conf folder.
2. Open the file server.xml.
3. Search for the entry 'keystoreFile', which will have the default value set to "conf/server.keystore". Change the value to "conf/<keystore_filename>" where <keystore_filename> belongs to the existing wild-card certificate.
4. Also search for the entry 'keystorePass' (found next to the keystoreFile), which will have the default value set to "passtrix". Change the value to "<keystore_password>", where <keystore_password> protects the existing wild-card certificate keystore.
5. Restart the PAM360 server and connect through the web browser console. If you are able to view the PAM360 login console without any warning from the browser, you have successfully installed your SSL certificate in PAM360.

   Note: Please refer your CA's documentation for more details and troubleshooting.

PAM360 runs as a HTTPS service. It requires a valid CA-signed SSL certificate with the principal name as the name of the host on which it runs. By default, on first time startup, it creates a self-signed certificate, which will not be trusted by the user browsers. Thus, while connecting to PAM360, you need to manually verify the certificate information and the host name of PAM360 server carefully and should force the browser to accept the certificate.

To make the PAM360 server trusted by web browsers and users:

• Obtain a new signed certificate from a CA for the PAM360 host. [OR]
• Configure an existing certificate obtained from a CA with wild-card principal support for the PAM360 host.

There are different ways to generate the signed SSL certificates:

• By using the "Certificate Management" module of PAM360.
• By using the OpenSSL or Keytool (bundled with Java) to create your certificates, get them signed by a CA and use them with PAM360.
• By installing a wild card certificate.

You can decide the mode of generating the signed SSL certificates based on what your security administrators recommend. The detailed steps for using each of the above methods are provided under the links below.

1. Generating Signed SSL certificates using the Certificate Management module of PAM360
2. Generating Signed SSL certificates using OpenSSL
3. Generating Signed SSL certificates using Keytool
4. Generating Signed SSL certificates by installing a wild card certificate

1. Generating Signed SSL certificates using the Certificate Management module of PAM360

You can generate signed SSL certificates through the Certificate Management module of PAM360 and also apply the certificate changes (Certificate Keystore) directly from the PAM360 console. This involves three processes:

1.1 Generating a Certificate Signing Request (CSR):

To request and acquire certificates from a Local CA through PAM360, you need to first generate a Certificate Signing Request (CSR). Here are the steps for the same:

1. Navigate to the "Certificates >> Create CSR".
2. Click the Create button. The Create CSR page is displayed.
3. Select either of the options Create CSR or Create CSR From KeyStore, based on whether you want to create a new CSR or create a CSR from an already existing private key, respectively.
   1. If you have selected Create CSR, fill in the details, such as Common Name, SAN, Organization Unit, Organization Location, State, Country, Key Algorithm and Key Size. Select the Key Algorithm and Keystore Type. Enter the Validity and Store Password. 

      

   2. If you have selected Create CSR From KeyStore, browse and attach the required private key file along with the Private Key Password.
4. Click the Create button. You will be redirected to a window where the CSR content is displayed. You can copy the CSR content or export it to a mailbox.
   • Email - Select this option to send the certificate file via email to the specified mail id.
   • Export CSR / Private Key - Select this option to export the CSR or the corresponding private key alone based on your requirement.
5. View the saved CSRs under "Certificates >> Create CSR". 

1.2 Signing the Certificate:

PAM360 provides the option to sign and issue certificates to all clients in your network either from your Microsoft Certificate Authority or using a custom root CA certificate that is trusted within your environment.

Follow the below steps to sign the certificate:

• Navigate to "Certificates >> Create CSR". 
• Select the required CSR from the table and click Sign from the top menu. 
• In the pop-up window displayed, provide the name of the server that runs the internal certificate authority, CA Name and choose the certificate template based on your requirement. Click Sign Certificate. The CSR is signed now and the issued certificate can be viewed under "Certificates >> Certificates".

1.3 Applying the Certificate Keystore for PAM360 web server:

To apply the certificate Keystore, first you need to create it.

1. Navigate to "Certificates >> Certificates". Click the signed certificate link under the heading Common Name. In the certificate details page displayed, click the Export icon present at the top right corner of the screen. The certificate file will be downloaded to your local machine.
2. Now, navigate to "Certificates >> Create CSR". 
3. Click the Import Certificate icon corresponding to the CSR of the signed certificate. Browse and choose the certificate file downloaded in your local machine and click Import. Now, the certificate will be bonded with the private key to form a Keystore.
4. Now navigate back to "Certificates >> Certificates" and click the certificate link under the heading Common Name. In the certificate details page displayed, scroll down and click the Export link. This will download the certificate Keystore to your local machine.
5. The final step is to navigate to "Admin >> Configuration >> PAM360 Server" and do the following:
   • Choose the Keystore Type as JKS, PKCS12 or PKCS11, whichever you chose while generating the CSR.  
   • Browse and upload the Keystore File. 
   • Enter the same Keystore Password, you entered while generating the CSR.
   • Modify the Server Port, if required.
   • Hit Save. Restart the PAM360 service once, for the certificate change to take effect.

2. Generating Signed SSL certificates using OpenSSL

OpenSSL mostly comes bundled with the Linux distributions. If you are using the Windows server and do not have OpenSSL installed, download it from http://www.slproweb.com/products/Win32OpenSSL.html. Make sure the 'bin' folder under the OpenSSL installation is included in the 'PATH' environment variable.

2.1 Create the public-private key pair that will be used for the SSL handshake

1. Open the command prompt.
2. Execute 'openssl genrsa -des3 -out <privatekey_filename>.key 1024'

<privatekey_filename> is the filename you specify to store the private key.

3. You will be prompted to enter a pass-phrase for the private key. Enter 'passtrix' or a pass-phrase of your choice. (Though it is not documented, Tomcat has issues with passwords containing special characters, so use a password that has only alpha characters)
4. A file will be created in the name <privatekey_filename>.key in the same folder.

2.2 Create a Certificate Signing Request (CSR) for submission to a certificate authority to create a signed certificate with the public key generated in the previous step

1. Execute 'openssl req -new -key <privatekey_filename>.key -out <certreq_filename>.csr'
   • <privatekey_filename>.key is the one used in the previous step.
   • <certreq_filename>.csr is the filename you specify to carry the certificate creation request to the CA (certificate authority).
2. You will be prompted to enter a series of values that are part of the distinguished name (DN) of the server hosting PAM360.
3. Enter values as required. Importantly, for the 'Common Name' supply the fully qualified name of the server hosting PAM360 (with which it will be accessed through the browsers).
4. A file will be created in the name <certreq_filename>.csr in the same folder.

2.3 Submit the CSR to a Certificate Authority (CA) to obtain a CA signed certificate

Some of the prominent CAs are Verisign, Thawte, RapidSSL. Check their documentation / website for details on submitting CSRs and this will involve a cost to be paid to the CA. This process usually takes a few days time and you will be returned your signed SSL certificate and the CA's root certificate as .cer files. Save them both in the same working folder where files from steps 1 and 2 are stored

2.4 Import the CA-signed certificate to a keystore

1. Open command prompt and navigate to the same working folder.
2. Execute 'openssl pkcs12 -export -in <cert_file>.cer -inkey <privatekey_filename>.key -out <keystore_filename>.p12 -name PAM360 -CAfile <root_cert_file>.cer -caname PAM360 -chain'

   where,

   • cert_file.cer is the signed SSL certificate with the .cer extension.
   • privatekey_filename.key is the private key file with a .key extension.
   • keystore_filename.p12 name is the keystore that will be generated with a .p12 extension.
   • root_cert_file.cer is the CA's root certificate with a .cer extension.
3. When prompted for a password, enter the same password, you used in step 1 for the private key. This requirement is due to an inherent limitation in tomcat, which requires the two passwords to match.
4. Now, a keystore file in the name <keystore_filename>.p12 will be generated in the same folder.

2.5 Configure the PAM360 server to use the keystore with your SSL certificate

This is the final step in generating Signed SSL certificates using OpenSSL.

1. Copy the <keystore_filename>.p12 generated in step 4 to the <PAM360_Install_Folder>\conf folder.
2. Open command prompt and navigate to the <PAM360_Install_Folder>\conf folder.
3. Open the file server.xml and do the following changes:
   • Search for the entry 'keystoreFile', which will have the default value set to 'conf/server.keystore'. Change the value to 'conf/<keystore_filename>.p12'.
   • Starting from version 9700, the keystore password is encrypted and cannot be updated directly in the server.xml file.In order to manuallyupdate the keystore password in the .xml file, disable the encryption first,bychanging the value'keystorePassEncrypted=true'to 'keystorePassEncrypted=false'.
4. Now, set the value of 'keystorePass' to "passtrix" or the password you specified in the previous step while creating the keystore.
5. Add a new entry keystoreType= PKCS12 or PKCS11 next to the keystorePass entry.
6. Save the server.xml file.
7. Restart the PAM360 server and connect through the web browser. If you are able to view the PAM360 login console without any warning from the browser, you have successfully installed your SSL certificate in PAM360.

3. Generating Signed SSL certificates using Keytool

3.1 Create the public-private key pair that will be used for the SSL handshake

1. Go to the <PAM360_Home>/jre/bin folder.
2. Execute the command:
   "./keytool -genkey -alias PAM360 -keyalg RSA -sigalg SHA256withRSA -keypass <privatekey_password> -storepass <keystore_password> -validity <no_of days> -keystore <keystore_filename>

   where,
   <keystore_password> is the password to access the keystore, <privatekey_password> is the password to protect your private key. Note that due to an inherent limitation in tomcat, these two passwords have to be the same. (Though it is not documented, Tomcat has issues with passwords containing special characters, so use a password that has only alpha characters)
   <no_of_days> is the validity of the key pair in number of days, from the day it was created

3. The above command will prompt you to enter details about you and your organization.
   • For the 'first and the last name', enter the FQDN of the server where PAM360 is running.
   • For other fields, enter the relevant details.
4. A keystore file will be created in the name <keystore_filename> in the same folder, with the generated key pair.

3.2 Create a Certificate Signing Request (CSR) for submission to a certificate authority to create a signed certificate with the public key generated in the previous step

1. Go to the <PAM360_Home>/jre/bin folder.
2. Execute the command: "keytool -certreq -keyalg RSA -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -file <csr_filename> -keystore <keystore_filename>".

   Note: The <csr_filename> that you choose should have the .csr extension.

3. A CSR file in the name <csr_filename> will be created in the same folder.

3.3 Submit the CSR to a Certificate Authority (CA) to obtain a signed certificate

Some of the prominent CAs are Verisign, Thawte, RapidSSL. Check their documentation / website for details on submitting the CSRs. Please note that this is a paid service. This process usually takes a few days of time. You will receive your signed SSL certificate and the CA's certificate as .cer files. Save both the files in the <PAM360_Home>/jre/bin folder.

3.4 Import the CA-signed certificate to the PAM360 server

1. Go to the <PAM360_Home>/jre/bin folder using command prompt.
2. If you have a single file as the certificate bundle(p7b), then run the below command:

   "keytool -import -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <your_ssl_bundle.p7b>"

   where,

   • <boundlessness> is the certificate bundle obtained from the CA, a .p7b file saved in the previous step. The <privatekey_password>,<keystore_password> and <keystore_filename> are the ones used in the previous steps.
   • If you have 3 files, the root, the intermediate and the actual certificates in .cer format, then you need to import each one of them using the below commands.
     • "keytool -import -alias root -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <rooter>"
     • "keytool -import -alias inter -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <inter.cer>"
     • "keytool -import -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -keystore <keystore_filename> -trustcacerts -file <your_ssl_cert.cer>"
3. Now, copy the <keystore_filename> to the <PAM360_Home>/conf folder.

3.5 Configure the PAM360 server to use the keystore with your SSL certificate

This is the final step in generating Signed SSL certificates using Keytool.

1. Go tothe <PAM360_Home>/conf folder.
2. Open the fileserver.xml.
3. Search for the entry 'keystoreFile', which will have the default value set to "conf/server.keystore". Change the value to "conf/<keystore_filename>", where <keystore_filename> is the one used in the previous steps.
4. Starting from version 9700, the keystore password is encrypted and cannot be updated directly in the server.xml file.In order to manually update the keystore password in the.xml file, disable the encryption first, bychanging the value 'keystorePassEncrypted=true' to 'keystorePassEncrypted=false.

   Note: This step is applicable only if you're using the version 9700 or above.

5. Set the value of 'keystorePass' to "passtrix" or the password you specified in the previous step while creating the keystore.
6. Restart the PAM360 server and connect through the web browser. If youare able to view the PAM360 login console without any warning from the browser, you have successfully installed your SSL certificate in PAM360.

   Note: Tomcat, by default, accepts only the JKS (Java Key Store) and PKCS #12 format keystores. In case, the keystore is of PKCS #12 format, include the following option in the server.xml file along with the keystore name, keystoreType="PKCS12? This notifies tomcat that the format is PKCS12. Restart the server after this change.

4. Generating Signed SSL certificates by installing an existing wild card supported SSL certificate:

1. Go to the <PAM360_Home>/conf folder.
2. Open the file server.xml.
3. Search for the entry 'keystoreFile', which will have the default value set to "conf/server.keystore". Change the value to "conf/<keystore_filename>" where <keystore_filename> belongs to the existing wild-card certificate.
4. Also search for the entry 'keystorePass' (found next to the keystoreFile), which will have the default value set to "passtrix". Change the value to "<keystore_password>", where <keystore_password> protects the existing wild-card certificate keystore.
5. Restart the PAM360 server and connect through the web browser console. If you are able to view the PAM360 login console without any warning from the browser, you have successfully installed your SSL certificate in PAM360.

   Note: Please refer your CA's documentation for more details and troubleshooting.

Yes, you can create a certificate using SAN with an alias name and apply it in PAM360. Follow the below steps:

1. Creating a CSR using PAM360's SSL certificate management module, and submitting it to any CA for signing

1.1 Create a Certificate Signing Request (CSR)

1. Login to PAM360 as an administrator.
2. Navigate to Certificates >> Create CSR.
3. Click on the 'Create' button.
4. Here, provide a name for your certificate.
5. The Subject Alternative Name (SAN) will be auto-filled when you click on it after providing the common name. You can include additional SANs in the text field.
6. Provide the other details including your organization details, location, validity, and a password.
7. Click on 'Create'.
8. Once done, you will find the option to export the certificate and the private key, or send the CSR to an email address that you specify.

1.2 Submit the CSR to a Certificate Authority (CA) to obtain a CA signed certificate

After creating the CSR, the next step is get the CSR verified and signed by a CA. There are two options to do this:

1. You can export the CSR file and manually send it to a third party CA to get it signed.
2. You sign and issue certificates to all clients in your network either from your Microsoft Certificate Authority or using a custom root CA certificate that is trusted within your environment. To do this, navigate to Certificates >> Create CSR, select a certificate, and click on 'Sign'.  Refer to this document for more details on certificate signing.

Once signed, you can view the certificate under 'Certificates'.

1.3 Import the CA-signed certificate to the PAM360 server

To import the certificates in your network:

1. Navigate to the Certificates.
2. Click on 'Add'.
3. Choose the required option:
   • File Based Certificate“ Browse and import the required certificate file directly from your system.
   • Content Based Certificate “ Copy the content of the required certificate file and paste it in the text box.
   • Keystore Based “ Import all individual certificates available in keystore simultaneously. Upload the required keystore file and enter its corresponding password (if any).
4. Click on the 'Add' button.

2. Creating a certificate with SAN using Microsoft internal CA

Make sure you follow the below mentioned steps to create server certificate with SubjectAlternativeName using Microsoft Internal CA. Also, in Additional Attributes, specify the 'san:dns=<The URL which you use to access PAM360>', and then try creating the certificate.

1. Connect to the server where Microsoft Certificate Service is running.
2. Open a command prompt and execute certutil -setreg policy\EditFlags +EDITF_ATTRIBUTESUBJECTALTNAME2
3. Then, restart Microsoft Certificate Service(certsvc).
   Create the private key using the below command,"./keytool -genkey -alias PAM360 -keyalg RSA -keypass <privatekey_password> -storepass <keystore_password> -validity <no_of days> -sigalg SHA256withRSA -keysize 2048 -keystore <keystore_filename>"
4. Here, when it prompts for first and last name, specify the name which you use to access PAM360.
5. Create the Certificate Signing Request(CSR) using the below command: 'keytool -certreq -keyalg RSA -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -file <csr_filename> -keystore PAM360.keystore'
   • Submit CSR request to Microsoft Internal CA:
   • Open IE and go to your CA's certificate request page.
   • Request advanced certificate.
   • Submit a certificate request.
   • Copy and paste content of <csr_filename>.cer file.
   • Certificate template should be Web Server.
   • In "Additional Attributes", enter 'san:dns=passwordmanager&dns=passwordmanager.tcu.ad.local' and click on 'Submit'.
   • Download the certificate chain in base64 format as PAM360cert.p7b.
6. Import the downloaded 'PAM360cert.p7b' file into the PAM360.keystore "keytool -import -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -keystore PAM360.keystore -trustcacerts -file PAM360cert.p7b"

   Notes: 

   1. If you receive the error message "Failed to establish chain from reply" with the above command, it means the root and intermediate certs of your CA are not available in the trusted store of the PAM360. So, before importing the actual certificate, you have to import the root certificate with a different alias and then import the actual certificate. Also, if you have multiple root certificates, then you have to import them one by one with the different alias names.

      For example,

      ./keytool -import -alias root1 -keypass Password123 -storepass Password123 -keystore PAM360.keystore -trustcacerts -file root1.cer
      ./keytool -import -alias root2 -keypass Password123 -storepass Password123 -keystore PAM360.keystore -trustcacerts -file root2.cer

      Based on the number of root or intermediate root certificates, you have to execute the above command with different alias names and then continue with the actual certificate.

   2.  The actual certificate should be in .cer or .crt format.
7. Applying the certificate keystore in PAM360.
   • Login to PAM360 as an administrator.
   • Navigate to Admin >> Configuration >> PAM360 Server.
   • Choose PKCS12 or PKCS11 as the Keystore Type.
   • Click on 'Browse' and select your PFX/P12 file.
   • Provide the correct keystore password and save the configuration.
   • Restart PAM360 service to bring the certificate change into effect. 

3. Creating certificate with SAN signed by third party vendor like GoDaddy, Verisign, Commodo, etc.

Make sure you follow the below mentioned steps to get SAN certificate signed from the third party vendors.

1. Create the private key using the below command,

    './keytool -genkey -alias PAM360 -keyalg RSA -keypass <privatekey_password> -storepass <keystore_password> -validity <no_of days> -sigalg SHA256withRSA -keysize 2048 -keystore <keystore_filename>"'

   Here, when it prompts for first and last name, specify the name which you use to access PAM360.

2. Create the Certificate Signing Request(CSR) using the below command:

    'keytool -certreq -keyalg RSA -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -file <csr_filename> -keystore PAM360.keystore'

3. Submit CSR request to third party signing tool and ensure to get the certificate signed using SAN name. Download the certificate chain in base64 format as PAM360cert.p7b
4. Import the downloaded 'PAM360cert.p7b' file into the PAM360.keystore keytool -import -alias PAM360 -keypass <privatekey_password> -storepass <keystore_password> -keystore PAM360.keystore -trustcacerts -file PAM360cert.p7b

   Note: If you receive the error message "Failed to establish chain from reply" with the above command. Then, the root and intermediate certs of your CA are not available in the trusted store of the PAM360. So, before importing the actual certificate, you have to import the root certificate with a different alias and then the actual certificate. Also, if you have multiple root certificates, then you have to import them one by one with different alias names. For example,

   ./keytool -import -alias root1 -keypass Password123 -storepass Password123 -keystore PAM360.keystore -trustcacerts -file root1.cer
   ./keytool -import -alias root2 -keypass Password123 -storepass Password123 -keystore PAM360.keystore -trustcacerts -file root2.cer

   Based on the number of root or intermediate root certificates, you have to execute the above command with different alias names and then continue with the actual certificate.

5. Applying the certificate keystore in PAM360.
   • Login to PAM360 as an administrator.
   • Navigate to Admin >> Configuration >> PAM360 Server.
   • Choose PKCS12 or PKCS11 as the Keystore Type.
   • Click on Browse and select your PFX/P12 file.
   • Provide the correct keystore password and save the configuration.
   • Restart PAM360 service to bring the certificate change into effect. 

Yes. PAM360 can remotely reset the passwords of various end points. PAM360 supports both agent-based and agent-less modes of changing passwords. Refer this document for more information.

Let us first look at the requisites for both the modes:

The agent mode requires the agent to be installed as a service in each end point and run with administrative privileges to perform password reset operations. The agent uses one-way communication using outbound traffic to reach the PAM360 server.

For the agent less mode, you must supply administrative credentials to perform the password changes. For Linux, you must specify two accounts- one with root privileges and the other with normal user privileges that can be used to login remotely. Telnet or SSH service must be running on the resources. For Windows domain, you must supply the domain administrator's credentials. For Windows and Windows Domain, PAM360 uses remote calls, so relevant ports must be open on the resource.

Based on this, you can choose which mode you want for your environment, indicated by the following tips:

Choose the agent mode when:

• You do not have administrative credentials stored for a particular resource in PAM360,
• You do not have the required services running on the resource (Telnet / SSH for Linux, RPC for Windows),
• You run PAM360 in Linux and want to make password changes to a Windows resource.

Choose agent less mode in all other cases as it is a more convenient and reliable way of doing password changes.

Yes, you can. As long as your resource type label contains the string 'Linux' or 'Windows', you can still configure agent less password reset for those resources.

Example of valid resource type labels to enable password reset:

Debian Linux, Linux - Cent OS, SuSE Linux, Windows XP Workstation, Windows 2003 Server

PAM360 supports remote password reset for custom resource types through SSH command sets, password reset plugins, and password reset listeners.

• SSH Command Sets: For SSH-based devices, you can build command-based executables directly from PAM360 using a set of default or customized SSH commands. These command sets can then be associated with the respective SSH device accounts that do not come out of the box with PAM360 to perform their password resets without the need for a CLI. 
• Password Reset Plugin: You can build your own implementation class and run it via PAM360 to enforce automatic password resets of custom resource types. With the plugin, you can also leverage access control for legacy accounts and automatically reset passwords instantly upon usage. This way, the passwords of these accounts will serve as one-time passwords that are reset after every use via the associated plugin.
• Password Reset Listeners: Listeners are custom scripts or executables that can be invoked for local password changes, as well as to reset the passwords of custom resource types for which remote password reset is not supported out-of-the-box by PAM360. You can configure listener scripts individually for each resource type including the custom ones.

In the agent mode:

• Check if the agent is running by looking at the Windows active process list for the entry 'PAM360Agent.exe' or the presence of a process named 'PAM360Agent' in Linux.
• Check if the account in which the agent is installed has sufficient privileges to make password changes.

In the agent less mode:

• Check if the right set of administrative credentials have been provided and the remote synchronization option is enabled.
• Check if the necessary services are running on the resource (Telnet / SSH for Linux, RPC for Windows).
• Check if the resource is reachable from the PAM360 server using the DNS name provided.

This happens when PAM360 is run as a Windows service and the 'Log on as" property of the service is set to the local system account. Change it to any domain user account to be able to reset domain passwords. Follow the instructions below to effect that setting:

1. Go to the Windows Services Applet (from Control Panel --> Administrative Tools --> Services).
2. Select the 'ManageEngine PAM360' service, right-click --> choose 'Properties'.
3. Click the 'Log On' tab and choose 'This Account' radio button and provide the username and password of any domain user - in the format <domainname>\<username>.
4. Save the configuration and restart the server.

Before enabling windows service account reset, ensure if the following services are enabled in the servers where the dependent services are running:

• Windows RPC service should have been enabled.
• Windows Management Instrumentation (WMI) service should have been enabled.

The domain Single Sign On (windows integrated authentication) is achieved in the Windows environment by setting non-standard parameters in the HTTP header, which are usually stripped off by devices like firewalls / VPNs. PAM360 is designed for use within the network. So, if you have users connecting from outside the network, you cannot have SSO this enabled.

Yes. you can migrate PAM360 to another server by following the below steps:

1. Stop PAM360 service, exit tray icon.
2. Make sure that the Postgres process is not running in Task Manager.
3. Copy and move entire PAM360 directory to the new server.
4. Open command prompt with admin rights and navigate to <PAM360 HOME>\bin directory. Execute the command PAM360.bat install. (This will install PAM360 service.) 
5. Move the encryption key(PAM360_key.key) to the new server and specify the correct location of it in PAM360/conf/manage_key.conf file. Click here for more information about the encryption key.
6. Go to services console, provide a service account and start PAM360 service. 
7. If you want the tray icon, Go to the <PAM360 HOME>, right click on PAM360.exe and select "Run as Administrator". 
   Now you should be able to access the PAM360 web page using the new server name in the URL.

Yes, you can. PAM360 can periodically backup the entire contents of the database, which can be configured through the PAM360 console. Refer this document for more details.

All sensitive data in the backup file are encrypted using the 7-Zip utility, which has options to encrypt and compress data by the AES256 algorithm. The encrypted data is stored under the '<PAM360_Install_Directory/backUp>' directory as a .zip file. We recommended you to store the backup in secure, secondary storage for disaster recovery.

There are three license types:

1. Evaluation download / Trial Version - You can straightaway download and install this trial version. It is fully functional, capable of supporting a maximum of 5 administrators and you can evaluate all the features for 30 days.
2. Free Edition - Licensed software that allows you to have 1 administrator and manage up to 10 resources. Valid forever.
3. Registered Version - You get the Enterprise edition, and Licensing is based on the Number of Administrators. This is useful if you require more enterprise-class features such as auto discovery of privileged accounts, integration with ticketing systems and SIEM solutions, jump server configuration, application-to-application password management, out-of-the-box compliance reports, SQL server / cluster as backend database, etc.

   Note: PAM360 comes with five user roles - Administrator, Password Administrator, Privileged Administrator, Password Auditor and Password User. The term 'administrator' denotes Administrators, Password Administrators and Privileged Administrators. So, licensing restricts the number of administrators as a whole, which includes Administrators, Password Administrators and Privileged Administrators. There is no restriction on the number of Password Users and Password Auditors. To get more details on the five user roles, refer this section of our help documentation.

Though PAM360 follows an annual subscription model for pricing, we also provide perpetual licensing option. The perpetual license will cost three times the annual subscription price, with 20% AMS from the second year. Contact sales@manageengine.com for more details.

• Login as an administrator in the PAM360 web interface. Click the 'My Account' icon at the top right corner and select License from the drop down.
• Browse to add the license file and click on Upgrade. Your new license file is added.
• Now, restart the PAM360 service for the license to take effect. You can check to see if the license is applied and other details under the same section.

Yes, if you buy a single license, you are entitled to have the High Availability setup. You can apply the same license on the Primary as well as the Secondary servers. Follow the below steps:

1. Stop the PAM360 service in the Primary server.
2. Login PAM360 using the Secondary server URL as an Administrator.
3. Tap License under the User menu, at the top right corner of the console.
4. Update the same license file which you applied for the Primary server.

Yes, very much. If you want a license with more than 1000 administrator users, please contact sales@manageengine.com for more details.

Yes. Fill in the required details in the website and we will send you the license keys.

No. PAM360 adopts the same approach for managing SSH user accounts and SSH service accounts. The only difference is that during resource discovery, if service / root account credentials are provided to establish connection with the resource, you acquire extended privileges to import and manage keys from all user accounts in the resource.

Whereas, when connection to the resource is established using user account credentials, you get key management privileges only for SSH keys present in that particular account.

Yes. We have a dashboard that displays the number of keys that were not rotated for the predefined time period as specified in the notification policy.

PAM360 houses a key vault called "Key Store" which facilitates the storage and management of any type of digital key. However, the option to discover and import is limited to SSH keys and SSL certificates only, and isn't available for other types of digital keys.

No. PAM360 supports all X.509 certificate types.

Yes. You can create scheduled tasks to perform automatic certificate discovery through which you can import and replace old certificates from target systems with their updated versions in PAM360' certificate repository. Click here for a detailed explanation on creating schedules.

No, it doesn't. The AD User Certificate and MS Certificate Store tabs appear only in the Windows version of PAM360.

PAM360 differentiates certificates by their common names and records certificates with same common names as a single entry in its certificate repository. We've designed it this way because PAM360 licensing is based on the number of certificates and we don't want customers to spend many license keys for the same certificate. 

However, if there's a need to manage both the certificates separately, you can do so by listing them as separate entries in PAM360' certificate repository. Once listed, the newly added certificate will be counted for licensing.

To add a certificate with the same common name as a separate entry in certificate repository,

1. Navigate to the Certificates tab and click Certificates, and click the Certificate History icon beside the certificate.
2. Click the 'Certificate Settings' icon beside the required version of the certificate and click on 'Manage Certificate'.
3. The selected version is listed as a separate certificate in the certificate repository.
4. In case you want to manage only one version of the certificate, click 'Certificate Settings' icon beside the required version and choose 'Set as current certificate' option. 

Follow the steps below to import a certificate's private key into PAM360.

1. Navigate to the Certificates tab and click Certificates.
2. Select the certificate for which you need to import the private key.
3. Click the Import Keys option from the More drop down menu at the top.

Browse for the file that contains the private key, enter the keystore password, and click on 'Import'. The private key will be imported and attached to the selected certificate.

PAM360 facilitates certificate deployment through which you can deploy certificates from its repository to target server's Microsoft Certificate Store.  

Click here for step-by-step explanation on certificate deployment. 

To map the certificate to its corresponding application, you've to manually restart the server on which the application is running for the change to take effect.

No. PAM360 currently doesn't support subnet based SSL certificate discovery.

No. Currently, PAM360 doesn't support automatic scheduling for certificate discovery from MS Certificate Store.

Email notifications are generated ONLY for certificates listed in PAM360's certificate repository and NOT for different versions of a certificate displayed in "Certificate History" section.

Yes. All types of SSL certificates, SSH keys and any other digital key being managed using PAM360 are taken into account for licensing. There's a dashboard widget "License Details" that provides insights on the type and number of digital identities being managed using PAM360 that will be taken into account for licensing.

To import a root certificate, open the Command Prompt and navigate to the <pam360_server_home>\bin directory and execute the following command: