A request with no X-Amz-Target and no Authorization gets MissingAuthenticationToken, where DynamoDB answers UnknownOperationException

Open Beginner friendly
#1,287 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust

Research direction

Read extract_operation in crates/server/src/request_helpers.rs and the missing_target_no_auth_returns_missing_auth_token unit test. Compare the code comment and test with the DynamoDB response measured in the issue. Done when the comment and test reflect the reported UnknownOperationException behavior for a request with neither header.

Written by the indexing model from the issue text.

Description

Amazon DynamoDB answers a POST with no X-Amz-Target header and no Authorization header with UnknownOperationException and no message. ExtendDB answers MissingAuthenticationToken.

Measured in us-east-1 on 21 Nov 2026 with a POST to / with the Content-Type application/x-amz-json-1.0, the body {"Limit": 1}, and neither header. The request went out twice and got the same answer both times. The ExtendDB column is SQLite at f0170bde8.

Part of the answer DynamoDB ExtendDB
Status 400 400
Body {"__type":"com.amazon.coral.service#UnknownOperationException"} {"__type":"com.amazon.coral.service#MissingAuthenticationToken","message":"Missing Authentication Token"}
X-Amz-Crc32 1368724161 2747205903

extract_operation in crates/server/src/request_helpers.rs (lines 21 to 30) answers MissingAuthenticationToken when the request has neither header, and UnknownOperationException when it has an Authorization header but no X-Amz-Target. Its comment says that DynamoDB answers MissingAuthenticationToken when the auth headers are absent too. The measurement above contradicts that sentence. The unit test missing_target_no_auth_returns_missing_auth_token pins the current answer.

The fix for #1075 changes ExtendDB's body for this request to the new type and message of that error. It does not change which error this request gets.

Dominant language
Rust
Stars
517
Forks
60
Avg merge
4d 23h
Merged PRs (30d)
134

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ExtendDB/extenddb

All issues in ExtendDB/extenddb

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.