From 5a87879681d28375a55203c4839338b13b668046 Mon Sep 17 00:00:00 2001 From: Pranav Rathi <4427674+pranavrth@users.noreply.github.com> Date: Tue, 30 Jan 2024 14:32:43 +0530 Subject: [PATCH] Updated FIPS docs to reflect schema registry related FIPS compliance information (#1701) --- examples/fips/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/fips/README.md b/examples/fips/README.md index 00e0732c2..74baf7e57 100644 --- a/examples/fips/README.md +++ b/examples/fips/README.md @@ -82,7 +82,7 @@ To make client (consumer, producer or admin client) FIPS compliant, you must ena ## Communication between client and Schema Registry -This part is not tested for FIPS compliance right now. +The communication between client and Schema Registry is also FIPS compliant if the underlying python is using FIPS compliant OpenSSL. This depends on the system level OpenSSL if the python is installed in default way. To know more on how to use FIPS provider with OpenSSL, check [How to use FIPS Module](https://www.openssl.org/docs/man3.0/man7/fips_module.html) and [Generating FIPS module and config file](https://github.com/openssl/openssl/blob/openssl-3.0.8/README-FIPS.md) links. The steps are briefly described above as well. ## References * [Generating FIPS module and config file](https://github.com/openssl/openssl/blob/openssl-3.0.8/README-FIPS.md)