So, more stuff I always forget... how to properly generate SSL certs. Well, easiest is with openssl (of course) Something like: openssl req -new -newkey rsa:2048 -nodes -sha256 -subj "/C=NL/ST=Utrecht/L=Utrecht/O=Cooperatieve Rabobank U.A./OU=RASS Groep ICT/CN=my-common-name.host.nl" -keyout somename-prod.key -out somename-prod.csr That can get you a certificate sign request (csr) and the appropriate key. Of course, you want to then import those keys into a keystore. The trick to doing that is to convert it to a pkcs12 format where it can have the certificate and the key combined. openssl pkcs12 -export -inkey somename-prod.key -in somename-prod.rabobank.nl.crt -out somename-prod.p12 Note that the crt is the signed certificate, acquired through getting the csr generated above approved.. This p12 file you can import using something like KeyStore Explorer. After that, you can also append the root certificates of the original cert, to en...
We've had it so, so often. Junit 5 is a bitch to run in maven. First there were issues with the surefire plugin. Make sure that is updated. Then there were issues with the versions you need to use together. Whelp, that was all set up right. And of course... still no junit 5 A fun thing was seeing this: [INFO] --- maven-surefire-plugin:3.1.2:test (default-test) @ my-project --- [INFO] Using auto detected provider org.apache.maven.surefire.junit4.JUnit4Provider Yeah, that's not how it should go. This forces the junit 4 provider... Which is not the junit 5 generic one. After a lot of digging, it turns out that surefire determines which provider to use... through some magic from the classpath. Of course, nowhere is there a junit4 dependency. They're all gone. Well... Except... Except... The platform dependency < dependency > < groupId >org.junit.platform</ groupId > < artifactId >junit-platform-launcher</ artifactId > < version ...