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

Pull the wrong cert during windows provisioning #5861

Closed
lzammit opened this issue Sep 29, 2020 · 2 comments · Fixed by #6768
Closed

Pull the wrong cert during windows provisioning #5861

lzammit opened this issue Sep 29, 2020 · 2 comments · Fixed by #6768

Comments

@lzammit
Copy link
Contributor

lzammit commented Sep 29, 2020

Add a template check when PF pulls the certificate per username because if you have two RootCA it will always download the certificate from the 1st RootCA for that username

Example:

ZamRootCA -> UserZamProfile -> lzammit (cert)

ZamRootCA2 -> UserZamProfile2 -> lzammit (cert)

the provisioning will always push the lzammit cert issued by ZamRootCA even though the Provisioner PKI Provider points at the ZamRootCA2 user profile.

@fdurand
Copy link
Member

fdurand commented Oct 7, 2020

When you pull the certificate it's not complicate to select the correct one since we have the profile id.
But when you will want to revoke it when you unreg the device we don't have the profile_id so we will need to keep track of the profile used to create the certificate.

@lzammit
Copy link
Contributor Author

lzammit commented Oct 8, 2020

It's not me selecting the certificate but the PKI provisioner.

@fdurand fdurand mentioned this issue Oct 8, 2020
3 tasks
fdurand added a commit that referenced this issue Dec 9, 2021
@fdurand fdurand mentioned this issue Dec 13, 2021
3 tasks
fdurand added a commit that referenced this issue Jan 6, 2022
fdurand added a commit that referenced this issue Jan 20, 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.

3 participants