aws / aws/aws-lambda-rust-runtime
IoTCoreCustomAuthorizerResponse create invalid payalod
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 396
- PR merge metrics
- No merged PRs in 30d
Description
It seems that IoTCoreCustomAuthorizerResponse can create a payload not accepted by AWS IOT broker.
The following attributes: `pub policy_documents: Vec>` allow a Vec that contains None but AWS IOT broker raise an AUTHORIZATION_FAILURE error in that case.
The corresponding json value is:
```json
"policyDocuments": [
null
]
```
Should policy_documents type be: `Vec>` instead ?
Contributor guide
Research direction
Start by locating IoTCoreCustomAuthorizerResponse and its policy_documents field, then inspect how IamPolicyDocument values are serialized. Look for related serialization or response tests and verify the completed change cannot produce a policyDocuments array containing null, matching the AWS IoT broker behavior described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- backend-api-design, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100