The connector.xml files in the policy-security-* quickstart demos specify relative paths to the jks files. Thus, unless you're in JBoss' "bin" directory when you start JBoss, the jks files cannot be found.

Additionally, some of the readme's have their instructions in the wrong order as to when to do a server start vs. the jboss:deploy.

Below please find a copy/paste from a community member who brought this to our attention via a github issue/comment:

Hi,

when I tried to run demos/policy-security-wss-signencrypt quickstart I ran across several problems:

Location of tomcat.jks should be specified differently, because now it is relative to the current working directory when executing EAP.

<ssl name="https" password="changeit" certificate-key-file="../standalone/configuration/tomcat.jks"/>
When lunched from quickstart directory:

15:40:09,007 ERROR [org.apache.tomcat.util] (MSC service thread 1-5) JBWEB003002: Failed to load keystore type JKS with path ../standalone/configuration/tomcat.jks due to ../standalone/configuration/tomcat.jks (Adresář nebo soubor neexistuje)
When lunched from bin directory (./standalone.sh) it is OK.

Step:

4​. Deploy the quickstart

mvn jboss-as:deploy
should be after:

5​. Start JBoss AS 7 in standalone mode:

$

/bin/standalone.sh
because otherwise it ends with:

[ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.1.1.Final:deploy (default-cli) on project switchyard-quickstart-demo-policy-security-wss-signencrypt: Error executing FORCE_DEPLOY: Could not execute operation '

': java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out

----------

The tomcat.jks problem is also in:
demos/policy-security-saml
demos/policy-security-wss-username
demos/policy-security-basic
demos/policy-security-cert
demos/policy-security-wss-signencrypt

The swapped deploy and executions are also in:
demos/policy-security-saml
demos/policy-security-basic
demos/policy-security-wss-signencrypt