FAQ: Linux 12.5 Client Package Build Workaround

Spirion released the Linux version 12.5 client and sunset the support of RHEL versions 5 and 6 due to RHEL end of life support. During the packaging of the new release the library files for RHEL 5 and RHEL 6 were removed from the build to reduce the size of the package. 

The removal of the RHEL libraries from the package causes a failure when trying to build a package for deployment.

You can build a deployment package by following the steps in the topics below.

Obtain the Files for the Build Package

Obtain the required files to build the package:

1. Download the build script and endpoint application files, SpirionSetup.tgz (legacy versions were IdentityFinderSetup.tgz), from the Customer Portal.
2. Download your license file, identityfinder.lic, from the Customer Portal.
   It is very important that you do not change the name of your license file. Keep it named idenityfinder.lic
3. Open a web browser, navigate to http://consoleserver/Services where consoleserver is the name or IP address of the console and click on the appropriate link for Linux to save the identityfindersettings.xml file to the local client.

Prepare to Build the Package

Before executing the script to build the package, it is necessary to organize the files that will be included in the package. 

Use the following steps to organize the files that will be included in the package:

1. Create a temporary package directory, for example: /tmp/SpirionPackage:
   mkdir /tmp/SpirionPackage
2. Copy the SpirionSetup.tgz bundle from the location it was downloaded to in the section "Obtaining the Installation Files" to the temporary package directory. 
3. 1. For example, if it was downloaded to /home/user/Downloads, this command would copy it to the example temporary folder /tmp/SpirionPackage:
      cp /home/user/Downloads/SpirionSetup.tgz /tmp/SpirionPackage
3. Switch the current working directory to the temporary package directory, for example:
   cd /tmp/SpirionPackage
4. Execute the following command to extract the bundle:
   tar -zxvf SpirionSetup.tgz
5. Copy the identityfindersettings.xml file; downloaded in the section "Obtaining the Installation Files", to the temporary package directory. 
6. 1. For example, if it was downloaded to /home/user/Downloads, this command would copy it to the temporary folder /tmp/SpirionPackage:
      cp /home/user/Downloads/identityfindersettings.xml /tmp/SpirionPackage
6. Copy the identityfinder.lic license file downloaded to in the section "Obtaining the Installation Files" to the temporary package directory into your temporary package directory.  For example, if it was downloaded to /home/userDownloads, this command would copy it to the example temporary folder /tmp/SpirionPackage:
   cp /home/user/Downloads/identityfinder.lic /tmp/SpirionPackage
7. In the SpirionPackage folder create 2 new empty folders one called bin5.tgz and a second called bin6.tgz.
8. 1. These folders are needed to get past the package build process still looking for the old libraries.
   2. You will see the package already has a bin7.tgz folder for support of RHEL 7+.
   3. The issue should be fixed in a future release.
8. When SSL is used for the Services application, the Linux client only requires certificate configuration if the server certificate is self-signed or from a private certification authority.  All certificates from publicly trusted root certificate authorities such as GoDaddy, Verisign, Thawte, etc. are automatically be recognized. 
   
   If a self-signed or private certificate is used on the console server for SSL communications, follow these steps:
9. 1. Obtain the ca.pem file as described in the "Obtaining the server's SSL certificate" section of the following article: Enabling SSL communication between Linux Endpoints and the Console.
   2. Copy the ca.pem file into the temporary package directory (e.g., /tmp/SpirionPackage).
   3. Edit the identityfindersettings.xml file to add the Console\caPath setting as described in the "Configuring the client to use the SSL certificate" section of the article noted above in step 7.1.  The build script will copy the ca.pem to /var/lib/identityfinder, so the value for the Console\caPath setting should be:
      /var/lib/identityfinder/ca.pem
      
      Note: When using SSL you also need to configure the following setting in a System Policy that will be applied to the endpoint.  You can create an installer pkg with the Default Tag feature so the endpoint will automatically be put in a Tag when installed, and that System Policy will be applied to that Default Tag.

Build the Package

Use the following steps to run the script to build the package:

1. Run the following command to build the pkg:
   sudo bash ./install.sh -c
2. If you do not use the -c command line switch then it installs without creating a pkg.
3. Once the package creation script is complete, the following file are created in the script directory, for example /tmp/SpirionPackage:
   SpirionCustom.tgz