Deploying the Launcher in IGEL UMS 12

Overview

The Login Enterprise Launcher for IGEL UMS (Universal Management Suite) enables seamless deployment and management of virtual appliances on IGEL devices. This article walks you through setting it up and ensuring that all necessary certificates and packages are correctly installed and configured.

In the following sections, you will learn how to:

• Install and configure the required certificates on both the IGEL UMS and IGEL devices.

• Import the necessary SDK certificates to ensure secure communication.

• Deploy the Login Enterprise Launcher package to the IGEL UMS web interface and the IGEL device.

• Run the Login Enterprise Launcher to manage virtual appliance instances effectively.

By the end of this section, you will have successfully deployed and configured the Login Enterprise Launcher in your IGEL UMS environment, enabling you to manage virtual appliance deployments across your IGEL devices.

Requirements

These steps assume the following has been done already:

1. Login Enterprise is configured. Contact Login VSI Sales if not configured.

2. IGEL UMS 12 Desktop and UMS 12 Web are installed. For details, see Installing / Upgrading to IGEL UMS 12.

   1. The IGEL UMS is licensed. For details, see UMS Licenses.

   2. The IGEL UMS is Registered to IGEL. For details, see Registering the UMS.

   3. The IGEL UMS is configured as an Update proxy instead of the IGEL App Portal. For details, see Configuring Global Settings for the Update of IGEL OS Apps.

      1. This enables the Login Enterprise launcher to be installed without the App Portal.

3. An IGEL 12 OS Device is already set up to be used as a Login Enterprise Launcher. For details, see the Installation Procedure.

   1. The IGEL OS minimum version is 12.6 -- for the IGEL SDK certificates to work; certificates will be set up later in this article.

   2. The IGEL OS is licensed. For details, see Deploying Licenses through the IGEL UMS.

   3. The IGEL OS is registered to UMS. For details, see Registering IGEL OS Devices on the UMS Server.

Getting the Certificate into UMS and onto the Device

1. Download the Login Enterprise CA.crt in a web browser by navigating to https://<FQDN Login Enterprise virtual appliance hostname>/contentDelivery/content/CA.crt

2. Log in to the UMS web console.

3. In the UMS sidebar menu, go to Configuration and click Files.

4. In Files, click Upload File. Navigate to the downloaded CA.crt and upload it.

5. In Classification, select SSL Certificate.

6. Click Finish upload.

7. The CA.crt is now visible in the UMS web console.

8. In the UMS sidebar menu, go to Devices, and select the IGEL device you want to be a Login Enterprise Launcher.

9. In the top bar menu, click Assign Object.

10. In Assign Object to Device > Assignable Objects, click on the CA.crt, then click on the right arrow.

11. Ensure the CA.crt is now in Assignments. Then, click Save and apply on reboot.

12. Click Reboot.

13. Once the device has rebooted, refresh the page to confirm that the license is now applied to the Device.

Confirming the Certificate is Applied to the Device (Optional)

To verify that the license is correctly applied to the device:

1. Console into the device.

2. Access the root shell by running the following command: openssl x509 -in /wfs/ca-certs/CA.crt -text -noout

3. Review the output in the terminal shell. You should see details about your Virtual Appliance certificate, such as the hostname.

For more information, see Terminals in IGEL OS.

Installing SDK Certificates on the IGEL Device

1. Download the following files:
   IGEL_OS_12_SDK-intermediate.crt
   IGEL_OS_12_SDK-leaf.crt

2. Copy or transfer these files to the IGEL device that will act as the Login Enterprise Launcher. You can use one of the following two methods to get the files onto the device:

   1. Drive configuration for the IGEL Device. For details, see Windows Drive Configuration in IGEL OS 12.

   2. Getting files into an IGEL Device through UMS Web. For details, see Upload and Assign Files in the IGEL UMS Web App.

3. Via a terminal in the IGEL Device, create the directories for the certs. Run these commands:
   mkdir /wfs/cmty/im-certs
mkdir /wfs/cmty/certs/

4. Copy the IGEL_OS_12_SDK-intermediate.crt into /wfs/cmty/im-certs/.
   For example, if you have IGEL_OS_12_SDK-intermediate.crt in /tmp/ you would run the following command: cp -r /tmp/IGEL_OS_12_SDK-intermediate.crt /wfs/cmty/im-certs/
   Copy the i into /wfs/cmty/certs/. For example, cp -r /tmp/IGEL_OS_12_SDK-leaf.crt /wfs/cmty/certs/

