SQL Server

Azure ServiceBus - Request a Token from ACS

This example duplicates the HTTP POST described at Request a Token from ACS. SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    -- This example assumes the Chilkat HTTP API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    -- The goal of this example is to send the following HTTP POST:

    -- POST https://your-namespace-sb.accesscontrol.windows.net/WRAPv0.9/ HTTP/1.1  
    -- Content-Type: application/x-www-form-urlencoded  
    -- Host: your-namespace-sb.accesscontrol.windows.net  
    -- Content-Length: 136  
    -- Expect: 100-continue  
    -- Connection: Keep-Alive  
    -- 
    -- wrap_name=owner&wrap_password=r8LuxCKD6DWY8auQcFql4M7euH2UuhcLcV1TaJTqNNE%3d&wrap_scope=http%3a%2f%2fyour-namespace.servicebus.windows.net%2f
    -- 

    DECLARE @http int
    EXEC @hr = sp_OACreate 'Chilkat.Http', @http OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @req int
    EXEC @hr = sp_OACreate 'Chilkat.HttpRequest', @req OUT

    -- Build the HTTP request...
    EXEC sp_OASetProperty @req, 'HttpVerb', 'POST'
    EXEC sp_OASetProperty @req, 'Path', '/WRAPv0.9/'
    EXEC sp_OASetProperty @req, 'ContentType', 'application/x-www-form-urlencoded'

    -- Adding the Connection: Keep-Alive is optional.  It only makes sense if the intent is to send
    -- additional requests to the same domain (your-namespace-sb.accesscontrol.windows.net) within a reasonable time period.
    EXEC sp_OAMethod @req, 'AddHeader', NULL, 'Connection', 'Keep-Alive'

    -- The Expect: 100-continue really isn't necessary.  This only makes sense when a response is large.  The "100-continue"
    -- provides a means for the HTTP server to alert the HTTP client that the request failed before sending the full response.
    -- In this case, the response size is small, so there's no real need to bother with an "Expect: 100-continue".
    -- If desired, it would be added just like any request header:
    EXEC sp_OAMethod @req, 'AddHeader', NULL, 'Expect', '100-continue'

    -- Note: The following headers are automatically added by Chilkat:  Content-Type, Host, Content-Length.
    -- The application should NOT set these directly.

    -- Add the query parameters
    -- When URL decoded and split, the query params look like this:
    -- 
    -- 	wrap_name=owner
    -- 	wrap_password=r8LuxCKD6DWY8auQcFql4M7euH2UuhcLcV1TaJTqNNE=
    -- 	wrap_scope=http://your-namespace.servicebus.windows.net/

    -- Pass the URL-decoded values to AddParam.
    EXEC sp_OAMethod @req, 'AddParam', NULL, 'wrap_name', 'owner'
    EXEC sp_OAMethod @req, 'AddParam', NULL, 'wrap_password', 'r8LuxCKD6DWY8auQcFql4M7euH2UuhcLcV1TaJTqNNE='
    EXEC sp_OAMethod @req, 'AddParam', NULL, 'wrap_scope', 'http://your-namespace.servicebus.windows.net/'

    -- OK.. our request is properly setup.  Now send to the web server at your-namespace-sb.accesscontrol.windows.net.
    -- We want https (i.e. SSL/TLS), so the port would be 443.
    DECLARE @useTls int
    SELECT @useTls = 1
    DECLARE @resp int
    EXEC @hr = sp_OACreate 'Chilkat.HttpResponse', @resp OUT

    EXEC sp_OAMethod @http, 'HttpSReq', @success OUT, 'your-namespace-sb.accesscontrol.windows.net', 443, @useTls, @req, @resp
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @req
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END

    -- A successful response will have a status code = 200.
    EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
    IF @iTmp0 <> 200
      BEGIN

        EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
        PRINT 'Response Status Code = ' + @iTmp0
        EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
        PRINT @sTmp0

        PRINT 'Failed.'
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @req
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END

    -- A successful response will contain a URL encoded param string such as the following:

    -- 	wrap_access_token=net.windows.servicebus.action%3d
    -- 	Listen%252cManage%252cSend%26
    -- 	http%253a%252f%252fschemas.microsoft.com%252faccesscontrolservice%252f2010%252f07%252fclaims%252fidentityprovider%3d
    -- 	https%253a%252f%252fyour-namespace-sb.accesscontrol.windows.net%252f%26
    -- 	Audience%3dhttp%253a%252f%252fyour-namespace.servicebus.windows.net%252f%26
    -- 	ExpiresOn%3d1404435127%26
    -- 	Issuer%3dhttps%253a%252f%252fyour-namespace-sb.accesscontrol.windows.net%252f%26
    -- 	HMACSHA256%3dF%252bBoXUoifWdT%252fly8Oic9V1oPBbc3KmXKbSJbVhGSopU%253d&
    -- 	wrap_access_token_expires_in=10799
    -- 

    -- The UrlEncParamValue method can be used to extract individual param values by name.
    -- There are two params in the response: wrap_access_token and wrap_access_token_expires.
    -- (It's a bit confusing because the value of the wrap_access_token is itself a URL encoded 
    -- param string.)

    -- Get the access token from the response:
    DECLARE @accessToken nvarchar(4000)
    EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
    EXEC sp_OAMethod @resp, 'UrlEncParamValue', @accessToken OUT, @sTmp0, 'wrap_access_token'


    PRINT 'Your access token is the following param string:'

    PRINT @accessToken

    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @req
    EXEC @hr = sp_OADestroy @resp


END
GO