[KEYCLOAK-1] Keycloak - Enable FIPS 140-2 Created: 31/Dec/23  Updated: 12/Jan/24  Resolved: 12/Jan/24

Status: Closed
Project: folio-keycloak
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Craig McNally Assignee: Oleksandr Oliinyk
Resolution: Done Votes: 0
Labels: back-end, epam-eureka, eureka-phase4, need-review, non-testable
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2024-01-12-16-51-26-730.png    
Issue links:
Defines
defines UXPROD-4605 Component Ownership In Progress
Sprint: Eureka Sprint 43
Story Points: 1
Development Team: Eureka

 Description   

For the LoC Eureka env being setup for FedRAMP compliance gap analysis we need to make sure Keycloak is running with FIPS 140-2 enabled.  See https://www.keycloak.org/server/fips#_keycloak_server_in_fips_mode_in_containers.   

Scope:

  • Make the necessary adjustments to https://github.com/folio-org/folio-keycloak 
  • Work with FSE Platform team to get a new image built and pushed to ECR
  • Deployment to a cloud environment will be handled by the FSE Platform team, but Eureka may need to provide some support


 Comments   
Comment by Natalia Zaitseva [ 31/Dec/23 ]

looking at the BouncyCastle stuff a little closer, I think we might be OK - at least for LoC / FedRAMP compliance testing.  It appears that BC uses the MIT license model... Here's a snippet from their website:Please note this should be read in the same way as the MIT license.Please also note this licensing model is made possible through funding from donations and the sale of support contracts.LICENSECopyright (c) 2000 - 2023 The Legion of the Bouncy Castle Inc. (https://www.bouncycastle.org)Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ""Software""), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED ""AS IS"", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Comment by Craig McNally [ 12/Jan/24 ]

Verified on evrk:  

Generated at Thu Feb 08 22:32:24 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.