microsoft / microsoft/vscode-powerquery-sdk
How do I sign a Power BI .pqx file when .pfx files are now no longer available
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Preflight Checklist
- I have installed the latest version of Power Query SDK.
- I have checked existing resources, including the common issues and the release notes.
- I have searched for similar issues.
Power Query SDK
0.1.5
Regression From
No response
Platform
All
Architecture
i86
OS Version
No response
VSCode version
1.93
PQSdkTool Path
not relevant
Bug Description
The documentation says to use the MakePQX tool to pack the .mez to a .pqx file and then sign with the .pfx file from a code signing certificate.
But now code signing certificates comes on a memory stick and you can no longer extract the .pfx file.
If I can't sign the .pqx my clients will have to reduce the security setting in Power BI to enable the custom connector I've built
Steps to Reproduce
- Download the MakePQX tool. 2 Execute the Pack command. 3. Try to get the .pfx file from the code signing certificate
Actual Experience
The documented way to extract a .pfx file no longer seems to work since code signing certificates changed in May 2023
Expected Experience
I expected a way to extract the .pfx file or a way to sign the .pqx file without the .pfx file
Additional Context
This was originally raised as a support call on Microsoft .com as part of my MAPS support. It was directed to the Power BI break and fix team who could not answer the question and instead gave me this link to raise it as an issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked connector-signing documentation and the Power Query SDK release notes, then inspect the MakePQX Pack command and current signing guidance. Determine whether the documented .pfx workflow is still supported and identify the supported replacement or required documentation update; done means users can follow a verified signing path for .pqx files.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100