Summary
A Local License Server (LLS) set up in HTTPS mode is unable to start when an obfuscated keystore password is used in local-configuration.yaml configuration file.
The issue is being observed in LLS 2024.06 version onwards.
Symptoms
When an LLS is configured to run in HTTPS mode with a certificate , the keystore password needs to be passed on to the local configuration.yaml config file. The keystore password can be obfuscated/hashed using the below
java -jar flexnetls.jar -password <password>
If the obfuscated keystone password is used on the local-configuration.yaml, the LLS is unable to start or install as a service. The issue occurs in both console mode and running as a service.
The following error is thrown by the LLS:
2024-08-06T07:54:55,974Z WARN - Exception encountered during context initialization - cancelling refresh attempt:
org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'undertowServletWebServerFactory' defined in
com.flexnet.glservice.UllsConfiguration: Bean instantiation via factory method failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
Steps to Reproduce
To reproduce this issue, perform the following steps:
- Produce producer
-settings.xmland configurelocal-configuration.yamlto run LLS in HTTPs mode. - Obfuscate the keystore password using
java -jar flexnetls.jar -password <password>. - Use the obfuscated password as the keystore password in the
local-configuration.yamlHTTPS in section. The following is a screenshot of the configuration: - Start LLS in console mode or install it as a service. LLS will throw an error of Unable to start web server.
Workaround
- Currently the workaround for running LLS in HTTPS mode is to use the keystore-password as plaintext and not obfuscated in the local-
configuration.yamlconfig file. For example:keystore-password: keystorepassword - Start the LLS in console mode or installs as a service.
- Otherwise, LLS 2024.05 can be used.
Fix Version and Resolution
The bug is fixed in the 2024.08 release of LLS.
Related Articles
FlexNet Manager for Engineering Applications Reporting Server fails to start due to incorrect keystore or truststore passw… 15Number of Views Reasons for lmgrd Service not Getting Started 25Number of Views Is there a way to recover lost admin password with LLS? 9Number of Views Is There's an API Available to Manage the Reservation List to Add and Return Devices in LLS? 6Number of Views Update Waiting on Status Message in App Portal for Packages Not Getting Updated for Client Machines Reporting to Secondary… 12Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago