We are running into an issue where some Apps won't install using UAM because running scripts is disabled by default in Windows. While I could just allow any old script, that's not a good practice. So that leaves creating a self-signed or using a public certificate. Well we have a public certificate requited for ScreenConnect now. And it's stored in an Azure Key vault and because it is backed by an HSM you cannot just export the private key. It we have to use it directly from the vault to sign code.
Allow Code Signing Certificates from an Azure Key Vault Backed by HSM
0
We appreciate your feature request—community input is essential to our ongoing development.
Next steps:
• We will review your suggestion and update its status during the evaluation process.
• If further clarification is needed, we'll contact you via comments.
We also encourage others to contribute through feedback and voting.
Next steps:
• We will review your suggestion and update its status during the evaluation process.
• If further clarification is needed, we'll contact you via comments.
We also encourage others to contribute through feedback and voting.
Hey Matthew,
Thanks for the request! This is an interesting one - When we implemented the code signing functionality, we assumed most MSPs wouldn't want to go through the process of managing the Code Signing cert and went the self-signed route instead. I'll review with my team and see if your use case would work with our app deployment model and multi-tenancy.
Thanks
Andy Weidner
We were forced to go this route by ConnectWise ScreenConnect's update to how they handle their on-prem version.
Please sign in to leave a comment.
Comments (3 comments)