Repository navigation
blob: Support bearer authorization for URL copy sources - #2897
Merged
Akanksha Jain (jainakanksha-msft) merged 3 commits intoNov 9, 2026
Merged
Akanksha Jain (jainakanksha-msft) merged 3 commits into
Akanksha Jain (jainakanksha-msft) merged 3 commits into
Conversation
Carry forward the implementation and tests from PR #2876 (issue #2815), including bearer-only source credentials and the separator normalization fix. Preserve existing source-read validation and cover both copy operations. Co-authored-by: jainakanksha-msft <jainakanksha@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are identified for the source bearer-authorization changes.
No open issues 🎉
What changed in this PR
Adds bearer authorization for private URL copy sources in Azurite’s Blob service, partially addressing #2815. The separate Copy Blob From URL handler remains out of scope.
Changes:
- Forwards source bearer credentials for Put Blob From URL, Put Block From URL, and copied source tags.
- Normalizes bearer scheme casing and repeated separator spaces while rejecting unsupported schemes.
- Adds OAuth regression coverage and documents the user-visible behavior.
The PR reports successful build, lint, and targeted tests. SQL-backed execution and live Azure compatibility checks were not repeated.
| File | Description |
|---|---|
tests/blob/oauth.test.ts |
Adds source authorization, tag copying, normalization, and credential rejection tests. |
src/blob/handlers/BlockBlobHandler.ts |
Validates and forwards bearer source credentials to content and tag reads. |
ChangeLog.md |
Documents source authorization support under Upcoming Release. |
Review effort: Balanced
Akanksha Jain (jainakanksha-msft)
deleted the
fix/copy-source-authorization-release
branch
November 9, 2026 10:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Carry forward #2876 onto a new branch based on
mainfor release consideration, preserving the original author's attribution. Includes the source-authorization implementation, tests, and the separator-normalization fix from commit c6461a7.Related issue: #2815. This is a partial fix: the separate Copy Blob From URL handler remains out of scope.
Changes
Validation
npm run buildandnpm run lint: passed.git diff --check: passed.Existing installed dependencies were reused. Local HTTPS tests used the repository-standard TLS test override. SQL-backed execution and live Azure checks were not repeated for this branch; test tags do not establish SQL coverage.
Reviewer notes
--oauth basicbehavior; does not add token-signature or RBAC enforcement.Checklist
main(Azurite V3).