play-scala-tls certificates expired on 25th Aug 2019
ignasi35 opened this issue · 1 comments
ignasi35 commented
$ cd play-samples/play-scala-tls-example/scripts
$ openssl x509 -in example.com.crt -text
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 63408077 (0x3c787cd)
Signature Algorithm: ecdsa-with-SHA256
Issuer: C=US, ST=California, L=San Francisco, O=Example Company, OU=Example Org, CN=exampleCA
Validity
Not Before: May 27 16:58:42 2019 GMT
Not After : Aug 25 16:58:42 2019 GMT
Subject: C=US, ST=California, L=San Francisco, O=Example Company, OU=Example Org, CN=example.com
Subject Public Key Info:
Public Key Algorithm: id-ecPublicKey
Public-Key: (256 bit)
pub:
04:a8:b1:a8:15:bd:df:88:f4:71:cf:e9:18:f1:70:
a3:fa:23:a5:d2:92:f3:65:04:fc:24:b0:89:9a:7e:
57:74:09:8e:e9:6f:ee:e1:8d:1f:e0:94:40:74:6e:
...
This causes tests to fail:
[info] ServerSpec:
[info] Server
[info] - should work fine over https *** FAILED ***
[info] The future returned an exception of type: java.net.ConnectException, with message: General SSLEngine problem. (ServerSpec.scala:40)
[info] ScalaTest
[info] Run completed in 5 seconds, 545 milliseconds.
[info] Total number of tests run: 1
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 0, failed 1, canceled 0, ignored 0, pending 0
[info] *** 1 TEST FAILED ***
[error] Failed: Total 1, Failed 1, Errors 0, Passed 0
This only surfaces now because we haven't launched a single build in the last 26+ days.