AuthAzureSAS ActiveX Reference Documentation

AuthAzureSAS

Current Version: 11.5.0

Chilkat.AuthAzureSAS

Create Azure Shared Access Signature tokens for signed Azure Storage requests.

Chilkat.AuthAzureSAS creates Azure Shared Access Signature authentication tokens. It defines the SAS string-to-sign, supplies the Azure Storage account access key used to compute the signature, and controls which parameters are included in the generated SAS token query string. The resulting token can be used with Chilkat.Rest, Chilkat.Http, or other request-building code that needs time-limited, permission-scoped access to Azure Storage resources.

SAS token generation

Generate a signed query-string token that authorizes limited access to an Azure Storage resource.

String-to-sign control

Provide the exact Azure SAS string-to-sign required for the storage service and resource being accessed.

Account key signing

Use the Azure Storage account access key to compute the signature placed in the generated SAS token.

Token parameters

Add signed SAS parameters such as permissions, expiry, resource type, API version, protocol, or IP restrictions.

Non-token parameters

Add query parameters that should accompany the request but should not be included as part of the SAS token itself.

REST integration

Use the generated SAS query string with Azure Storage requests built using Chilkat.Rest or other Chilkat HTTP workflows.

Common pattern: Create an AuthAzureSAS object, set the Azure Storage AccessKey, provide the required StringToSign, add SAS token parameters with SetTokenParam, add any extra query parameters with SetNonTokenParam, then call GenerateToken. Use AuthAzureSAS when you need a SAS query token; use Chilkat.AuthAzureStorage when you need Shared Key authorization headers instead.

Object Creation

Note:
For a specific major version, use "Chilkat.AuthAzureSAS.<major_version>", such as "Chilkat.AuthAzureSAS.10" for Chilkat v10.*.*
See Chilkat ActiveX Object Creation

(ASP)
set obj = Server.CreateObject("Chilkat.AuthAzureSAS")

(AutoIt)
$obj = ObjCreate("Chilkat.AuthAzureSAS")

(Visual Basic 6.0)
Dim obj As New ChilkatAuthAzureSAS

(VBScript)
set obj = CreateObject("Chilkat.AuthAzureSAS")

(VBA, such as Excel)
Dim obj As New ChilkatAuthAzureSAS
See How to Use ActiveX in Excel

(Delphi)
obj := TChilkatAuthAzureSAS.Create(Self);

(FoxPro)
loObject = CreateObject('Chilkat.AuthAzureSAS')

(PowerBuilder)
lole_object = create oleobject
li_rc = lole_object.ConnectToNewObject("Chilkat.AuthAzureSAS")

(SQL Server)
EXEC @hr = sp_OACreate 'Chilkat.AuthAzureSAS', @obj OUT

(Javascript)
var obj = new ActiveXObject("Chilkat.AuthAzureSAS");

Properties

AccessKey
AccessKey As String
Introduced in version 9.5.0.65

This is the signing key (access key) that must be kept private. It is a base64 string such as abdTvCZFFoWUyre6erlNN+IOb9qhXgDsyhrxmZvpmxqFDwpl9oD0X9Fy0hIQa6L5UohznRLmkCtUYySO4Y2eaw==

top
DebugLogFilePath
DebugLogFilePath As String

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.

top
LastBinaryResult
LastBinaryResult As Variant (read-only)

This property is mainly used in SQL Server stored procedures to retrieve binary data from the last method call that returned binary data. It is only accessible if Chilkat.Global.KeepBinaryResult is set to 1. This feature allows for the retrieval of large varbinary results in an SQL Server environment, which has restrictions on returning large data via method calls, though temp tables can handle binary properties.

top
LastErrorHtml
LastErrorHtml As String (read-only)

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.

top
LastErrorText
LastErrorText As String (read-only)

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.

top
LastErrorXml
LastErrorXml As String (read-only)

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.

top
LastMethodSuccess
LastMethodSuccess As Long

Indicates the success or failure of the most recent method call: 1 means success, 0 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.

top
LastStringResult
LastStringResult As String (read-only)

In SQL Server stored procedures, this property holds the string return value of the most recent method call that returns a string. It is accessible only when Chilkat.Global.KeepStringResult is set to TRUE. SQL Server has limitations on string lengths returned from methods and properties, but temp tables can be used to access large strings.

