The following specific libraries are required, but are usually installed by default:
The Solaris 1E Client is provided as an Image Packaging System (IPS) package archive file, with the suffix .p5p. The basic command to install a package archive is:
Unfortunately, IPS does not support pre- and post-install actions of any sort, so after installation separate commands must be run to configure the client, enable it as a service, and start it. So, if the Tachyon Server (assuming that the switch and the background channel are both installed on the Tachyon Server) has the DNS Name FQDN tachyon.acme.local then the 3 commands needed are as follows:
Please refer to 1E Client configuration settings and installer properties for a list of other configuration properties that can be configured in the same way.
Package repository errors
If you get an error telling you that you can't get to the Solaris package repository while installing, e.g. Unable to contact any configured publishers - which you'll probably get if your machine doesn't have internet access - you may need to temporarily disable the Solaris publisher from the package repository, by running the following command:
Then the pkg install should succeed. You should be able to re-enable the Solaris publisher (should you need to) by doing an
--enable instead of
--disable on the command line above.
Another restriction of Solaris IPS is that files and directories cannot be tagged so that they are not deleted on uninstall. If you want the client's persistent storage to survive after uninstall (e.g. because you are likely to install the client again in future), installing the additional 1e.client.persist package will ensure this. This is included in the same package archive file as the client package itself. This command can be run either before or after installation of the client itself:
Warning: extra configuration for Solaris
443(one each for
tcp) to the
/etc/servicesfile if they are not there already. Likewise
80for consistency. The Tachyon background channel does not work without the
httpsentries, and we get "
ERROR - failed to get host IP address for name '<background channel server>' because: service name not available for the specified socket type", and file downloads for example fail.
Certificate Files for the Tachyon Solaris client
The client certificate Tachyon.pfx and a cacert.pem file are required in the hidden directory:/etc/1E/Client/.sslcerts (to create these files see Configuring a non-Windows 1E Client certificate).
If Tachyon.pfx contains the same certificate trust chain as the Tachyon Switch, then cacert.pem is optional. This is because the client will have already cached the public certificates when it parses Tachyon.pfx and cacert.pem will be duplicating the public certificate information. If Tachyon.pfx is using a different certificate trust chain from the Tachyon Switch, then cacert.pem is always required.
Please refer to 1E Client command-line parameters if you would like to see details of other CLI commands.
This method is suitable for reconfiguring all 1E Client settings on non-Windows devices because only Tachyon client features are available and all settings are stored in the 1E Client configuration file.
Each client device requires its own certificate, which must be created as a .pfx file.
Using OpenSSL to create the .pfx file
Each non-Windows devices requires its own certificate. Below is a guide for using a Microsoft CA to issue a certificate (which is the same for Windows computers), then exporting it and using OpenSSL to prepare it before installing it on the non-Windows device.
First, you will need to have created a new Certificate template on your Certificate Authority by making a duplicate of either the Computer or Workstation template and configuring it with at least the following properties:
- General - use a suitable name such as Tachyon Devices and validity period
- Request Handling - Allow private keys to be exported
- Subject Name - Allow information to be supplied in the certificate request, rather than being built from Active Directory information
- Extensions - Application Policies should contain only Client Authentication
- Security - ensure relevant users and computers will be able to request certificates.
Once the new template is created on the CA, issue it.
Using the issued template, request a certificate for a target device, and export it in .pfx form and remember the password.
The target device requires a copy of the basic cacert.pem and the .pfx file with its password removed. You can do this using the following steps. Use the relevant OpenSSL version for the OS. OpenSSL is normally available by default on Linux and Mac devices. If you want to follow these steps on Windows you will need to download the open source version appropriate to your OS.
First, extract the certificate:
Second, the CA key:
Now, the private key:
Remove the passphrase:
Put things together for the new PKCS-File (on Windows, type can be used instead of cat):
And create the new .pfx file, when prompted for a password ensure that you enter an empty password (that is press enter when prompted for the password and confirmation without entering any text):
Now you have a new PKCS12 key file without passphrase on the private key part. This Tachyon.pfx file and the cacert.pem file, must be placed in one of the following locations - depending on the OS. These are hidden folders.
Storing the .pfx on the client
The client certificate file (Tachyon.pfx), and Certificate Authority (CA) certificate(s) for the Switch certificate (cacert.pem file) are stored in the hidden directory: /Library/Application Support/1E/Client/.sslcerts
If the client certificate (Tachyon.pfx) uses the same certificate trust chain as the Tachyon Switch, then cacert.pem is optional. This is because the client will have already cached the public certificates when it parses Tachyon.pfx.
If the client certificate (Tachyon.pfx) uses a different certificate trust chain from the Tachyon Switch, then cacert.pem is always required.
The Solaris IPS packaging system does not support pre- and post-install actions, so the 1E Client must be disabled before uninstallation.
If you protected the 1E Client's persistent storage, as described in Solaris installation, but no longer need it, then you will also need to run this command:
Even if you did not protect the 1E Client's persistent storage, when the 1E Client is uninstalled the IPS system saves the directory at
/var/pkg/lost+found/etc/1E/1e.client/Persist-timestamp , so it can be restored if necessary.