Running
Tomcat
This is a work in progress while I figure out which settings required for the Servlet 4.0 TCK ar still required for the Servlet 5.0 TCK.
setenv.[sh|bat]
Set the following system properties
...
Remove the sections setting the default character encoding for requests and responses to UTF-8.
...
.
...
server.xml
Enable TLS on port 8443
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true">
<SSLHostConfig truststoreFile="conf/cacerts.jks">
<Certificate certificateKeystoreFile="conf/clientcert.jks"
certificateKeystorePassword="changeit"
type="RSA" />
</SSLHostConfig>
</Connector>
Remove the lock-out realm
Client certificate tests: see below
Test Suite
Download latest nightly build
...
Extract to SERVLET_TCK_HOMEImport
cd $SERVLET_TCK_HOME/bin/certificates
Convert cts_cert to a truststore doing: "keytool -import -alias cts -file cts_cert -storetype JKS -keystore cacerts.jks" password should be "changeit"
Create the truststore using "keytool -import -alias cts -file cts_cert -storetype JKS -keystore cacerts.jks" password should be "changeit"
Place cacerts.jks truststore in $SERVLET_TCK_HOME/bin/certificates
Add $SERVLET_TCK_HOME/bin/certificates/cacerts.jks and $SERVLET_TCK_HOME/bin/certificates/clientcert.jks in the Tomcat conf folder
...
securedWebServicePort=8443
command.testExecute += -Djava.endorsed.dirs=${ts.home}/endorsedlib -Djavax.net.ssl.trustStore=${ts.home}/bin/certificates/cacerts.jks
...
A default 10.0.x build (as of 2020-06-18) with the above configuration and the TCK built from source (as of 2020-06-18) triggers 25 23 test failures
1 Expected failures
...
- PR 338
- Incorrect major version (1 failure),
- Using LF rather an CRLF (15 failures)
- Strange /j_security_check test (2 failures)
- Error page attributes assumed to be unset when spec requires them to be set (3 failures)
- Missing annotation marker in Java 8 signature tests (1 failure)
...
- Re-do Java 11 signature test based on Java 8