Closed delema98 closed 1 year ago
Thanks for reporting this bug, it is a regression of #1777 and caused by the fact that this environment variable was never exposed in the command line, and we only tested the command line options. Is end of August ok for a fix?
Thanks for your quick answer and your support! Would a pull request from my side significantly speed up this process? If I find some time to look into this, I might be able to support.
Thank you for the offer @delema98, the fix has been integrated as part of the latest snapshot and will be part of 2.9.1, likely mid to end of August. If you want to test you can publish a docker image from main, and run that one instead of the official one that will be released.
Great thanks! I'll for sure take a look at that!
After upgrading to Version 2.9.0 we encounter some certificate issues (see stack trace below). In the past (while using v2.8.4) we were using the command line options:
"--pf=/mount/opcpublishermodule.settings.json",
"--aa",
"--tm",
"--RejectUnknownRevocationStatus=false",
"--mq=100",
"--batchsize=2",
"--heartbeatinterval=15",
"--iothubprotocol=AmqpOverTcp",
"PkiRootPath=/mount/pki"
Is it possible that the CLI command ""--RejectUnknownRevocationStatus=false" is not supported anymore? Additionally to the stack trace shown below we get the following error message:
The certificates are structured like this: https://reference.opcfoundation.org/v104/GDS/docs/F.1/
Stack trace: