Get certificate extensions/attributes natively through Get-PendingRequest

[mcdonamw]

Submitting an enhancement request to pull attributes and extensions of pending certificate requests in the Get-PendingRequest (and similar cmdlets if they exist).

I found #82 , where someone had a question on the matter, but the workaround seems pretty convoluted. Would be grateful if this could just be built into the cmdlet above.

[Crypt32]

Sorry, there are no current plans to implement this. Provided workaround seems to be sufficient. This is not very critical issue.

[mcdonamw]

With all due respect, that is a terrible point of view and response. I was merely making a feature request/suggestion to make your tool more user friendly to the people you supposedly built them for.

Simply determining my request as not critical and flatly shutting it down is not how I'd suggest doing business with potential customers who are testing your toolsets.

Perhaps this isn't proper area for feature requests? If so apologies.

[Crypt32]

I was merely making a feature request/suggestion to make your tool more user friendly to the people you supposedly built them for.

I appreciate your interest and efforts in this feature request. We are reviewing every feature request and triage them, so they fit the overal concept of the tool and evaluate required efforts to implement them comparing to return benefits. This particular request has lots of unknowns for us, has performance and reliability questions, while we have lots of items with higher priority.

The tool is primarily a framework which includes individual commands to cover most common use cases. We can't provide individual commands to cover every use case and if there is no cmdlet for your task, we suggest to explore alternatives, such using APIs like it was suggested in #82 . Sorry, we can't make happy everyone.

flatly shutting it down

it is not shut down, it is still open. We re-evaluate each open case during each release cycle and if we find that particular issue makes more sense and/or we have an ability to fix this, we put the issue into development. There is a chance that we return to this in future, though, not at this point.

[mcdonamw]

Thanks for the reply. Perhaps this is just a misunderstanding.

I am simply making a suggestion to enhance your tool. I have no expectations that it would ever get done at all, or on a specific timeline if it ever were.

Your response that there are no plans to fix it as the workaround is sufficient, and the issue being labeled "wontfix", suggested to me that this request would never be up for consideration (now or in the future). If that's just a miscommunication or bad wording, great, but I would suggest different wording in the future to help better manage expectations.

Ultimately I searched for your tools to help me manage my CA. Get-PendingRequests seems like a great cmdlet, on the surface, but if it doesn't do what I would consider basic tasks, such as get all the needed properties a CA admin would need from said pending requests, then the cmdlet is pretty light, in its usefulness.

I would equate that to Microsoft providing the Get-Process cmdlet, but requiring users of said cmdlet to perform their own API calls to get information you would expect said cmdlet to pull by default. Perhaps I'm just not a typical CA admin, but what I'm looking for is basic functionality. Most of your cmdlets are far above what I'd even want to do right now, so it just strikes me as odd that something this basic wouldn't already be there.

[Crypt32]

I am simply making a suggestion to enhance your tool.

and we appreciate this!

However, every suggestion goes through triage process. We evaluate many aspects of each suggestion, like our ability to conveniently implement this, estimate efforts, use case and scenario coverage, best practices compliance, performance hit and so on. At this point, your request failed to pass several steps, thus labeled "won't fix". If the item is still open, then it will be put to future consideration. If we decide that it never will be done, it is closed. We received your feedback and will review labeling process to make it more clear.

if it doesn't do what I would consider basic tasks, such as get all the needed properties a CA admin would need from said pending requests, then the cmdlet is pretty light, in its usefulness.

we understand your concern, but we need to consider a lot of hidden obstacles in designing and implementation, including underlying API limitations.