Skip to content

Correct overstated Azurite HTTPS limitation in azure.md #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vectorloom merged 1 commit into from
Aug 15, 2026
Merged

Correct overstated Azurite HTTPS limitation in azure.md #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions docs/providers/azure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,11 +86,15 @@ for diagnosing *why*.
- **HTTPS only.** `AddAzureBlobPersistenceProvider`'s `TokenCredential` path refuses to construct
a client against an `http://` URI at all (`Azure.Storage`'s own guard against sending bearer
tokens unencrypted) — confirmed by running the composed image against a local Azurite over
plain HTTP, which throws immediately at startup. This is never a problem in a real deployment
(Azure Storage is HTTPS-only anyway), but it does mean this provider can't be exercised
end-to-end against local Azurite the way `AzureBlobPersistenceProvider`'s own unit and
plain HTTP, which throws immediately at startup. Never a problem in a real deployment (Azure
Storage is HTTPS-only anyway), but it does mean this provider can't be exercised end-to-end
against a *default* local Azurite the way `AzureBlobPersistenceProvider`'s own unit and
integration tests do (those construct `BlobContainerClient` directly from an Azurite connection
string, bypassing this extension method entirely).
string, bypassing this extension method entirely). Azurite can be configured for HTTPS + OAuth
(`--cert`/`--key` plus `--oauth basic` — see
[Azurite's docs](https://learn.microsoft.com/azure/storage/common/storage-install-azurite#certificate-configuration-https)),
which would let `TokenCredential` auth work against it too; RiftCache doesn't set this up or
test against it today.

### Usage

Expand Down
Loading