problem peppol oxalis standalone certificate expired but is ok #715
Unanswered
aliprandimat
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I'm Matteo and I'm currently testing Oxalis 6.7 (standalone) on an Ubuntu Server 24.04.
I'm encountering an issue when trying to send Peppol documents in test mode.
sudo OXALIS_HOME="/var/peppol/conf" java -Djavax.net.ssl.trustStore=/var/peppol/conf/truststore_peppol.jks -Djavax.net.ssl.trustStorePassword=************ -jar /var/peppol/OUT/oxalis-standalone.jar -f /var/peppol/OUT/DOCS/TestOrdineConBusta.xml -e /var/peppol/OUT/PROCESSED
The error message I get is:
Message failed: Certificate does not have a valid expiration date.
Total time spent: 1s
Attempted to send 0 files
I have verified the keystore multiple times. I tried both:
a single .jks containing private key + leaf + intermediate + root
my configuration is this
oxalis.keystore {
path = "ap_keystore.p12"
password = "***"
key.alias = "peppol_ap"
key.password = ""
type = "PKCS12"
}
oxalis.truststore {
path = "truststore_peppol.jks"
password = "************"
type = "JKS"
}
separate files (keystore and truststore)
But the result is always the same.
Here's the output from the keystore:
Your keystore contains 1 entry
Alias name: peppol_ap
Creation date: May 9, 2025
Entry type: PrivateKeyEntry
Certificate chain length: 2
Certificate[1]:
Owner: CN=PIT000293, OU=PEPPOL TEST AP, O=ENERJ SRL, C=IT
Issuer: CN=PEPPOL ACCESS POINT TEST CA - G2, OU=FOR TEST ONLY, O=OpenPEPPOL AISBL, C=BE
Valid from: Wed Mar 26 00:00:00 UTC 2025
Until: Tue Mar 16 23:59:59 UTC 2027
Root file (truststore)
Certificate[2]:
Owner: CN=PEPPOL Root TEST CA - G2, OU=FOR TEST ONLY, O=OpenPEPPOL AISBL, C=BE
Issuer: CN=PEPPOL Root TEST CA - G2, OU=FOR TEST ONLY, O=OpenPEPPOL AISBL, C=BE
Valid from: Thu Jan 04 00:00:00 UTC 2018
Until: Mon Jan 03 23:59:59 UTC 2028
For additional context, I also deployed Oxalis 6.7 under Tomcat on the same server, only to verify the certificate status, and it correctly reports the certificate as valid:
version.oxalis: 6.7.0
version.java: 11.0.27
mode: TEST
certificate.subject: CN=PIT000293,OU=PEPPOL TEST AP,O=ENERJ SRL,C=IT
certificate.issuer: CN=PEPPOL ACCESS POINT TEST CA - G2,OU=FOR TEST ONLY,O=OpenPEPPOL AISBL,C=BE
certificate.expired: false
build.id: 26f4371
build.tstamp: 10.08.2024 @ 17:14:12 UTC
So it seems the certificate is valid and correctly recognized by the AS4 module in the webapp.
The problem appears only when using the standalone JAR for transmission.
Is there anything I might be missing in the standalone configuration or classpath that affects certificate validation?
Thanks in advance!
Matteo
All reactions