- 最新
- 最多得票
- 最多評論
Hi Encho,
Can you please take a look at the pem files and check whether they are certificate chains? (It has more than one certificate) If it does, this is a known issue in aws-c-io and a fix has been submitted. If you'd like to manually apply the fix yourself before a new version is released, it's a single line change.
In aws-c-io -> source -> windows -> windows_pki_utils.c change line 606 from
if (i != cert_count - 1 || !add_result) {
to
if (i != 0 || !add_result) {
That should fix the issue and unblock you for now until this is propagated into a release.
Hello,
Thanks for the answer. When the fix is expected to be released? Something more, is this library used by the Java SDK? We are using Java(sorry if I forgot to mention this) Currently, we are partially blocked(because from the team, I am the only one working on Windows machine).
Thanks!
Hi Encho, the fix may be a little ways off as we need to also implement unit testing before pushing it to main. The fix is in the CRT so it should apply to all higher level languages, java included as long as you're using the v2 SDKs. In the meanwhile, could you provide me with logs from the CRT as well as the certificates that are being used in your testing? Thanks!
Hello Steve,
I can provide the logs but the only ones which I see are part of the Java stacktrace of the execution. Could you tell me how to enable the logs of the CRT?
Thanks!
Hi Encho, you can look at how the CRT handles logging here: https://github.com/awslabs/aws-crt-java/blob/main/src/main/java/software/amazon/awssdk/crt/Log.java
Please set the following properties: -Daws.crt.debugnative=true -Daws.crt.log.destination=File -Daws.crt.log.level=Trace -Daws.crt.log.filename=<path and filename>
相關內容
- 已提問 6 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
How do you instantiate the
AwsIotMqttConnectionBuilder
? By using one of the factory methods?Or do you set the tlsOptions by hand?