Add support for TLS/FIPS mode

Description

Overview:

Issue during module start-up:

Approach:

Follow the usual approach for adding TLS support to modules, e.g. add fips-specific Dockerfile, incorporate bouncycastle jars, check that HTTP clients are using the TLS properties, update README with any new properties, etc.

Additional Notes:

  • work with FSE to get this deployed to the evrk3 env which is running the latest Q CSP and is setup for FIPS.

Environment

None

CSP Request Details

None

CSP Rejection Details

None

Estimation Notes and Assumptions

None

RCA Group Details

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Craig McNally December 18, 2024 at 6:16 PM
Edited

disregard my comment from moments ago… wrong issue!

Dima Tkachenko December 16, 2024 at 12:04 PM

please use this version to update the env

Maksym Sinichenko November 20, 2024 at 4:24 PM


Retested with latest released version, added env vars according to documentation - env vars present in the logs
Without listed env vars module started successfully

but modules fail during startup

Oleksii Kuzminov November 7, 2024 at 10:38 AM

Blocked by . Should recheck

Done

Details

Assignee

Reporter

Development Team

Eureka

Release

Ramsons (R2 2024) Bug Fix

RCA Group

Related dependency upgrade

Story Points

Sprint

Fix versions

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created October 1, 2024 at 12:20 PM
Updated December 18, 2024 at 6:17 PM
Resolved December 16, 2024 at 12:05 PM
TestRail: Cases
TestRail: Runs