1. Thomas Rolseth
  2. PowerBuilder
  3. Tuesday, 4 May 2021 22:59 PM UTC

We are trying to deploy an application (PB 2019 R3 build 2703) using PowerClient.  I successfully deployed to a local instance of IIS on Windows 10 and then zipped the two folders that were created in inetpub/wwwroot and gave them to the clients IT team.  They put those folders onto their web server in the same location.

When the user tried to launch the application via their browser, they were given the two options -- 'Download the Launcher' and 'Start the Application'.  When doing the former the user reported the following error:

"I received this error from Microsoft Defender SmartScreen:  CloudAppLauncher_Installer.exe was blocked because it could harm your device."

Adding an exclusion to Windows Defender may not be an option due to strict security policies.  Is there anything else that can be done to get around this?

Thanks, Tom

Accepted Answer
Thomas Rolseth Accepted Answer Pending Moderation
  1. Friday, 7 May 2021 21:09 PM UTC
  2. PowerBuilder
  3. # Permalink

I'm still having problems with PowerClient specifically since moving to build 2703 PB 2019 R3.  I can deploy the Cloud App Launcher but it never installs when I load the app in browser.  The microhelp on that page just keeps flashing 'connecting...'.  When I try to install the CAL manually from my AppData folder, it never goes beyond 0% in the progress bar and eventually just closes w/o any error.  I have tried running the CAL as administrator but that doesn't seem to matter.  This is all being done locally (i.e. localhost)

I have the PowerServer 2021 beta installed.  Should I uninstall that?  Perhaps there is a conflict between R3 and PS 2021.

Tom

Attachments (1)
Comment
  1. Armeen Mazda @Appeon
  2. Friday, 7 May 2021 22:49 PM UTC
Hi Thomas, This is most likely conflict between PB 2019 R3 and PB 2021 since PB 2021 is a beta. I think we are going to have hard time to troubleshoot this by posting Q&A. I would recommend you open a support ticket and request a remote session where our support staff remotely debug your environment.
  1. Helpful
  1. Thomas Rolseth
  2. Monday, 10 May 2021 13:41 PM UTC
Ok, thanks. I've logged a case with technical support (6570).
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 10 May 2021 16:54 PM UTC
Hi Tom .. I cannot replicate this issue on my test PC's with R3 & 2021 beta installed. This, I have sent the ticket over to the PC / PS gurus for their feedback.
  1. Helpful
There are no comments made yet.
Thomas Rolseth Accepted Answer Pending Moderation
  1. Tuesday, 4 May 2021 23:57 PM UTC
  2. PowerBuilder
  3. # 1

Regarding #1, we don't have access to the remote web server so will need to have the client look into that.  Regarding #2 and #4, those are the settings I used.  To us, it looks like the Cloud App Launcher is signed by Appeon -- see attached.  Is that not sufficient?

Thanks, Tom 

Attachments (1)
Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 5 May 2021 00:14 AM UTC
Oh, I forgot we sign the default profile ones. Only if you customize the Cloud App Launcher then you need to sign again.

Please verify the URL the end user is using starts with HTTPS and ends in manual.html. If problem still persists, please open a support ticket and also report to Microsoft that this is a false positive.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 4 May 2021 23:22 PM UTC
  2. PowerBuilder
  3. # 2

Hi Tom,

Microsoft Defender should not block the app if you have properly secured the app:

  1. Make sure the application is accessed through HTTPS not HTTP.  In fact, disable HTTP on your Web server.
  2. Configure the Cloud App Launcher using the "Default_WithoutService" profile.
  3. Sign the Cloud App Launcher using a trusted certificate (not self-signed).
  4. In the Deployment tab of the project object, make sure "Startup without background service" is selected (and keep "Deploy manual.html..." selected and "Deploy auto.html..." unselected).
  5. Sign your PowerBuilder app using a trusted certificate (not self-signed).
  6. Launch the app using URL https://www.domain.com/app/manual.html

It is important you do all 6 steps exactly as I said so that your app is deployed with the highest security.

Best regards,
Armeen

Comment
There are no comments made yet.
Thomas Rolseth Accepted Answer Pending Moderation
  1. Tuesday, 4 May 2021 23:01 PM UTC
  2. PowerBuilder
  3. # 3

I should note that we are not using TLS/SSL encryption.  Another post said switching to 'no encryption' fixed a similar issue but that isn't the case here.

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.