5. Reboot the IGEL device and log in again once it has fully restarted.

6. Open a terminal again and run the following commands:
   cd /wfs/cmty/im-certs/
dir
   If the IGEL_OS_12_SDK-intermediate.crt file appears in the terminal console output, the IGEL device is successfully trusting the certificate.

7. Run the following commands:
   cd /wfs/cmty/certs/
dir
   If the IGEL_OS_12_SDK-leaf.crt file appears in the terminal console output, the IGEL Device is successfully trusting this certificate.

Now the IGEL Device is ready to have the Login Enterprise Launcher installed on it via the IGEL UMS.

Manually Downloading and Getting the Launcher Package on the IGEL UMS Web

1. Download the Login Enterprise Launcher package
   Login_Enterprise_Launcher-5.14.7+5.14.7.zip

   1. Extract this file to get the .ipkg file inside

2. Open and log in to the IGEL UMS Web console.

3. In the UMS sidebar menu, navigate to Apps and then click Import App.

4. In Import App, click Browse files.

5. Browse and select the Login Enterprise Launcher .ipkg file.

6. The Import App pop-up will show that the file is being uploaded.

7. After uploading, click Confirm.

8. The Login Enterprise Launcher application should now be visible in the IGEL UMS Web interface.

Getting the Launcher onto IGEL Devices

Follow these steps regardless of whether you got the Login Enterprise Launcher into the UMS manually or via the App Portal.

1. In the UMS sidebar menu, go to Devices, and select the IGEL Device you want to be a Login Enterprise Launcher.

2. In the top bar menu, click Assign Object.

3. In Assign Object to Device > Assignable Objects, click on the Login Enterprise Launcher, and then click on the right arrow.

4. Ensure the Login Enterprise Launcher is in Assignments. Then, click Save and apply on reboot.

5. Click Reboot.

6. Confirm the Reboot action.

7. On the IGEL device where the Login Enterprise Launcher is being installed, click OK on the System Reboot pop-up initiated by UMS. This will speed up the installation process.

8. After the IGEL device reboots, a pop-up will appear, indicating that the download is complete. Click Restart Now to speed up the installation process.

9. After the IGEL device reboots, open a terminal and type the following command:
   /services/Login_
   Press the Tab on your keyboard to automatically complete the path.
   If /services/Login_Enterprise_Launcher/ appears in the terminal, the Login Enterprise Launcher has been installed.

10. Download the appsettings.json file.

In a text editor, edit the appsettings.json file

• Find ServerUrl and enter the value for your Login Enterprise appliance’s web URL, such as https://myDomain.myAppliance.com – note without the slash at the end, like how it is here:

• Find the ClientSecret and place it in the Launcher secret value. To copy the ClientSecret, in the Login Enterprise sidebar menu, navigate to Launchers > Downloads.

• Below is how the ClientSecret will appear in the appsettings.json file once you’ve added your actual ClientSecret. The placeholder value is shown here:

11. Save the appsettings.json file

12. In the UMS Web Console, navigate to Configuration, and then click Files.

13. In Files, click Upload file.

14. In the Upload File pop-up, the Name will remain as appsettings.json. Set the Classification to Undefined, the Device File Location to /services/Login_Enterprise_Launcher, and the Owner to User. Ensure to enable all the Access rights via the checkboxes, then click Save.

15. The appsettings.json will be visible now in the UMS Web interface.

16. In the UMS sidebar menu, go to Devices and select the IGEL device.

17. In the top bar menu, click Assign Object.

18. In Assign Object to Device > Assignable Objects, click on appsettings.json, and then click the right arrow.

19. Ensure the appsettings.json is in Assignments.

20. In the UMS sidebar menu, go to Configuration > Profiles.

21. In Profiles, click Create new profile.

22. In Create New Profile, give the new profile the name Login Enterprise Launcher Custom Application, and then click Select Apps.

23. In the App Selector, click on IGEL OS Base System and then Save.

24. In Profiles, click Edit Configuration.

25. In Profile Configurator, click System.

