You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ISSUE:
Currently, the "Getting Started Kit" vended by the IoT console vends a policy that doesn't match the strings used by any V2 SDK samples. So they fail right off the bat 😢
SOLUTION:
Let's get all the V2 SDKs using the same strings, then we can create a policy to fit them all. I'd like to put wildcards in the new policy so users can toy around a little bit, but include the word "test" everywhere so they feel inclined to change it before they ship.
Also, let's get all the samples putting randomness into the client-id, since colliding IDs are a frequent source of confusion.
Also, make a default topic for pubsub samples
Please note that on Mac, once a private key is used with a certificate, that certificate-key pair is imported into the Mac Keychain. All subsequent uses of that certificate will use the stored private key and ignore anything passed in programmatically. Beginning in v1.7.3, when a stored private key from the Keychain is used, the following will be logged at the "info" log level:
58
60
59
-
```
61
+
```
60
62
static: certificate has an existing certificate-key pair that was previously imported into the Keychain. Using key from Keychain instead of the one provided.
61
63
```
62
64
63
65
## Samples
64
66
65
67
[Samples README](samples)
66
68
67
-
68
-
69
69
## Getting Help
70
70
71
71
Use the following sources for information :
72
72
73
-
*Check api and developer guides.
74
-
*Check for similar issues already opened.
73
+
* Check api and developer guides.
74
+
* Check for similar issues already opened.
75
75
76
76
If you still can’t find a solution to your problem open an [issue](https://github.com/aws/aws-iot-device-sdk-cpp-v2/issues)
77
77
78
-
79
-
80
78
## Giving Feedback and Contributions
81
79
82
80
We need your help in making this SDK great. Please participate in the community and contribute to this effort by submitting issues, participating in discussion forums and submitting pull requests through the following channels.
83
81
84
-
*[Contributions Guidelines](CONTRIBUTING.md)
85
-
* Articulate your feature request or upvote existing ones on our [Issues](https://github.com/aws/aws-iot-device-sdk-cpp-v2/issues?q=is%3Aissue+is%3Aopen+label%3Afeature-request) page.
* Articulate your feature request or upvote existing ones on our [Issues](https://github.com/aws/aws-iot-device-sdk-cpp-v2/issues?q=is%3Aissue+is%3Aopen+label%3Afeature-request) page.
0 commit comments