When a new add-in loads into Revit you get a Security warning dialog asking the user to trust the add-in. While this makes sense, especially for unsigned add-ins, our signed add-in still generates this dialog.
According to the Revit API documentation:
https://help.autodesk.com/view/RVT/2020/ENU/?guid=Revit_API_Revit_API_Developers_Guide_Introduction_Add_In_Integration_Digitally_Signing_Your_Revit_Add_in_Digitally_Signing_Your_App_html
"Once the DLL is signed with an authorized certification, Revit will no longer pop up a security warning dialog upon loading your add-in."
We signed our add-in dll with a number of code signing cert providers but a security dialog always is displayed. We kept on buying more expensive code signing certificates thinking that this might be a matter that the root certificates of the CA authority may not be trusted.
First tried a trial Ascertia code signing cert.
Next a GlobalSign standard code signing cert protected by a hardware token.
Lastly, a DigiCert EV code signing cert which is also protected by a hardware token.
All produce the security dialog. I don't think there is a more trusted certificate than an EV one.
Is there something else I must do to get this security dialog to not show?
I have researched the forums and there is an old thread about code signing Revit add-ins that seems to talk about this:
https://forums.autodesk.com/t5/revit-api-forum/code-signing-of-revit-addins/td-p/5981560
It this thread Jeremy Tammik reproduced a copy of pre-release documentation that seems to indicate that I need to install a certificate in the Trusted Publishers store. I have experimented with this and it seems if I add the code signing certificate itself to the Trusted Publishers store, Revit does indeed not show the security dialog on loading the add-in.
But is this right? I need to use the "code signing" certificate? The root certificate does not work?
I have some resistance to this as I want my add-in installer to not require administrator privileges.
Also, I could not find any mention of this in "official" Autodesk documentation (except for making your own certificate for testing). I don't want to apply a fix that will just break with the next update of Revit.
I have also tried some of the registry modifications from this forum thread.
https://forums.autodesk.com/t5/revit-api-forum/security-prompt-for-unsigned-add-ins/td-p/7299954
They did not work for me. Maybe because the add-in is signed.
What do other add-in developers do to get rid of this dialog?