1. mike S
  2. PowerServer
  3. Wednesday, 13 December 2023 21:43 PM UTC

We sign the launcher, but we dont' use the super expensive Extended Validation Code due to hardware requirements (must be on a fob or similar).  As a result, edge goes out of its way to try to prevent users from downloading and installing the launcher.

 

PB 2022R2 does not appear support signing when the cert is on hardware.   Am i wrong about that? Has anyone been able to use an Extended Validation code cert?  Hopefully R3 will support hardware tokens/EV certs for all signing.

 

Would it make more sense to just have appeon sign it with their EV cert as an option?

Accepted Answer
Mora Wang @Appeon Accepted Answer Pending Moderation
  1. Thursday, 14 December 2023 06:44 AM UTC
  2. PowerServer
  3. # Permalink

Hi Mike,

2022 R2 also supports signing when the cert is on hardware. You can create a cmd file before creating the Launcher and then sign it through Package Cloud App Launcher > Signing > Use your own signing script(.cmd). For details please refer to the “On the Signing tab, select whether to digitally sign the launcher executable file (CloudAppLauncher_Installer.exe)” on https://docs.appeon.com/ps2022/Customize_cloud_app_launcher.html.

 Also, in the 2022 R3 to be released, we added the support for token-based signing and also made improvements to “Use your own signing script(.cmd)” to support .cmd with parameters so that users can sign the EXE more flexibly. For UI details you can refer to the attached screenshot.

Let us know if you have any thoughts or suggestions about what we do with 2022 R3 so that our products can serve users better. Thanks!

Best Regard,

Mora

Comment
  1. mike S
  2. Thursday, 14 December 2023 16:55 PM UTC
"added the support for token-based signing "



that is great!
  1. Helpful
There are no comments made yet.


There are replies in this question but you are not allowed to view the replies from this question.