AzureCredential
Produces the Authorization header value for one AzureBlobClient request.
Shared Key needs the full request shape to compute a signature; a bearer-token strategy needs none of it and answers the same header for every call. Both fit through this one seam so AzureBlobClient::send() never branches on which kind of credential it was given.
Synopsis
Section titled “Synopsis”interface AzureCredential
| Implemented by | BearerCredential, SharedKeyCredential |
| Source | AzureCredential.php |
Methods
Section titled “Methods”| Method | Description |
|---|---|
authorizationHeader(string $accountName, string $method, string $path, array<string, string> $query, array<string, string> $headers): string |
authorizationHeader()
Section titled “authorizationHeader()”abstract public function authorizationHeader(string $accountName, string $method, string $path, array<string, string> $query, array<string, string> $headers): string
The request’s headers, including x-ms-date and
x-ms-version, before Authorization is added.
| Parameter | Type | Description |
|---|---|---|
$accountName | string | |
$method | string | |
$path | string | |
$query | array``<``string``, ``string``> | Signed as part of the canonicalized resource. |
$headers | array``<``string``, ``string``> | The request’s headers, including x-ms-date and x-ms-version, before Authorization is added. |
Returns string