FlexNet Publisher (FNP) has been validated to operate successfully on supported operating systems where FIPS 140‑3 mode is enabled at the OS level. Internal testing confirms that core licensing operations function as expected in FIPS‑enabled environments. This article explains the scope of this validation and clarifies how functional compatibility on FIPS‑enabled systems differs from formal FIPS compliance or certification.

Functional Compatibility on FIPS‑Enabled Systems

Revenera has performed internal validation to confirm that FlexNet Publisher continues to function correctly when FIPS 140‑3 is enabled on supported platforms. Testing verified successful execution of standard licensing workflows, including license server startup and shutdown, license checkout and check‑in, borrow and return operations, lmadmin server functionality, and activation flows. This validation was performed to ensure operational compatibility when FIPS enforcement is enabled by the operating system.

Compliance Scope and Clarification

While FlexNet Publisher has been validated for runtime compatibility in FIPS‑enabled environments, it is not certified or compliant with the FIPS 140‑3 standard, and Revenera does not claim cryptographic module validation under FIPS. The testing described above does not constitute FIPS certification and should not be interpreted as a compliance claim.
As documented in existing Revenera guidance, FlexNet Licensing cryptography is used to protect license rights rather than customer data, and therefore, FIPS certification is not applicable in the same way as for data‑security or encryption products.

Customer Guidance

• Running FlexNet Publisher on FIPS-enabled systems: Supported and validated for core licensing functionality.
• FIPS 140‑3 certification or compliance: Not claimed or provided by FlexNet Publisher.