AuthAzureStorage Dart Reference Documentation
CkAuthAzureStorage
Current Version: 11.6.1
Chilkat.AuthAzureStorage
Hold the storage account name and Base64 account access key used to sign
Azure Storage REST requests.
Configure Azure Storage authentication using
Specify the Azure Storage service being accessed, such as
Set the
Use the configured object with
Pair this authentication object with manually constructed REST requests
when application code needs direct control over Azure Storage operations.
For an extended overview, see
AuthAzureStorage Class Overview.
Authenticate Azure Storage REST requests with account-key Shared Key signing.
Chilkat.AuthAzureStorage is a credential object for Azure
Storage Services authentication. It stores the storage account name, Base64
account access key, Azure Storage service type, authentication scheme, and
x-ms-version API version used when signing REST requests for
Blob, Queue, File, or Table storage.
Azure Storage credentials
Shared Key signing
SharedKey or
SharedKeyLite, depending on the service and request style.
Service targeting
Blob, Queue, File, or
Table.
API version header
x-ms-version value required by the Azure Storage
REST API version being used.
REST integration
Chilkat.Rest so requests are
signed automatically before being sent.
Low-level control
AuthAzureStorage object, set the storage
Account, Base64 AccessKey, Service,
Scheme, and XMsVersion, then attach it to a
Chilkat.Rest request workflow. Use
AuthAzureStorage for Shared Key authorization headers; use
Chilkat.AuthAzureSAS when the request should be authorized with
a SAS query token instead.
Object Creation
// pubspec.yaml:
// dependencies:
// chilkat: ^11.6.1
import 'package:chilkat/chilkat.dart';
// Once per process, before any other Chilkat call:
Chilkat.unlockBundle('Anything for 30-day trial'); // shorthand for CkGlobal().unlockBundle(..)
final authAzureStorage = CkAuthAzureStorage();
// ... the native object is released when `authAzureStorage` is garbage collected, or now with authAzureStorage.dispose().Creates the underlying native Chilkat object. Use a CkAuthAzureStorage only from the isolate that created it: Chilkat objects cannot be sent between isolates. Every call is synchronous; in a Flutter app, run long operations (network, large files) inside Isolate.run, creating the Chilkat objects inside the isolate.
Releases the native object immediately instead of waiting for garbage collection (useful for a large CkBinData or an open socket). Calling it more than once is harmless; any other use of the object afterwards throws a StateError. isDisposed tells whether it has been called.
Errors
A method that can fail throws a ChilkatException: a method whose only outcome is success or failure returns void and throws on failure; a method producing a String or an object returns it and throws where Chilkat would have returned null. The exception carries the object's LastErrorText at the time of the failure (lastErrorText), the class and method names (className, methodName) and a one-line message. Properties never throw, and methods that answer a question (has..., is..., ...) return a plain bool.
try {
authAzureStorage.someMethod(...);
} on ChilkatException catch (e) {
print(e); // CkAuthAzureStorage.someMethod failed: <reason>
print(e.lastErrorText); // the full Chilkat log of the failed call
}Properties
AccessKey
String get accessKey
set accessKey(String value)
Account
String get account
set account(String value)
The Azure storage account name. (A storage account can contain zero or more containers. A container contains properties, metadata, and zero or more blobs. A blob is any single entity comprised of binary data, properties, and metadata. )
topDebugLogFilePath
String get debugLogFilePath
set debugLogFilePath(String value)
If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.
Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.
Possible causes of hangs include:
- A timeout property set to 0, indicating an infinite timeout.
- A hang occurring within an event callback in the application code.
- An internal bug in the Chilkat code causing the hang.
LastErrorHtml
String get lastErrorHtml
Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastErrorText
String get lastErrorText
Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
LastErrorXml
String get lastErrorXml
Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastMethodSuccess
bool get lastMethodSuccess
set lastMethodSuccess(bool value)
Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.
Scheme
String get scheme
set scheme(String value)
Can be SharedKey or SharedKeyLite. The default value is SharedKey.
Service
String get service
set service(String value)
Can be Blob, Queue, File, or Table. The default is Blob.
Note: Authentication for the Table service did not work in versions prior to v9.5.0.83.
VerboseLogging
bool get verboseLogging
set verboseLogging(bool value)
If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.
Version
String get version
XMsVersion
String get xMsVersion
set xMsVersion(String value)
If set, automatically adds the x-ms-version HTTP request header to Azure Storage requests. The default value is 2014-02-14.