Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (6)

Resolved PowerServer signing questions (again)

  1. How-to
0
Votes
Undo
  1. Marco Meoni
    Marco Meoni
  2. PowerServer
  3. Monday, 27 September 2021 18:11 PM UTC

Hello,
I went through this very informative post (thank you Glenn!):

https://community.appeon.com/index.php/qna/q-a/powerclient-signing-questions

I am using PS 2021 instead of PC, but frontend deployment is the same and Glenn's considerations are applicable too.

In short, I am stuck with generic error "please check signature info" when signing the executable.
I expected to be in case (1) from post above, so installed my self-signed certificate under Certificate Manager, but no luck.

Since CMD script from command line signs the app correctly (bottom-right in the screenshot below), I also gave a try to last option in PS project signing tabpage.
However:
- sign.cmd script in the form "signtool sign <options> app.exe" doesn't show any errors BUT app.EXE is not signed;
- sign.cmd script in the form "sign <options> app.exe" shows "check the script" error.

All in all however, my goal is to use SignTool option form PS project tab page.
What could still be the issue?

Best,
.m

Cause of Powerserver Error 02012
Issue running powerserver2021
Responses (6)
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Friday, 8 October 2021 07:59 AM UTC
  2. PowerServer
  3. # 1

Hello,

quick recap of the findings, hoping they will be useful for others.

Given that CMD script was working (with syntax in the command shell from previous post), problem using SignTool.exe from PB was http://timestamp.digicert.com not accessible by user running PB IDE.

PB in fact is started as administrator because otherwise FTP to deployment server is not allowed by the customer. And admin user is not allowed to access timestamp URL.

The CMD script instead was working because, when launched from within PB, it is executed as regular user (which has internet access).

Thanks ZhaoKai for hints and support.

Best,

.m

 

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 27 September 2021 20:06 PM UTC
  2. PowerServer
  3. # 2

Hi Marco;

  • Since it works in DOS Command mode ... Are you running the PB IDE "As Admin"?
  • Could this be an MS-Windows "policy"  restriction issue?

Regards ... Chris

Comment
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 28 September 2021 05:04 AM UTC
  2. PowerServer
  3. # 3

Hi Marco,

Does it work well on other machines? Please make sure the application is deployed successfully without signing.

It might be a file path related issue, the app.exe will be deployed into the temp path, for example, C:\Users\%Windows user%\AppData\Local\Temp\pbappscache\temp\%your application%, please try signing the exe file in the temp path with full path via CMD script from the command line to see if it works.

Regards,
ZhaoKai

Comment
There are no comments made yet.
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Wednesday, 29 September 2021 07:57 AM UTC
  2. PowerServer
  3. # 4

Hi ZhaoKai and Chris,

I always run PB as admin, and there are no known restriction issues.
The point is to understand what PB is doing when calling Signtool.exe. 
The error description is very minimal.

@ZhaoKai: how PB is calling SignTool?

For what is worth, I have tried to sign SalesDemo on my machine with same customer's self-signed certificate and it works.
In the attached image, left side my local machine while signing SalesDemo, right side customer's machine while signing his app. 
"Generating file list" step is not coming...

Best,

.m

Comment
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Thursday, 30 September 2021 02:21 AM UTC
  2. PowerServer
  3. # 5

Hi Marco,

It seems to be a deploying issue rather than a signing issue, please try deploying the application without signing to see if it works.

And please also provide a simple PB case that can reproduce the issue to us for more study, thanks.

Regards,
ZhaoKai

Comment
There are no comments made yet.
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Thursday, 30 September 2021 07:12 AM UTC
  2. PowerServer
  3. # 6

Hi ZhaoKai,

deployment works and app is running ok.

Production wants the app do be signed otherwise it would be blocked by app locker.

That's I am trying to sign.

Best,

.m

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.