top
LastStringResultLen
LastStringResultLen As Long (read-only)

The length, in characters, of the string contained in the LastStringResult property.

top
StringToSign
StringToSign As String
Introduced in version 9.5.0.65

Defines the format of the string to sign.

The format is specified as a comma-separated list of names. For example:

signedpermissions,signedstart,signedexpiry,canonicalizedresource,signedidentifier,signedIP,signedProtocol,signedversion,rscc,rscd,rsce,rscl,rsct
This will result in an actual string-to-sign that is composed of the values for each name separated by newline (LF) chars. For example:
signedpermissions + <code>\n</code> +  
signedstart + <code>\n</code> +  
signedexpiry + <code>\n</code> +  
canonicalizedresource + <code>\n</code> +  
signedidentifier + <code>\n</code> +  
signedIP + <code>\n</code> +  
signedProtocol + <code>\n</code> +  
signedversion + <code>\n</code> +  
rscc + <code>\n</code> +  
rscd + <code>\n</code> +  
rsce + <code>\n</code> +  
rscl + <code>\n</code> +  
rsct

More Information and Examples
top
VerboseLogging
VerboseLogging As Long

If set to 1, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is 0. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
Version As String (read-only)

Version of the component/library, such as "10.1.0"

top

Methods

Clear
Clear()
Introduced in version 9.5.0.65

Clears all params set by the methods SetNonTokenParam and SetTokenParam.

Returns 1 for success, 0 for failure.

top
GenerateToken
GenerateToken() As String
Introduced in version 9.5.0.65

Generates and returns the SAS token based on the defined StringToSign and params.

Returns Nothing on failure

More Information and Examples
Explaining Azure SAS Tokens(AutoIt) How to Generate an Azure Service Bus Shared Access Signature (SAS)(Classic ASP) How to Generate an Azure Service Bus Shared Access Signature (SAS)(PowerBuilder) How to Generate an Azure Service Bus Shared Access Signature (SAS)(SQL Server) How to Generate an Azure Service Bus Shared Access Signature (SAS)(VBScript) How to Generate an Azure Service Bus Shared Access Signature (SAS)(Visual Basic 6.0) How to Generate an Azure Service Bus Shared Access Signature (SAS)(Visual FoxPro) How to Generate an Azure Service Bus Shared Access Signature (SAS)(AutoIt) How to Generate an Azure Storage Account Shared Access Signature (SAS)(Classic ASP) How to Generate an Azure Storage Account Shared Access Signature (SAS)(PowerBuilder) How to Generate an Azure Storage Account Shared Access Signature (SAS)(SQL Server) How to Generate an Azure Storage Account Shared Access Signature (SAS)(VBScript) How to Generate an Azure Storage Account Shared Access Signature (SAS)(Visual Basic 6.0) How to Generate an Azure Storage Account Shared Access Signature (SAS)(Visual FoxPro) How to Generate an Azure Storage Account Shared Access Signature (SAS)(AutoIt) Create an Azure Service SAS(Classic ASP) Create an Azure Service SAS(PowerBuilder) Create an Azure Service SAS(SQL Server) Create an Azure Service SAS(VBScript) Create an Azure Service SAS(Visual Basic 6.0) Create an Azure Service SAS(Visual FoxPro) Create an Azure Service SAS(AutoIt) Use an Azure Service SAS(Classic ASP) Use an Azure Service SAS(PowerBuilder) Use an Azure Service SAS(SQL Server) Use an Azure Service SAS(VBScript) Use an Azure Service SAS(Visual Basic 6.0) Use an Azure Service SAS(Visual FoxPro) Use an Azure Service SAS
top
SetNonTokenParam
SetNonTokenParam(name As String, value As String) As Long
Introduced in version 9.5.0.65

Adds a non-token parameter name/value. This is a value that is included in the string to sign, but is NOT included in the token query params.

Returns 1 for success, 0 for failure.

top
SetTokenParam
SetTokenParam(name As String, authParamName As String, value As String) As Long
Introduced in version 9.5.0.65

Adds a token parameter name/value. This is a value that is included in the string to sign, and is also included in the token query params.

Returns 1 for success, 0 for failure.

top