Steven Bruneel

Experiencing the same issue with PnP PowerShell for SharePoint 2013 version 3.25.2009.1

Ok, thank you for the fast response!

Ok I'll give it a shot, I think the last row `keyStoreAlias` should be removed? As it is already configured above as `myalias`?

Just tried it out, got the following failure: --- javafx-maven-plugin:8.8.4-SNAPSHOT:build-jar (create-jfxjar) @ CL_AppM --- Building JavaFX JAR for application Adding 'deploy' directory to Mojo classpath: D:\NetBeansProjects\App-M\maven\CL_AppM/src/main/deploy --- javafx-maven-plugin:8.8.4-SNAPSHOT:build-web (create-web) @...

Sorry, my bad. It's been a long day :) I got a BUILD SUCCESS now, however, if I check with `jarsigner -verify`, it let's me know that the jar is...

ah maybe my bad in the short explanation. With the previous keystore (before the hardware key), I signed all jars (so including dependencies) and created a JNLP file to launch...

just tried, yet the jar in `/target/jfx/native/` is still unsigned according to jarsigner... am I doing something bad? :)

not sure if it's possible without the hardware key? :p I can post the plugin configuration thou if you want?

There you go! :) com.zenjava javafx-maven-plugin 8.8.4-SNAPSHOT App_m.ui.MainApp test signing launch true 1.8+ true true YourApplication true myalias mypass true -keystore NONE -storetype PKCS11 -tsa http://timestamp.globalsign.com/scripts/timestamp.dll -providerClass sun.security.pkcs11.SunPKCS11 -providerArg D:\NetBeansProjects\App-M\maven\CL_AppM\src\main\resources\token\eToken.config...

Still unsigned it says :( C:\Program Files\Java\jdk1.8.0_121\bin>jarsigner.exe -verify d:\NetBeansProjects\App-M\maven\CL_AppM\target\jfx\web\CL_AppM-0.9.8-jfx.jar jar is unsigned.