Release notes
Only use LTS21 releases (3.8.x) in combination with nevisProxy LTS21 (4.x).
If you use nevisProxy from LTS19 (3.x), use nevisAdmin LTS19 (3.7.x) instead.
Do not upgrade nevisAdmin 3 to 3.8.x if you cannot upgrade all nevisProxy instances to at least release 4.0.
Known issues
Since JDK version 1.8.0_322, the Glassfish container of nevisAdmin may stop responding to incoming requests after a few minutes.
The reason for this is an error during the SSL handshake with certain browsers.
If you are facing this issue, you may have to disable an algorithm in the java.security
file of the JDK.
Where this file is located depends on your operating system. Example:
/usr/lib/jvm/jre-1.8.0/lib/security/java.security
.
Search for the configuration of jdk.certpath.disabledAlgorithms
in that file,
and add RSASSA-PSS
to disable the problematic algorithm.
The configuration looks as follows:
jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \
RSA keySize < 1024, DSA keySize < 1024, EC keySize < 224, \
include jdk.disabled.namedCurves, RSASSA-PSS
General upgrade instructions
After installing the nevisAdmin RPM, or upgrading the admin
appliance,
run the following command to ensure that nevisAdmin is redeployed:
nevisadmin redeploy
Release 3.8.5 has fixed a bug where symlinks were missing after upgrading RPMs. However, old versions are still affected.
Proceed as follows if you are upgrading from a version earlier than 3.8.5. The example is for nevisAgent, do the same for nevisAdmin:
## install new version
rpm -i nevisagent-<new_version>-1.noarch.rpm
## check which versions are installed
rpm -qa nevisagent
## remove previous version
rpm -e nevisagent-<old_version>-1.noarch --noscripts
nevisAdmin 3.8.17 LTS 2021 - 27.07.2023
- NEVISADM-4169: We fixed a bug which caused missing log levels in
bc.properties
for nevisProxy.
nevisAdmin 3.8.16 LTS 2021 - 16.06.2023
- NEVISADM-4167: We fixed the
nevisadmin test repository
command. - NEVISADM-4167: We fixed the logging of
nevisadmin
commands to STDOUT.
nevisAdmin 3.8.15 LTS 2021 - 20.04.2023
- NEVISADM-4162: We fixed import of filters with
filter-lib
element. - NEVISADM-4163: We fixed import of filters with missing
filter-lib
element. - NEVISADM-4163: We fixed import of filters which use
Condition
statements in theFilterRules
init-param
. - NEVISADM-4160: We changed SNMP scripts to use
ss
instead ofnetstat
when available. - NEVISPROXY-6365: We added SNMP OID for monitoring nevisProxy dynamic session stores.
nevisAdmin 3.8.14 LTS 2021 - 02.01.2023
- NEVISADM-4158: We upgraded Primefaces to fix a Remote Code Execution vulnerability (CVE-2022-1000486).
nevisAdmin 3.8.13 LTS 2021 - 16.11.2022
- NEVISBASE-5: We changed
nevis-op-idm.sh
to useapplication.log
from nevisIDM instance. - NEVISADM-4153: We fixed a bug with email validation.
nevisAdmin 3.8.12 LTS 2021 - 17.08.2022
- NEVISADM-4148: We fixed a bug which caused an error message “unable to patch logging.yml” during commit.
- NEVISADM-4146: We fixed the path of nevisAdmin log files in logging.yml provided by the instance template.
- NEVISADM-4147: We added missing unit MB to SizeBasedTriggeringPolicy in generated logging.yml files.
- NEVISADM-4150: We upgraded several dependencies.
nevisAdmin 3.8.11 LTS 2021 - 18.05.2022
- NEVISADM-4144: We migrated several Nevis components from Log4J v1 to Log4J v2. For details, see the Release Notes of other components.
- NEVISADM-4140: We fixed file upload on Administration / Software repository screen.
- NEVISBASE-2: We updated nevis-op-proxy.sh to report a session count when dynamic session management is used.
- NEVISBASE-3: We fixed nevis-op-idm.sh calculation of max heap size for nevisIDM instances.
nevisAdmin 3.8.10 LTS 2021 - 16.02.2022
- REMOVED: The supplied log4j version 1.2.17 is patched to remove vulnerable classes org/apache/log4j/net/JMSAppender.class and org/apache/log4j/net/SocketServer.class.
nevisAdmin 3.8.9 LTS 2021 - 17.11.2021
- FIXED: In case of a temporary checkout, the repository at a custom path was not deleted. From now on, we delete such temporary repositories.
- FIXED: From now on, env.conf (standalone) is used instead of vmargs.conf (adnjboss) if both files exist in SNMP scripts.