apache-tomee-fips

Apps

Fips

Stig

Updated yesterday

Apache TomEE-FIPS Overview

Secure your stack with a FIPS-validated, hardened Apache TomEE image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

Apache TomEE gives teams a lightweight option for running enterprise Java applications that need Jakarta EE features — EJB, JMS, CDI, and JPA — without the overhead of a full application server. It builds directly on Apache Tomcat, so teams already deploying WAR files can adopt EJB and CDI incrementally, and can pick from four bundled profiles (Web Profile, JAX-RS, Plus, and Plume) to match how much of the Jakarta EE spec their application actually needs. Use this image when you need to meet the requirements for FIPS-validated cryptographic protection.

FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

For a quick test, print the version information:

docker run --rm \
reg.mini.dev/apache-tomee-fips version.sh

Ready to try out a TomEE webserver?

In the next example, we will start a TomEE container and serve a simple webpage indicating that the server is up.

Create a local webapp directory with a sample index.html:

mkdir -p webapp
echo "<html><body><h1>TomEE is up!</h1></body></html>" > webapp/index.html

Save the following code to a new file compose.yaml in your project directory:

services:
  tomee:
    image: reg.mini.dev/apache-tomee-fips:latest
    container_name: my-tomee
    ports:
      - "8080:8080"
    volumes:
      - ./webapp:/usr/local/tomee/webapps/ROOT
    restart: unless-stopped

Run the TomEE server from your project directory:

docker compose up -d

You should get a response similar to this from the container logs:

...
Starting Servlet Engine: [Apache Tomcat (TomEE)]
...
Server startup in [xxx] milliseconds

Visit http://localhost:8080 to view the landing page.

Clean up

Run the following command to remove the container and its associated volumes:

docker compose down -v

Technical Considerations

The Apache TomEE-FIPS image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image.

Apache TomEE-FIPS built by Minimus:

Runs as root to support required functions in alignment with the public image.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.