1.4.2(Dec 2021)

Defects

The following defects are resolved in this build.

NXPSR-11215	Regression: Nexaweb launcher 1.3 does not work with Custom JVM
NXPSR-11228	[Compatibility] Nexaweb Launcher log output feature is not effective in 1.4.1
NXPSR-11233	Nexaweb Launcher does not update files from the server
NXPSR-11239	Cannot use openjdk or microsoft jdk for launcher

Feature requests

NXPSR-11226	Support self signed certs
NXPSR-11227	Support persistent cookies in Nexaweb launcher
NXPSR-11230	Provide functionality to delete runNexaweb.nexaweb file downloaded by Nexaweb Launcher
NXPSR-11235	Allow for customization of launcher download timeout

NXPSR-11228 [Compatibility] Nexaweb Launcher log output feature is not effective in 1.4.1

All standard outputs were written to console.log since Nexaweb Launcher 1.1
But it is broken in Nexaweb Launcher 1.4.1.

Please refer to "1. Enable Console for debugging" this document for more detail.

NXPSR-11226 Support self signed certs

To use self-signed certs, copy certs to <installDirectory>/security/cacerts folder and

Add a line jvmarg =-Djavax.net.ssl.trustStore= <path to your cert> to runNexaweb.jsp.

Please refer this document for more details.

NXPSR-11227 Support persistent cookies in Nexaweb launcher

A configuration has been added to nexaweb-client.xml to support persistent cookie.

<!--In this section you can configure how persistent cookies are stored in client's device when running a desktop application.	-->
	<!--You can choose the encryption method and provide encryption key by implementing interface GenerateKey.						-->
	<!--If key is not configured, cookies will be stored as plain text.																--> 
	<cookie-config>
		<!-- Whether persistent cookies should be stored to client's device.														-->
		<persist-cookie>false</persist-cookie>
		<key-configuration>
			<!-- Encryption method. It can be AES or DES.																			-->
			<crypt-mode>AES</crypt-mode> 
			<!--Class to provide encryption key. Replace with your own implementation. By default, cookies are not encrypted.		-->
			<generate-key class="com.nexaweb.util.GenerateKeyImpl"/>
		</key-configuration>
	</cookie-config>

The cookie is stored in <user.home>/.nexaweb/<yourApp>/cookies folder
The cookie name is encoded with base64, the content is encrypted based on your key setting.

Note: Requires platform 4.5.69 or higher

NXPSR-11230 Provide functionality to delete runNexaweb.nexaweb file downloaded by Nexaweb Launcher

Anytime Nexaweb Launcher is used, a runNexaweb.nexaweb file is downloaded from the browser to the download folder.
A configuration has been added to nexaweb-client.xml which allows to delete the runNexaweb.nexaweb file after the application is closed.

<launcher-config>
	<!-- When you run the nexaweb application as laucher mode,*.nexaweb file will be created by the nexaweb server. 	-->
	<!-- you can select to keep or remove this file.																	-->
	<keep-launcher-config-file>false</keep-launcher-config-file>
<launcher-config>

Note: Requires platform 4.5.69 or higher

NXPSR-11235 Allow for customization of launcher download timeout

The getdown set the connection timeout =0 , but read timeout = 30s. If the file read time > 30s, will throw java.net.SocketTimeoutException: Read timed out.
A configuration to customize downoload read time has been added to nexaweb-client.xml.

<launcher-config>
  <!--Specifies the read timeout (in seconds) to use when downloading all files from the server.    -->
        <!--The default is 30 seconds, meaning that if a download stalls for more than 30 seconds, the      -->
        <!--update process wil fail. Setting the timeout to zero (or a negative value) indicates no limit.      -->
      <download-read-timeout>30</download-read-timeout>
 </launcher-config>

Note: Requires platform 4.5.69 or higher