NuMaker connection with AWS IoT thru MQTT/HTTPS
Dependencies: MQTT
my-tlssocket/mbed_lib.json@45:7d315fb1ba3e, 2021-09-02 (annotated)
- Committer:
- ccli8
- Date:
- Thu Sep 02 11:34:22 2021 +0800
- Revision:
- 45:7d315fb1ba3e
- Parent:
- 41:b878d7cd7035
Fix MQTT client ID collision
If not assigned, generate unique MQTT client ID:
1. For non-TZ targets, use FMC/UID.
2. For TZ targets (NS), FMC/UID is inaccessible. Use random instead.
Who changed what in which revision?
User | Revision | Line number | New contents of line |
---|---|---|---|
ccli8 |
25:edf568984d27 | 1 | { |
ccli8 |
25:edf568984d27 | 2 | "name": "my-tlssocket", |
ccli8 |
25:edf568984d27 | 3 | "config": { |
ccli8 |
25:edf568984d27 | 4 | "tls-debug-level": { |
ccli8 |
25:edf568984d27 | 5 | "help": "Debug level for TLS. Larger value for more verbose message. Its value can be 0, 1, 2, 3, or 4", |
ccli8 |
41:b878d7cd7035 | 6 | "value": 0 |
ccli8 |
25:edf568984d27 | 7 | }, |
ccli8 |
25:edf568984d27 | 8 | "tls-max-frag-len": { |
ccli8 |
25:edf568984d27 | 9 | "help": "Maximum fragment length value for the payload in one packet, doesn't include TLS header and encryption overhead. Is needed for constrainted devices having low MTU sizes, Value 0 = disabled, 1 = MBEDTLS_SSL_MAX_FRAG_LEN_512, 2= MBEDTLS_SSL_MAX_FRAG_LEN_1024, 3 = MBEDTLS_SSL_MAX_FRAG_LEN_2048, 4 = MBEDTLS_SSL_MAX_FRAG_LEN_4096", |
ccli8 |
25:edf568984d27 | 10 | "value": 0 |
ccli8 |
25:edf568984d27 | 11 | } |
ccli8 |
25:edf568984d27 | 12 | } |
ccli8 |
25:edf568984d27 | 13 | } |