Skip to content

Feature/23201/csr extension requests#2091

Merged
jpartlow merged 6 commits intopuppetlabs:masterfrom
jpartlow:feature/23201/csr-extension-requests
Nov 19, 2013
Merged

Feature/23201/csr extension requests#2091
jpartlow merged 6 commits intopuppetlabs:masterfrom
jpartlow:feature/23201/csr-extension-requests

Conversation

@jpartlow
Copy link
Contributor

Provides a mechanism for specifying X509 certificate extension requests to be added to the csr for a host and copied into the hosts certificate by the Puppet certificate authority.

Puppet has never provided a way to add microsoft extension requests to
generated CSRs, so it's not something we would necessarily restore. This
commit removes a comment that indicates that we used to support
msExtReq.
The `Puppet::SSL::CertificateRquest#subject_alt_names` method was trying to
select all of the subjectAltName extensions in the extension requests,
but was accidentally assigning that OID to all extensions instead of
comparing them.

Before 63cecc56 subjectAltName was the only possible extension request so
this was innocuous, but following that commit this error was destructive.
This commit resolves the issue by using the comparison operator instead
of assignment.
@puppetcla
Copy link

CLA signed by all contributors.

Certificates generated by the Puppet CA come with a number of standard
extensions, but users may want to create certs with custom extensions
and then retrieve them later. This commit adds a mechanism for adding
extension requests to the CSR from the csr_attributes file and exposes
custom extensions on the signed certificate.
jpartlow added a commit that referenced this pull request Nov 19, 2013
…quests

Feature/23201/csr extension requests
@jpartlow jpartlow merged commit fbd8a50 into puppetlabs:master Nov 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants