#3398: Fix for FIPS enabled in bookshelf using bookshelf s3 url with … #1
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.
…localhost setting in chef-server.rb
Description
Updated oc_erchef.config.erb with s3 url location for FIPS enabled .
<% if node['private_chef']['fips_enabled'] -%>
%% When we're using a fips openssl, we default to using http for bookshelf.
%% The reason for this is because we do not have a TLS implementation for
%% Erlang when we turn on fips.
%%
%% This is the reason that the only supported configuration for the fips
%% package is standalone. We will allow http over localhost so that the
%% chef server can talk to bookshelf. We can give provide bookshelf['url'] = 'http://127.0.0.1:4321' for naking it work for FIPS enabled
%% {s3_url, "http://<%= node['private_chef']['bookshelf']['listen'] %>:<%= node['private_chef']['bookshelf']['port'] %>"},
{s3_url, "<%= @helper.bookshelf_s3_url %>"},
<% else -%>
{s3_url, "<%= @helper.bookshelf_s3_url %>"},
<% end %>
Issues Resolved
chef#3398 issu has been resolved with this fix for FIPS
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]
Check List