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

New-SelfSignedCertificate into "Trusted Root CAs" #3467

Open
Legends opened this issue May 16, 2023 · 1 comment
Open

New-SelfSignedCertificate into "Trusted Root CAs" #3467

Legends opened this issue May 16, 2023 · 1 comment
Assignees
Labels
area-pki Issues for pki module doc-enhancement Suggested additions/improvements to the article, but there is no evidence the customer was blocked.

Comments

@Legends
Copy link

Legends commented May 16, 2023

I have created CA certificate using New-SelfSignedCertificate and created dev certificate, which is signed by the CA certificate.
The problem is, I am disallowed by the cmdlet to store the CA certificate under "Trusted Root CAs", I have to do it manually.

Without having the CA certificate in the "Trusted Root CAs" there will be no trust.
Why Is this use case not supported?

EDIT:
When creating an unsigned cert with -TestRoot switch, there is again no trust.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@scanum scanum self-assigned this May 18, 2023
@scanum scanum added doc-enhancement Suggested additions/improvements to the article, but there is no evidence the customer was blocked. area-pki Issues for pki module labels May 18, 2023
@officedocspr5
Copy link
Collaborator

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Image showing a dialog asking if the article was helpful with yes and no answers.

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful Article was unhelpful
Image showing a dialog asking how the article was helpful with several options. Image showing a dialog asking how the article wasn't helpful with several options.

Finally, select Submit and you're done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-pki Issues for pki module doc-enhancement Suggested additions/improvements to the article, but there is no evidence the customer was blocked.
Projects
None yet
Development

No branches or pull requests

3 participants