26. Expand System Customization and click on Custom Application

27. In Custom Applications, click Add Item.

28. In Session name, fill in the field with Login Enterprise Launcher.

29. Scroll down to find the Autostart configuration. Enable Autostart to ensure the Login Enterprise Launcher starts automatically when the IGEL device boots. Set the Autostart delay to 10 seconds. This is the recommended configuration.

30. Expand the Login Enterprise Launcher in the left pane and click Settings.

31. Ensure that Icon large and Command are both enabled.

    1. In Icon large, input: /services/Login_Enterprise_Launcher/login-enterprise.svg

    2. In Command, input: xterm -e "/services/Login_Enterprise_Launcher/LoginPI.Launcher.Linux"

32. Click Save and Close.

33. In the UMS Web sidebar menu, navigate to Devices and select the IGEL Device.

34. In the top bar menu, click Assign Object.

35. In Assign Object to Device > Assignable Objects, click Login Enterprise Launcher Custom Application, and then click the right arrow.

36. Ensure the Login Enterprise Launcher Custom Application is in the Assignments. Then, click Save and apply on reboot.

37. Click Reboot.

38. Confirm the reboot, then reboot the IGEL device as before to speed up the process.

After rebooting, the IGEL device may display a secondary reboot confirmation, indicating that the device has changed. If this happens, click Reboot.

Running the Launcher

1. If Autostart was configured in the previous steps, the Virtual Appliance Launcher can be invoked by logging into the IGEL device.

2. When the Login Enterprise Launcher runs and successfully connects to the Virtual Appliance, it will display a message indicating it’s waiting for a Test to run. You will see the status "Reading Configuration" and a log path being displayed.

3. Alternatively, you can start the Virtual Appliance Launcher by clicking the desktop icon or selecting it from the Application Launcher on the IGEL device.

4. To verify that the Login Enterprise Launcher is successfully connected to the Virtual Appliance, in the Login Enterprise sidebar menu, go to the Launchers, and check that the IGEL device's machine name is listed.

The Login Enterprise Launcher is now ready to be used as a Launcher for the Test!

Updating the Launcher

This is necessary when updating the Login Enterprise Virtual Appliance, for example, after updating Login Enterprise 5.14.7 to 6.0.14. If the Login Enterprise Launcher is version 5.14.7 and the Login Enterprise virtual appliance is version 6.0.14, the Login Enterprise Launcher won't launch Test sessions. There must be parity. Below are the steps to update the Login Enterprise Launcher.

1. Open in a text editor the appsettings.json file you set up in step #10 in the Getting the Launcher onto IGEL Devices section.

2. Update the LauncherVersion key to reflect the Login Enterprise version update and save the file. For example:

• Before the update:

• After the update:

3. In the UMS Web interface, navigate to Configuration Objects > Files > Select the existing appsettings.json file, and click Delete.

4. Observe that the appsettings.json file is no longer in the Files pane, then click the Recycle Bin.

5. In the Recycle Bin, click on appsettings.json and then Delete Selected.

6. To upload the appsettings.json file modified with the new Login Enterprise version and add it to the IGEL OS device(s) using the Login Enterprise Launcher, perform the steps starting with step #12 in Getting the Launcher onto IGEL Devices.

7. When the updated appsettings.json file is re-uploaded, ensure in the UMS Web that the appsettings.json Source URL ends with plain appsettings.json, and not appsettings(1).json.

8. Download the Launcher package for IGEL according to your Virtual Appliance version.

9. In UMS Web, navigate to Apps, and then click Import App.

 10. In Import App, click Browse files.

11. Select the newly downloaded package in the file browser.

12. In Import App, observe the package getting uploaded.

15. In the UMS Web interface for the Login Enterprise Launcher App, click Edit Update Settings.

16. In Update Settings, if not already selected, click Update Default Version Manually, then Save.

17. In the UMS Web interface for the Login Enterprise Launcher App, click Set Default Version.

18. In Set Default Version, select the new version of the Login Enterprise Launcher from the drop-down.

19. In Set Default Version, click Save and apply changes on reboot.

20. Initiate a reboot on the affected IGEL device(s) that have the Login Enterprise Launcher installed.

Once the reboot has completed, the Launcher can be used again for Login Enterprise testing.