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

pfpki: PKI templates can be modified by a SCEP request #6751

Closed
nqb opened this issue Dec 8, 2021 · 0 comments · Fixed by #6767
Closed

pfpki: PKI templates can be modified by a SCEP request #6751

nqb opened this issue Dec 8, 2021 · 0 comments · Fixed by #6767

Comments

@nqb
Copy link
Contributor

nqb commented Dec 8, 2021

Describe the bug
If you create a PKI template with values for following fields : organisation, organisational_unit, country, state, locality, ocsp_url. Values of these fields (in PKI template) are removed when you request a certificate through SCEP using this PKI template.

User certificates doesn't contain these values too.

Has been noticed on 11.0.0, can be replicate on devel.

To Reproduce
Steps to reproduce the behavior:

  1. Create a CA
  2. Create a PKI template with values for organisation, organisational_unit, country, state, locality, ocsp_url (with SCEP enabled)
  3. Request a certificate through SCEP
  4. Look value of fields for PKI template

=> They have been removed

  1. Look value of fields for user certificate

=> Values are not here

Expected behavior

  • PKI template should not be updated by a SCEP request
  • User certificate should contain values of PKI template

Additional context
There is no specific error in logs.

@nqb nqb added this to the +1 (patch release) milestone Dec 8, 2021
fdurand added a commit that referenced this issue Dec 13, 2021
@fdurand fdurand mentioned this issue Dec 13, 2021
3 tasks
nqb pushed a commit that referenced this issue Dec 30, 2021
@nqb nqb closed this as completed in #6767 Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants