FlexNet Connect Knowledge Base

Unable to Save Server-Side Conditions

SummaryDue to an issue with the publisher site, it is not possible to save server side conditions.. This article provides a fix for the issue.SymptomsWhen attempting to configure Server-Side Conditions for an update, the settings are lost upon saving...

CharlesW Level 12 Flexeran Nov 06, 2018

FlexNet Connect 2015 R2 FlexNet Connect 2015 R2 SP1 How To

Control the Size of notification-err.log

SummaryThis article provides the steps necessary to restrict the size of notification-err.log.SynopsisThe log file notification-err.log will track various information about events and exceptions occurring on the notification server. This log can grow...

by acurry Flexera Alumni Jul 14, 2011

FlexNet Connect 2015 R2 How To

Featured Articles

Featured article

Summary: Several vulnerabilities have been reported in the Apache Log4j library. This article discusses the impact of the following vulnerabilities on FlexNet Connect: Log4j 2.x: CVE-2021-45105 CVE-2021-45046 CVE-2021-44228 Log4j 1.x: CVE-2021-4104 CVE-2019-17571 Description: The Log4j 2.x component is not used in FlexNet Connect Client or FlexNet Connect Back-Office 2017 R3, hence there is no impact from CVE-2021-45105, CVE-2021-45046, or CVE-2021-44228. There is no impact from CVE-2021-4104 or CVE-2019-17571 on FlexNet Connect Client or FlexNet Connect Back-Office 2017 R3 since the source code does not use any of the following: SocketAppender SocketServer class SMTPAppender JMSAppender which are the cause of the Log4j 1.x vulnerabilities mentioned above. Resolution: No resolution required. Workaround: No workaround required. Additional Information: Apache Security Site for CVE severity, score, and vector string: https://logging.apache.org/log4j/2.x/security.html

FlexNet Connect Knowledge Base

FlexNet Connect Knowledge Base

Featured Articles

Log4j vulnerability impact on FlexNet Connect