Add http_auth_jwt module to cryptographic boundary definition within 'NGINX Plus FIPS Compliance' document #658
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Problem: The cryptographic boundary definition within the 'NGINX Plus FIPS Compliance' document does not include the http_auth_jwt module. This leads to concern that the operational function of the http_auth_jwt module is not fips compliance.
Solution: Add the http_auth_jwt module to the cryptographic boundary definition within the 'NGINX Plus FIPS compliance' document.
Testing: NA
Closes service console case 00857454 - https://f5.lightning.force.com/lightning/r/Case/500Po00000rGPaRIAW/view