1 Reply Latest reply on Jun 25, 2014 11:00 AM by David Lloyd

    Restricting deployment to signed wars,ears, and jars only

    mike Milner Newbie

      Update:  Looks like I could add a Custom Deployer but would rather use a more straightforward option - any help?

      Is there a way in Wildfly-8-final to restrict loading ear, war and/or jars to those that include a valid digital signature?  Wildfly will verify the signature if one exists in the war, ear, jar but is there a setting or strategy to only allow a successful deployment for those that include a valid signature? I would like the deploymen to fail If the signature verfication fails or the signature is missing.


      Thanks for the help,