Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refs #11737 - support cnames and add localhost cname to qpid certs #65

Merged
merged 1 commit into from
Oct 20, 2016

Conversation

stbenjam
Copy link
Member

@stbenjam stbenjam commented Sep 8, 2015

This will require the user to do a --certs-update-all for the next upgrade, so qpid gets the new cert with the additional CN.

if resource[:cname].is_a?(String)
args << ['--set-cname', resource[:cname]]
else
resource[:cname].map { |cname| ['--set-cname', cname] }.flatten
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be added to the args array?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would make things actually work, yes :-)

@beav
Copy link
Contributor

beav commented Oct 19, 2016

@stbenjam is there a way to force the --certs-update-all to happen on upgrade, so users don't have to remember to type it?

@stbenjam
Copy link
Member Author

Maybe in the installer pre hook on the 3.2->3.3 upgrade?

https://github.com/Katello/katello-installer/blob/master/hooks/pre/20-certs_update.rb

@ehelms
Copy link
Member

ehelms commented Oct 19, 2016

Will this also require new certs to be generated for each capsule?

@stbenjam
Copy link
Member Author

Yea, unfortunately, everywhere qpid runs

@stbenjam stbenjam merged commit 59857e1 into theforeman:master Oct 20, 2016
@stbenjam stbenjam deleted the alternative-cn branch October 20, 2016 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants