...
Ensure you are using the right Username / Password. You can reset the Admin GUI accounts by running the supplied SQL scripts to reset the database to its default CONNECTAdmin account.
SOAPUI ValidationSuite fails to run correctly
Make sure your SoapUI has the libraries (FileUtils and MySQL jars) installed to run the ValidationSuite.
SoapUI Validation Fails with NPE before it hits the server
Make sure your GatewayPropDir property points to the nhinc property folder
The property 'nhinc.properties.dir' is not being found
Check your jvm making sure the path is being specifed: -Dnhinc.properties.dir=//Your/Path/Here/
SoapUI at a remote location
All that needs to be done is to change the endpoint so that the message is sent to the correct location.
Differences between secure and unsecure adapter web service requests
the The wsdls are different because the secured versions translate the CONNECT assertion element into an actual SAML assertion, while the unsecured version just keeps CONNECT assertion element
Where's the documentation on how to build an adapter?
the The reference adapter which come with CONNECT are a great place to start. In general adapters can be developed on three different interfaces; java, web services, and secured web services. You can implement the adapter’s java interface and package your implementation in the CONNECT application (ear), or go for web services. The WSDLs are in github so if you are familiar with WSDL first web services you can go that route.
...
Adding the system property '-Djavax.net.debug=ssl' to your jvm. This will output some pretty verbose logging but have found that it's a good way to track the the SSL handshake.
Validation tests are failing because of certificate path problems
The keystores were set up for you automatically. If this is the case, your gateway is using self-signed certificates. The Java keystore, gateway.jks, contains your gateway's certificate, which is known by the alias "gateway". This certificate has also been imported into the truststore, cacerts.jks, so that the gateway can make secured connections to itself. You may make secured connections to yourself when testing, so that your local gateway acts as both the requesting and responding gateway, and also at other times depending on your gateway configuration. If you want to send a message to a remote gateway, the same "gateway" certificate must be imported into the remote gateway's truststore.
Seeing WSSecurityException "The message has expired (WSSecurityEngine: Invalid timestamp The security semantics of the message have expired)"
...
If your local gateway uses the CommonType JAR, make sure it the correct version. Otherwise, please make sure your local gateway is using the correct schema.
Validation Suite issues
SoapUI at a remote location
All that needs to be done is to change the endpoint so that the message is sent to the correct location.
SOAPUI ValidationSuite fails to run correctly
Make sure your SoapUI has the libraries (FileUtils and MySQL jars) installed to run the ValidationSuite.
SoapUI Validation Fails with NPE before it hits the server
Make sure your GatewayPropDir property points to the nhinc property folder
Validation tests are failing because of certificate path problems
The keystores were set up for you automatically. If this is the case, your gateway is using self-signed certificates. The Java keystore, gateway.jks, contains your gateway's certificate, which is known by the alias "gateway". This certificate has also been imported into the truststore, cacerts.jks, so that the gateway can make secured connections to itself. You may make secured connections to yourself when testing, so that your local gateway acts as both the requesting and responding gateway, and also at other times depending on your gateway configuration. If you want to send a message to a remote gateway, the same "gateway" certificate must be imported into the remote gateway's truststore.