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

[dev.icinga.com #8465] Add the ability to use a CA certificate as a way of verifying hosts for CSR autosigning #2634

Closed
icinga-migration opened this issue Feb 17, 2015 · 5 comments
Labels
area/distributed Distributed monitoring (master, satellites, clients) enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/8465

Created by nick on 2015-02-17 18:38:01 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2015-02-18 07:16:31 +00:00)
Target Version: 2.3.0
Last Update: 2015-02-18 07:19:21 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

The use case for this is using a Puppet agent's cert and key on the Icinga 2 client to make a CSR against an Icinga 2 master. The Icinga 2 master would use the Puppet master's CA certificate to verify the Puppet agent cert used by the Icinga 2 client when the client makes a CSR request.

Changesets

2015-02-18 07:13:44 +00:00 by (unknown) 33e747a

Don't require tickets for clients which already have a trusted certificate

fixes #8465

Relations:

@icinga-migration
Copy link
Author

Updated by gbeutner on 2015-02-18 07:16:27 +00:00

  • Status changed from New to Assigned
  • Assigned to set to gbeutner
  • Target Version set to 2.3.0

@icinga-migration
Copy link
Author

Updated by Anonymous on 2015-02-18 07:16:31 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 33e747a.

@icinga-migration
Copy link
Author

Updated by gbeutner on 2015-02-18 07:19:21 +00:00

Please test this. Here's a short description how this works:

a) Icinga ignores the ticket if - and only if - the client has a certificate that is already signed by at least one of the CA certificates in your certificate chain file (ca.crt), this implies that you need to add the public puppet CA cert in your ca.crt file (in addition to the Icinga CA cert which should already be there).
b) Icinga will only sign requests for the exact same common name which the client already has a certificate for.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-03-09 09:51:43 +00:00

  • Relates set to 8649

@icinga-migration
Copy link
Author

Updated by gbeutner on 2015-03-18 17:42:39 +00:00

  • Relates set to 8801

@icinga-migration icinga-migration added enhancement New feature or request area/distributed Distributed monitoring (master, satellites, clients) labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.3.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/distributed Distributed monitoring (master, satellites, clients) enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant