06-30-2014 08:55 PM
I've noticed in a number of browser flag the quickconnect download as a dangerous file as it's not commonly downloaded.
Is there any way this can be avoided (either through app signing or similar) to allow for browsers to pass this without warning?
Feedback from some of my clients has suggested this doesn't go down well with the users and puts some people off using the app .
Solved! Go to Solution.
06-30-2014 08:59 PM
--Give Kudos: found something helpful, important, or cool? Click Kudos Star in a post.
--Problem Solved? Click "Accepted Solution" in a post.
07-01-2014 07:02 PM
does a code signing certificate have to be internal or self signed or can a public web server cert be used to sign an application?
I'm guessing that the usage parameters wouldn't be right to do this?
What do most people do here?
Can you insert a link to the root self signed certificate to be displayed on the Quickconnect page so the user is prompted to install this before quickconnect (similar to IOS experience)?
07-01-2014 08:40 PM
Tim Cappalli | Aruba ClearPass TME
@timcappalli | ACMX #367 / ACCX #480 / ACEAP / CWSP