1.4.3(Feb 2022)

Defects

The following defects are resolved in this build.

NXPSR-11238	If the server needs to be accessed via a proxy, the Standalone Client cannot be accessed via a proxy.
NXPSR-11241	Addition of launch check function for Nexaweb Launcher(For security).
NXPSR-11242	Improvement of Japanese message by Launcher

NXPSR-11238 : If the server needs to be accessed via a proxy, the Standalone Client cannot be accessed via a proxy.

Nexaweb Launcher displays a proxy dialog when accessing via Proxy. If the correct information is entered in the Proxy dialog, Launcher can download the file via Proxy.However, if Standalone Client is launched from launcher, the Standalone Client will not be accessible via a proxy. The proxy username/password is not passed along to the Standalone client.

Now you can see proxy credential is transferred to Standalone client. Password is encrypted.

-http.proxyHost
  localhost
  -http.proxyPort
  8888
  -http.proxyUser
  testuser
  -http.proxyPassword
  QTVEMThDMDFFMDBFRjYzQkNFQ0I5QUZBRjhENUYxMzI=

The encrypted password is saved in local file auth.bin. Users don't have to re-enter proxy detail once it is saved.

Note: Requires platform 4.5.70 or higher

NXPSR-11241 : Addition of launch check function for Nexaweb Launcher(For security).

To enhance the security of the application run by Nexaweb Launcher, following security measures have been implemented.
i. Ensure .nexaweb file that is is downloaded from ther server is indeed generated by the server. This is achieved by siginig the .nexaweb file by the nexaweb server usibg RSA signature. For more detail, refer

ii. Provide option to the client to whitelist server from which application can run. For more detail, refer

.Note: Requires platform 4.5.70 or higher